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.
35
3%
Does it follow best practices?
Impact
91%
0.96xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/06-backend-dev/redis-cache-manager/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a title with boilerplate metadata rather than a functional skill description. It provides no concrete actions, no natural trigger terms beyond the skill name repeated, and no guidance on when Claude should select this skill. It would be nearly useless for skill selection in a multi-skill environment.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configures Redis connections, sets and retrieves cache keys, manages TTL policies, handles cache invalidation strategies, and monitors cache hit/miss rates.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about Redis setup, caching strategies, cache invalidation, TTL configuration, key-value storage, or session caching.'
Remove the duplicate trigger term ('redis cache manager' is listed twice) and expand with varied natural language terms users might use, such as 'Redis', 'cache', 'caching layer', 'cache expiration', 'Redis client'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names 'Redis Cache Manager' but provides no concrete actions. There is no mention of what specific operations it performs (e.g., setting/getting cache keys, configuring TTL, managing cache invalidation, connection pooling). | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explicit 'Use when...' clause and no description of capabilities beyond the skill name itself. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'redis cache manager' repeated twice. It misses natural user terms like 'caching', 'Redis', 'cache invalidation', 'cache keys', 'TTL', 'memcache', or 'key-value store'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Redis' provides some domain specificity that distinguishes it from generic caching or backend skills, but the lack of concrete actions means it could still overlap with other Redis-related or caching skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is essentially a placeholder template with no substantive technical content about Redis cache management. It contains no code, no commands, no patterns, no configuration examples, and no actionable guidance whatsoever. Every section repeats the phrase 'redis cache manager' without teaching Claude anything it doesn't already know.
Suggestions
Add concrete, executable code examples for common Redis caching patterns (e.g., cache-aside, write-through) in Python, Node.js, and Go with actual Redis client libraries.
Define a clear workflow for implementing a cache manager, including steps like connection setup, key naming conventions, TTL strategies, cache invalidation, and error handling with validation checkpoints.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill rather than teach the skill—these waste tokens on information Claude doesn't need.
Add specific configuration examples (e.g., Redis connection pooling, sentinel/cluster setup) and link to separate reference files for advanced topics like cache eviction policies or distributed caching patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content about Redis caching. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero concrete guidance—no code examples, no commands, no configuration snippets, no specific Redis patterns. The content only describes rather than instructs, offering nothing executable or copy-paste ready. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. There are no sequences, validation checkpoints, or any procedural guidance for implementing or managing a Redis cache. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive block with no meaningful structure. There are no references to detailed files, no layered organization, and the sections all convey the same vacuous information. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3e83543
- Reviewed
Table of Contents
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.