How do I install the Inspect Redis skill?

Run npx skillmds@latest add hiai-gg/inspect-redis in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Inspect Redis skill do?

Inspect Redis keys and values: scan keys by pattern, read values of any type, check TTLs and types, and summarize what is stored. Use when asked what is in Redis, whether a key exists, or why a value looks wrong. It is listed under Research & Search on SkillMD.

Is Inspect Redis safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Inspect Redis?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Inspect Redis free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Inspect Redis?

HiAi-gg (@hiai-gg) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Inspect Redis by hiai-gg — Agent Skill

Name: Inspect Redis
Author: HiAi-gg

File contents

Inspect Redis Data

Use this skill when an agent needs to look at what is stored in Redis.

Server capability note

The official redis-mcp-server exposes write tools (set, lpush, sadd, zadd, xadd, expire, rename, delete, …). This skill is read-first: inspect before you ever consider writing. Mutating data requires explicit user intent.

Workflow

1. Orient

Confirm the target: dbsize for key count, info for server basics.
Identify the logical namespace from the user's question (e.g. session:*, cache:*, user:*).

2. Scan keys

Use scan_keys (or scan_all_keys when the set is small) with a pattern.
Prefer narrow patterns; do not dump the whole keyspace into a response.
Note the count so the user knows the scale.

3. Read values by type

type <key> first — the type determines the right read tool.
String: get <key>
Hash: hgetall <key>
List: lrange <key> 0 -1
Set: smembers <key>
Sorted set: zrange <key> 0 -1 WITHSCORES (or zrangebyscore for a range)
Stream: xrange <key> - + (see inspect-redis-streams)
JSON: json_get <key>
TTL: ttl <key> via the server's expiry tooling; negative means no TTL or missing key.

4. Summarize

Report: key count, the values/types you examined (quote selectively), and any TTL/expiry facts. If a value is missing, check the pattern and the database number (--url suffix /0, /1, …) before concluding.

Guardrails

Read tools only unless the user explicitly asks to change data.
Do not output entire large collections — bound with ranges/limits and summarize.

Frequently asked questions

Inspect Redis