redis-cache-manager

Redis Cache Manager - Auto-activating skill for Backend Development. Triggers on: redis cache manager, redis cache manager Part of the Backend Development skill category.

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill redis-cache-manager

What are skills?

Overall
score

19%

Review — 4%

Does it follow best practices?

Validation — 11 / 16 Passed

Validation for skill structure

SKILL.md

Review

Evals

Activation

This description is severely underdeveloped, consisting only of auto-generated boilerplate without any substantive content. It fails to describe what the skill actually does, provides redundant and narrow trigger terms, and lacks any guidance on when Claude should use it. The description would be nearly useless for skill selection among multiple options.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Manages Redis cache operations including setting/getting keys, configuring TTL, handling cache invalidation, and monitoring cache performance.'

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user mentions redis, caching strategies, cache invalidation, key expiration, or needs to optimize data retrieval with in-memory storage.'

Expand trigger terms to include natural variations users would say: 'redis', 'cache', 'caching', 'key-value', 'TTL', 'cache miss', 'cache hit', 'in-memory database'.

Dimension	Reasoning	Score
Specificity	The description only names the domain ('Redis Cache Manager') without describing any concrete actions. There are no specific capabilities listed like 'set cache keys', 'manage TTL', 'flush cache', etc.	1 / 3
Completeness	The description fails to answer 'what does this do' beyond the title, and has no 'Use when...' clause or equivalent guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	The trigger terms are redundant ('redis cache manager' listed twice) and overly specific. Missing natural variations users would say like 'redis', 'caching', 'cache invalidation', 'key-value store', 'memcache alternative'.	1 / 3
Distinctiveness Conflict Risk	While 'Redis' is a specific technology that provides some distinctiveness, the lack of specific capabilities means it could overlap with general database skills or other caching-related skills.	2 / 3
	Total	5 / 12 Passed

Implementation

This skill is a placeholder template with no actual Redis cache management content. It describes what a skill should do in abstract terms but provides zero actionable information about Redis caching patterns, commands, connection handling, or best practices. Claude already knows more about Redis than this skill teaches.

Suggestions

Add concrete Redis connection and caching code examples (e.g., SET/GET with TTL, cache-aside pattern implementation in Node.js/Python/Go)

Include specific caching strategies with executable code: cache invalidation patterns, cache warming, distributed locking

Define a clear workflow for implementing caching: identify cacheable data → choose TTL strategy → implement cache-aside → add monitoring/metrics

Add references to advanced topics like Redis Cluster configuration, Sentinel setup, or pub/sub for cache invalidation in separate files

Dimension	Reasoning	Score
Conciseness	The content is entirely boilerplate with no actual Redis-specific information. It explains what the skill does in abstract terms without providing any concrete Redis caching knowledge, wasting tokens on meta-description rather than actionable content.	1 / 3
Actionability	No concrete code, commands, or specific guidance is provided. Phrases like 'Provides step-by-step guidance' and 'Generates production-ready code' describe capabilities without demonstrating them. There are no Redis commands, connection examples, or caching patterns.	1 / 3
Workflow Clarity	No workflow is defined. The skill mentions 'step-by-step guidance' but provides none. There are no sequences, validation steps, or processes for implementing Redis caching strategies.	1 / 3
Progressive Disclosure	The content is a flat, uninformative structure with no references to detailed documentation, examples, or related files. The sections present (Purpose, When to Use, etc.) contain no substantive content to organize.	1 / 3
	Total	4 / 12 Passed

Validation

69%

Warnings & errors only

Validation — 11 / 16 Passed

Validation for skill structure

Criteria	Description	Result
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_version	'metadata' field is not a dictionary	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
body_steps	No step-by-step structure detected (no ordered list); consider adding a simple workflow	Warning

	Total	11 / 16 Passed

Reviewed

22 days ago

Table of Contents

Activation 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.