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.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured reference whose executable commands and tables are excellent. Its main gaps are the missing verification step around the destructive 'del' operation and some redundancy between the Examples and Debugging Tips sections.

Suggestions

Add a verification checkpoint to the Write Operations workflow, e.g. run 'exists <key>' to confirm the target before 'del' and again after to confirm removal, so destructive operations have a validate-then-act feedback loop.

Merge the Debugging Tips section into Examples (or replace it with cross-references) to remove the duplicated keys/get/hgetall/info commands and reduce token cost.

Tighten the opening line ('Use this skill to inspect Redis cache state for debugging purposes.') since it restates the frontmatter description.

Dimension	Reasoning	Score
Conciseness	The body is a mostly lean tabular reference with no over-explanation of concepts Claude already knows, but the Debugging Tips section repeats commands already shown in Examples and the opening line restates the frontmatter description.	4 / 5
Actionability	Every command is a fully-formed, copy-paste-ready 'node .claude/skills/redis-inspect/query.mjs ...' invocation and the Examples cover the common cases (keys, get, ttl, hgetall, hget, scard, info, del), matching the anchor 5 example.	5 / 5
Workflow Clarity	The destructive 'del' operation has a permission gate ('--writable' flag plus 'Always ask the user for permission') but no verification checkpoint such as confirming the key with 'exists' before or after deletion, so the destructive-operation cap of 3 applies.	3 / 5
Progressive Disclosure	Content is well-organized into clear headed sections and tables with no nested references, but the roughly 140-line body has Examples/Debugging Tips redundancy that could be tightened or split.	4 / 5
	Total	16 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that explicitly covers both what the skill does and when to use it with concrete, natural trigger phrases. Its only weakness is minor overlap among the 'Use for' use cases and a lack of synonym variation.

Dimension	Reasoning	Score
Specificity	Lists concrete actions ('Inspect Redis cache keys, values, and TTLs', 'checking cached values') but the 'Use for' use cases (debugging, checking, monitoring) overlap and are not fully comprehensive, fitting just below the anchor 5 example.	4 / 5
Completeness	It explicitly states the what ('Inspect Redis cache keys, values, and TTLs for debugging. Supports both main cache and system cache.') and the when ('Use for debugging cache issues, checking cached values, and monitoring cache state.') with concrete trigger phrases, matching the anchor 5 example.	5 / 5
Trigger Term Quality	Natural trigger phrases like 'debugging cache issues' and 'checking cached values' are present and would be said by a user, but synonyms such as 'troubleshoot' or 'examine cache' are missing, so it stops short of comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	It occupies a clear Redis-specific niche with distinct triggers (cache keys, values, TTLs, dual main/system cache) and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: civitai/civitai
Path: .claude/skills/redis-inspect/SKILL.md
Commit: c6ce0a4

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.