redis-inspect

$npx mdskill add aAAaqwq/AGI-Super-Team/redis-inspect

Inspect Redis cache keys, values, and TTLs for debugging.

  • Debug cache issues and verify stored data contents.
  • Integrates with Redis main and system cache instances.
  • Executes read-only queries by default with optional write access.
  • Outputs structured results via JSON or raw command formats.

SKILL.md

.github/skills/redis-inspectView on GitHub ↗
---
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`.

More from aAAaqwq/AGI-Super-Team

SkillDescription
a-fund-monitor监控 A 股基金实时估值与盘后净值,自动判断交易日并生成提醒或分析。
add-leadAdd company/person/relationship to CRM
ads-agentAI-агент для управления Facebook рекламой. Вызывай для анализа, оптимизации, создания кампаний и отчётов.
afrexai-compliance-auditRun internal compliance audits against major governance and security
afrexai-personal-financeComplete personal finance system — budgeting, debt payoff, investing, tax optimization, net worth tracking, and financial independence planning. Use when managing money, building wealth, paying off debt, planning retirement, or optimizing taxes. Zero dependencies.
after-salesUse when managing post-purchase experience, building customer loyalty, or increasing repeat purchases
agent-contactsAI agent contacts — add, list, remove MCP contacts. Use when someone gives an agent URL, or when you need to view/remove contacts.
agent-model-switcher批量查看和切换子 agent 的模型配置,用于统一调整多 agent 的 provider/model 设置。
agent-patternsFormat SPAWN REQUEST messages to launch parallel agents, generate structured agent status reports, and define communication protocols within the sprint system. Use when the user needs to coordinate multiple agents, format spawn requests, produce agent reports, or establish inter-agent communication patterns.
agent-task-confirmUse when confirming whether a dispatched agent task was actually received, activated, and progressing after sessions_send or other task handoff actions.