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.
| 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. |
Use this skill to inspect Redis cache state for debugging purposes.
node .claude/skills/redis-inspect/query.mjs <command> [options]
| 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 |
| 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) |
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 |
Regular application cache. Data here can be regenerated if lost.
Persistent system configuration and state. More critical data.
# 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
| 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 |
| 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 |
# 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 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.
Wire an existing ecosystem into the generation system. Adds generation support to basemodel.constants.ts, creates graph and handler files, and wires them into the ecosystem discriminator, workflow config, and router. Use after add-ecosystem when you need the ecosystem to show up in the generation form. Always checks @civitai/client for ecosystem-specific types before writing the handler.
Draft a model description for the CivitaiOfficial account when mirroring a third-party model on civitai.com or civitai.red. Use when the user is publishing or rewriting a mirrored model page (e.g. Sulphur, HappyHorse, Wan, ACE-Step) and wants a structured, properly-credited description rather than a one-line stub. Produces HTML ready to paste into the Civitai rich-text editor.
Read, replace, reset, export, and import XGuard policy options on the orchestrator. Use when you need to inspect current per-label policies for text or prompt scans, ship a refined policy, restore defaults, or back up the policy registry. Read-only by default; destructive operations require an explicit `--writable` flag.
Run PostgreSQL queries for testing, debugging, and performance analysis. Use when you need to query the database directly, run EXPLAIN ANALYZE, compare query results, or test SQL optimizations. Always uses read-only connections unless explicitly directed otherwise.
Author a prompt-enhancement system prompt for a new ecosystem and register/update it on the orchestrator's prompt-analysis service. Use when onboarding a new ecosystem (e.g. happyhorse, a new Flux variant, a new Wan video version) and the user provides the ecosystem key plus a reference link, model card, or description. Produces a guide that mirrors the structure and tone of existing ecosystem guides so the prompt-analysis tool behaves consistently.
Query and explore Civitai Orchestration workflows, jobs, and results. Use for analyzing image/video generation jobs, viewing job results, searching by workflow ID, job ID, user, or date range.
