redis-patterns

Redis data structure patterns, caching strategies, distributed locks, rate limiting, pub/sub, and connection management for production applications. Use when adding caching, a distributed lock, rate limiting, or pub/sub with Redis, or when key design needs review.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

The body is a strong, executable pattern catalog with concrete code and tables across the main Redis use cases. Its weakest spot is workflow clarity for destructive/batch operations, where explicit validation feedback loops are missing, and a lightly padded introductory section.

Suggestions

Trim or remove the "How It Works" paragraph — Claude already knows what Redis, RESP, and connection pools are; keep only anything non-obvious.

Add explicit validate→fix→retry checkpoints to destructive/batch operations: verify a cache invalidation cleared the expected keys, confirm consumer-group `xack` only after processing succeeds, and gate cluster/Sentinel setup on a connectivity/role check.

Consider splitting the per-pattern code (locks, streams, rate limiting) into one-level-deep reference files with a lean overview in SKILL.md to push progressive disclosure toward the top anchor.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code and tables, but the "How It Works" paragraph restates basic facts Claude already knows (what Redis stores, RESP protocol, why pools matter), which is minor over-explanation that could be trimmed.	4 / 5
Actionability	Provides fully executable, copy-paste-ready Python and Lua covering common cases (cache-aside, Lua sliding-window rate limit, SET NX PX locks with token-checked release, Streams consumer groups, pooling/cluster/sentinel), plus concrete key-naming and TTL tables.	5 / 5
Workflow Clarity	Sequences are clear within each pattern (e.g., acquire → try/finally release), but destructive/batch operations (cache invalidation, cluster setup, consumer-group ack, FLUSHALL) lack explicit validate→fix→retry checkpoints, which caps workflow clarity per the destructive-operations rule.	3 / 5
Progressive Disclosure	A single self-contained file with well-labeled sections, tables, and a Related-skills pointer; no nested or buried references. It is well organized but does not split detail into one-level-deep reference files, so it sits just below the top anchor.	4 / 5
	Total	16 / 20 Passed

Description

92%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.

The description is specific, covers the Redis domain comprehensively, and pairs a clear capability statement with explicit "Use when" triggers. Only minor synonym coverage is missing on the trigger-term side.

Dimension	Reasoning	Score
Specificity	Lists multiple specific capability areas — "caching strategies, distributed locks, rate limiting, pub/sub, and connection management" — giving comprehensive coverage of the Redis domain rather than vague abstractions.	5 / 5
Completeness	Explicitly answers both what (Redis data structure patterns and the listed strategies) and when ("Use when adding caching, a distributed lock, rate limiting, or pub/sub with Redis, or when key design needs review") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural phrases a user would say ("adding caching," "distributed lock," "rate limiting," "pub/sub with Redis") are well covered, though a few synonyms like "throttling" or "Redis Streams" as triggers are missing.	4 / 5
Distinctiveness Conflict Risk	The Redis-specific framing plus the "with Redis" qualifier and key-design trigger carve out a clear niche with minimal overlap against generic caching or backend skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/redis-patterns/SKILL.md
Commit: d8409a4

Reviewed: 1 day 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.