redis-inspect — Claude Code skill: what it does, how to install
redis-inspect — a skill that reads keys, values and TTLs across two Redis instances, the main cache and the system cache. Handy when you need to see what the cache holds right now.
Apache-2.0 ★ 7,327 updated 2026-10-25
npx skills add civitai/civitai --skill redis-inspect -a claude-codeWhat redis-inspect does
The skill wraps a small Node script, node .claude/skills/redis-inspect/query.mjs, and exposes Redis commands through it: get, keys, ttl, type, exists, hgetall, hget, scard, smembers, llen, lrange, del, info. Patterns in keys accept * as a wildcard, and --limit caps output at 100 by default.
Two instances are wired in. The main cache comes from REDIS_URL. Add --sys to reach the system cache through REDIS_SYS_URL, where feature flags, generation limits and job state live. A ttl reply of -1 means no expiry is set, -2 means the key is gone.
Reads are the default. del only runs with --writable, and the skill tells the agent to get your approval first, so that flag stays your call. Of the two caches, the system one holds the more critical data.
What it helps with
- trace why a session key disappeared
- read the remaining TTL on a generation counter
- dump every field of a feature-flag hash
- count members of a queue set
- check Redis server memory and stats
Example prompts for the agent
- List the first 10 keys matching
session:data2:*. - What is the TTL on
generation:count:123? - Pull all fields of
system:featuresfrom the system cache.
How to install redis-inspect
1Skills CLI (Vercel)
npx skills add civitai/civitai --skill redis-inspect -a claude-code2Manually: put the files in place
~/.claude/skills/redis-inspect/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/redis-inspect/
1Skills CLI (Vercel)
npx skills add civitai/civitai --skill redis-inspect -a codex2Manually: put the files in place
.agents/skills/redis-inspect/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add civitai/civitai --skill redis-inspect -a cursor2Manually: put the files in place
.cursor/skills/redis-inspect/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install civitai/civitai apps/event-engine/.claude/skills/redis-inspect2Manually: put the files in place
.github/skills/redis-inspect/SKILL.md1Skills CLI (Vercel)
npx skills add civitai/civitai --skill redis-inspect -a gemini-cli2Platform CLI
gemini skills install https://github.com/civitai/civitai --path apps/event-engine/.claude/skills/redis-inspectManually: put the files in place
.devin/skills/redis-inspect/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add civitai/civitai --skill redis-inspect -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about redis-inspect
How do I install redis-inspect in Claude Code?
Run npx skills add civitai/civitai --skill redis-inspect -a claude-code. The skill file then sits at ~/.claude/skills/redis-inspect/SKILL.md.
What does redis-inspect do?
It reads keys, values, types and TTLs through query.mjs, hitting the main cache or the system one when --sys is passed. Writes stay locked unless --writable is given.
How is the system cache different from the main one?
The main cache is a cluster-mode application cache, and its contents can be regenerated if lost. The system cache is single-node storage for configuration and state that matters more.
Source text
SKILL.md · Apache-2.0
--- name: redis-inspect description: Inspect Redis cache keys, values, and TTLs for debugging. Supports both main cache and system cache. Use for debugging cache issues, checking cached values, and monitoring cache state. Read-only by default. --- # Redis Cache Inspector Use this skill to inspect Redis cache state for debugging purposes. ## Running Commands ```bash node .claude/skills/redis-inspect/query.mjs <command> [options] ``` ### Commands | Command | Description | |---------|-------------| | `get <key>` | Get a string value | | `keys <pattern>` | Find keys matching pattern (use * as wildcard) | | `ttl <key>` | Get TTL (-1 = no expiry, -2 = not found) | | `type <key>` | Get the type of a key | | `exists <key>` | Check if key exists | | `hgetall <key>` | Get all fields from a hash | | `hget <key> <field>` | Get a specific hash field | | `scard <key>` | Get set cardinality (count) | | `smembers <key>` | Get all set members | | `llen <key>` | Get list length | | `lrange <key>` | Get list elements | | `del <key>` | Delete a key (requires --writable) | | `info` | Get Redis server info | ### Options | Flag | Description | |------|-------------| | `--sys` | Use system cache instead of main cache | | `--writable` | Allow write operations (required for del) | | `--json` | Output raw JSON | | `--limit <n>` | Limit results (default: 100) | ## Cache Types The project has two Redis instances: | Cache | Flag | Env Variable | Purpose | |-------|------|--------------|---------| | **Main Cache** | (default) | `REDIS_URL` | Regular cache, cluster mode, can be lost | | **System Cache** | `--sys` | `REDIS_SYS_URL` | Persistent system values, single node | ### Main Cache (default) Regular application cache. Data here can be regenerated if lost. - User sessions - Cached queries - Temporary data - Rate limiting counters ### System Cache (--sys) Persistent system configuration and state. More critical data. - Feature flags - Generation limits/status - System permissions - Job state - Event configurations ## Examples ```bash # Find keys matching a pattern node .claude/skills/redis-inspect/query.mjs keys "user:*" --limit 20 node .claude/skills/redis-inspect/query.mjs keys "packed:caches:*" # Get a value node .claude/skills/redis-inspect/query.mjs get "session:data2:123456" # Check system cache values node .claude/skills/redis-inspect/query.mjs --sys get "system:features" node .claude/skills/redis-inspect/query.mjs --sys hgetall "system:entity-moderation" # Check TTL node .claude/skills/redis-inspect/query.mjs ttl "generation:count:123" # Inspect a hash node .claude/skills/redis-inspect/query.mjs hgetall "packed:caches:cosmetics" node .claude/skills/redis-inspect/query.mjs hget "system:entity-moderation" "entities" # Check set size node .claude/skills/redis-inspect/query.mjs scard "queues:seen-images" # Get server info node .claude/skills/redis-inspect/query.mjs info node .claude/skills/redis-inspect/query.mjs --sys info ``` ## Common Key Patterns ### Main Cache | Pattern | Description | |---------|-------------| | `user:*` | User data | | `session:*` | Session data | | `packed:caches:*` | Packed/compressed cached data | | `packed:user:*` | Packed user cache | | `generation:*` | Generation-related cache | | `tag:*` | Tag cache | ### System Cache | Pattern | Description | |---------|-------------| | `system:*` | System configuration | | `generation:*` | Generation limits/status | | `download:limits` | Download limits | | `job:*` | Job state | | `event:*` | Event configurations | | `new-order:*` | New Order game state | | `daily-challenge:*` | Daily challenge config | ## Debugging Tips ```bash # Check if a user's session exists node .claude/skills/redis-inspect/query.mjs keys "session:data2:*" --limit 10 # Check generation status node .claude/skills/redis-inspect/query.mjs --sys get "generation:status" # Check feature flags node .claude/skills/redis-inspect/query.mjs --sys hgetall "system:features" # Check cache memory usage node .claude/skills/redis-inspect/query.mjs info ``` ## Write Operations Write operations require `--writable` flag and user approval: ```bash # Delete a specific key (requires approval) node .claude/skills/redis-inspect/query.mjs del "some:key" --writable ``` **IMPORTANT**: Always ask the user for permission before using `--writable`.
© civitai · Apache-2.0 · civitai/civitai