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.
Best use case
redis-inspect is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using redis-inspect should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/redis-inspect/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How redis-inspect Compares
| Feature / Agent | redis-inspect | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
SKILL.md Source
# 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`.
Related Skills
worktree
Create and manage git worktrees with automatic environment setup. Creates worktrees at ../model-share-<branch>, copies .env, and runs pnpm install.
ux-design
UX design methodology and external consultation. Use when creating user flows, wireframes, interaction patterns, or getting UX feedback. Provides structured frameworks for user-centered design.
retool-query
Run queries against the Retool PostgreSQL database for moderation notes, user notes, and other Retool-managed data. Read-only by default. Use when you need to query the Retool database directly.
ralph
Autonomous agent for tackling big projects. Create PRDs with user stories, then run them via the CLI. Sessions persist across restarts with pause/resume and real-time monitoring.
quick-mockups
Create multiple UI design mockups in parallel. Use when asked to create mockups, wireframes, or design variations for a feature. Creates HTML files using Mantine v7 + Tailwind following Civitai's design system.
postgres-query
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.
opensearch-admin
Inspect and debug OpenSearch clusters — health, index stats, search performance, query profiling, mappings, shards, and thread pools. Read-only admin operations for monitoring and troubleshooting.
mod-actions
Take moderator actions on users - ban, mute, remove content, manage leaderboard eligibility, send DMs. Use when you need to ban a user, mute them, send direct messages, or take other moderation actions.
metabase
Create and manage Metabase questions, dashboards, and public links. Use when the user wants to build metrics dashboards, create saved questions with SQL queries, or share analytics publicly.
meilisearch-admin
Check Meilisearch index status, tasks, health, and settings. Use for debugging search issues, monitoring indexing tasks, and inspecting index configuration. Read-only admin operations.
freshdesk
Interact with Freshdesk support platform - search/view/update tickets, reply to customers, add notes, look up contacts, and manage Knowledge Base articles. Use when you need to manage support tickets, look up customer information, or work with KB content.
flipt
Manage Flipt feature flags - list, create, enable/disable, and configure rollout rules. Use when you need to control feature flag state or set up segmented rollouts.