agentsclimarketplace

Redis inspect

Skill aAAaqwq/AGI-Super-Team/skills/redis-inspect

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.From its SKILL.md

Install
npx -y skills add aAAaqwq/AGI-Super-Team --skill redis-inspect

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

4.2 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it

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

CommandDescription
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)
infoGet Redis server info

Options

FlagDescription
--sysUse system cache instead of main cache
--writableAllow write operations (required for del)
--jsonOutput raw JSON
--limit <n>Limit results (default: 100)

Cache Types

The project has two Redis instances:

CacheFlagEnv VariablePurpose
Main Cache(default)REDIS_URLRegular cache, cluster mode, can be lost
System Cache--sysREDIS_SYS_URLPersistent 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

PatternDescription
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

PatternDescription
system:*System configuration
generation:*Generation limits/status
download:limitsDownload 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.

What ships with it: 1 file

11.9 KB alongside SKILL.md, 1 of them executable

Gives 0 of the 12 instructions most databases sql skills give in ~1.1k tokens

Counted across 609 of the 712 authors here whose files we hold, read 2026-09-06

  • Index all foreign key columnsin 26 of 609
  • Use cursor pagination instead of offsetin 25 of 609, across 20 files
  • Use timestamptz for timestampsin 21 of 609
  • Specify columns instead of using select starin 20 of 609, across 10 files
  • Use parameterized queries for all database interactionsin 20 of 609, across 19 files
  • Use Enum for categorical datain 17 of 609, across 7 files
  • Order by frequently filtered columnsin 17 of 609, across 7 files
  • Batch data insertsin 17 of 609, across 7 files
  • Use expand-contract pattern for schema changesin 17 of 609
  • Use materialized views for real-time aggregationsin 16 of 609, across 6 files
  • Partition tables by timein 16 of 609, across 6 files
  • Use smallest appropriate data typesin 16 of 609, across 6 files

Said here and by no other author read

  • Use the query script for cache inspection
  • Use --sys flag for system cache
  • Use --json flag for raw output
  • Use --limit to restrict result count
  • Ask for user permission before using --writable

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.