Skip to main content
skill CX Codex

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

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add civitai/civitai --skill redis-inspect -a claude-code
Open on GitHub

What 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:features from the system cache.

How to install redis-inspect

1Skills CLI (Vercel)

npx skills add civitai/civitai --skill redis-inspect -a claude-code

2Manually: put the files in place

~/.claude/skills/redis-inspect/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/redis-inspect/

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

Similar skills

All skills for Backend and APIs →

From the same set11

The whole set →
quick-mockups quick-mockups generates 3 to 5 parallel UI mockups in HTML. Useful when you need to explore layouts, wireframes, and hierarchy variations before writing frontend code. CX Codex +1 1,700installs meilisearch-admin meilisearch-admin — a skill for monitoring Meilisearch: check indexes, tasks, server health, and search settings. Spot indexing errors and diagnose what's wrong with your search. CX Codex +1 132installs postgres-query postgres-query — a skill for Claude Code that executes PostgreSQL queries during debugging and performance analysis. It targets specific database environments with --prod or --dev flags under read-only mode. CX Codex +1 105installs agent-review Route code and prompts to external AI agents for review. Anthropic models use your local subscription via Claude Agent SDK; other models go through OpenRouter API. Useful for security audits, architecture validation, or a second opinion. CX Codex +1 3installs discord Posts messages, embeds, and announcements to Discord channels via REST API. Useful for team alerts and release notices during coding sessions. CX Codex +1 ★ 7,327repo stars clickhouse-query clickhouse-query runs ad-hoc ClickHouse queries from the chat: metrics, event data, execution plans. Read-only unless you say otherwise. CX Codex +1 ★ 7,327repo stars postgres-query postgres-query runs PostgreSQL queries, inspects index usage, and analyzes execution plans using read-only connections by default. CX Codex +1 ★ 7,327repo stars browser-automation browser-automation runs browser sessions behind an HTTP server, keeps auth profiles, and supports concurrent users. Useful for repeatable flows and multi-user checks. CX Codex +1 ★ 7,327repo stars

Project sponsors

Companies that keep this analytics open