redis-patterns

Redis data structure patterns, caching strategies, distributed locks, rate limiting, pub/sub, and connection management for production applications.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/redis-patterns/SKILL.md

Quality

Content

77%

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-organized Redis reference with executable code throughout. It loses points for a brief redundant intro paragraph and for keeping everything in one monolithic file rather than splitting detailed reference material into bundle files.

Suggestions

Trim the 'How It Works' paragraph to only what Claude would not already know about Redis.

Move the larger reference tables (eviction policies, TTL strategy, anti-patterns) into a references/ markdown file and link to it, keeping SKILL.md an overview.

Dimension	Reasoning	Score
Conciseness	Mostly lean and code-driven, but the 'How It Works' paragraph explains Redis basics Claude already knows ('Redis is an in-memory data structure store that supports strings, hashes, lists...'), which is unnecessary padding.	2 / 3
Actionability	Provides fully executable, copy-paste-ready Python and Lua examples with concrete keys, TTLs, and pipeline usage across every pattern.	3 / 3
Workflow Clarity	As a reference/patterns skill each pattern is self-contained and unambiguous; risky operations like lock release use try/finally and atomic Lua scripts.	3 / 3
Progressive Disclosure	No bundle files exist, so all content is inline in a single ~400-line file; the cheat-sheet and reference tables could be split out, and the one-level-deep structure is not signaled via references.	2 / 3
	Total	10 / 12 Passed

Description

82%

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 specific, well-scoped description with natural trigger terms and low conflict risk. Its only gap is the missing explicit 'Use when...' trigger guidance.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when implementing caching, rate limiting, distributed locks, sessions, or pub/sub with Redis.'

Optionally add common user phrasings like 'Redis cache' or 'Redis lock' to further surface trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'data structure patterns, caching strategies, distributed locks, rate limiting, pub/sub, and connection management' — rather than vague language.	3 / 3
Completeness	Clearly answers 'what does this do', but there is no explicit 'Use when...' trigger clause, which caps completeness at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	Natural terms users would say are well covered: 'caching', 'rate limiting', 'distributed locks', 'pub/sub', 'Redis', 'connection management'.	3 / 3
Distinctiveness Conflict Risk	Redis-specific scope with distinct trigger terms makes it unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 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
Commit: 754b8dd

Reviewed: 3 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.