redis-inspect
Redis-inspect provides read-only access to Redis instances, enabling users to view keys, retrieve values, check TTLs, and inspect data structures.
Install
mkdir -p .claude/skills/redis-inspect && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/873" && unzip -o skill.zip -d .claude/skills/redis-inspect && rm skill.zipInstalls to .claude/skills/redis-inspect
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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.Key capabilities
- →Inspect Redis cache keys and values
- →Check TTL and key types
- →Retrieve hash fields and set members
- →Monitor server info
- →Delete keys with authorization
How it works
It provides a CLI interface to query Redis instances, supporting both main and system caches with read-only defaults.
Inputs & outputs
When to use redis-inspect
- →Check the TTL of a specific cache key
- →Debug session storage by inspecting hash fields
- →Monitor cache state during development
About this skill
Redis Cache Inspector
Use this skill to inspect Redis cache state for debugging purposes.
Running Commands
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
# 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
# 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:
# 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.
When not to use it
- →When performing write operations without user approval
- →When accessing system cache without the --sys flag
Prerequisites
Limitations
- →Write operations require --writable flag and user approval
- →Default limit of 100 results
How it compares
It provides a dedicated, safe interface for inspecting cache state compared to using generic Redis CLI tools.
Compared to similar skills
redis-inspect side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| redis-inspect (this skill) | 6 | 6mo | Review | Beginner |
| optimizing-performance | 1 | 2mo | Review | Intermediate |
| prisma-connection-pool-exhaustion | 1 | 6mo | Review | Intermediate |
| supabase-advanced-troubleshooting | 1 | 25d | Caution | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by civitai
View all by civitai →You might also like
optimizing-performance
CloudAI-X
Analyzes and optimizes application performance across frontend, backend, and database layers. Use when diagnosing slowness, improving load times, optimizing queries, reducing bundle size, or when asked about performance issues.
prisma-connection-pool-exhaustion
blader
Fix Prisma "Too many connections" and connection pool exhaustion errors in serverless environments (Vercel, AWS Lambda, Netlify). Use when: (1) Error "P2024: Timed out fetching a new connection from the pool", (2) PostgreSQL "too many connections for role", (3) Database works locally but fails in production serverless, (4) Intermittent database timeouts under load.
supabase-advanced-troubleshooting
jeremylongshore
Execute apply Supabase advanced debugging techniques for hard-to-diagnose issues. Use when standard troubleshooting fails, investigating complex race conditions, or preparing evidence bundles for Supabase support escalation. Trigger with phrases like "supabase hard bug", "supabase mystery error", "supabase impossible to debug", "difficult supabase issue", "supabase deep debug".
plain-optimize
dropseed
Captures and analyzes performance traces to identify slow queries and N+1 problems. Use when analyzing performance or optimizing database queries.
bullmq-specialist
davila7
BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when: bullmq, bull queue, redis queue, background job, job queue.
agentdb-advanced-features
ruvnet
Master advanced AgentDB features including QUIC synchronization, multi-database management, custom distance metrics, hybrid search, and distributed systems integration. Use when building distributed AI systems, multi-agent coordination, or advanced vector search applications.