ClawHub

Redis

v1.0.0

Use Redis effectively for caching, queues, and data structures with proper expiration and persistence.

⭐ 4· 2k·18 current·18 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name, description, and declared dependency (redis-cli as optional) align with the content: caching, queues, data structures, expiry, persistence, clustering, and memory management. Nothing requested that is unrelated to operating Redis.
✓
Instruction Scope
SKILL.md contains only Redis usage guidance and example commands (SET, EXPIRE, XADD, EVAL, etc.). It does not instruct reading unrelated files, pulling external URLs, or accessing unrelated environment variables. Note: it advises using EVAL (Lua) and other powerful commands — if the agent actually executes those against a reachable Redis instance, those commands will run with whatever privileges the Redis connection has.
✓
Install Mechanism
No install spec — instruction-only skill. Nothing is downloaded or written to disk by the skill itself.
✓
Credentials
No environment variables, credentials, or config paths are requested. The single binary listed (redis-cli) is appropriate for the stated purpose.
✓
Persistence & Privilege
The skill does not request permanent presence, does not modify other skills, and uses default invocation settings. It is user-invocable and not always-enabled.
Assessment
This is a coherent, instruction-only Redis best-practices guide and contains no hidden installs or credential requests. Before allowing an agent to execute these instructions (or giving it network access to Redis instances), consider that many example commands mutate data (SET, XADD, EVAL, etc.). If your agent can run redis-cli or reach Redis servers, it could make changes or run arbitrary Lua via EVAL with whatever access the connection has. If you want to limit risk, keep the agent isolated from production Redis endpoints, avoid giving it credentials, or only allow read-only/monitoring access when testing.

Like a lobster shell, security has layers — review code before you run it.

latestvk973mvtq54gfx0bqem2ykdyhy180wr1k

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

🔴 Clawdis
OSLinux · macOS · Windows
Any binredis-cli

Comments