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 and category label with no substantive content. It fails to describe any concrete capabilities, lacks natural trigger terms users would use, and provides no guidance on when Claude should select this skill. It reads like auto-generated boilerplate rather than a useful skill description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configures Redis connections, implements cache-aside patterns, manages cache invalidation strategies, sets TTL policies, and handles cache warming.'
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 improving application performance with caching.'
Remove the duplicate trigger term 'redis cache manager' and replace with diverse natural language variations users might actually say, such as 'Redis', 'caching layer', 'cache expiry', 'cache miss', 'distributed cache'.
| 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 explanation of capabilities and no explicit 'Use when...' clause with trigger guidance. | 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', 'key-value store', 'cache expiration', 'TTL', or 'memcache'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Redis' and 'Cache' provides some domain specificity that distinguishes it from generic backend skills, but the lack of concrete actions means it could still overlap with other caching or Redis-related 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 is an empty shell with no substantive content. It consists entirely of generic meta-descriptions and trigger phrases without any actual Redis cache management guidance, code examples, configuration patterns, or workflows. It provides no value beyond what the skill's title already communicates.
Suggestions
Add concrete, executable code examples for common Redis caching patterns (e.g., cache-aside, write-through) in Python, Node.js, or Go with actual Redis client libraries.
Define a clear workflow for implementing a cache manager, including steps like connection setup, key strategy design, TTL configuration, and cache invalidation with validation checkpoints.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill rather than teaching Redis caching techniques.
Add specific configuration examples (e.g., Redis connection pooling, eviction policies, sentinel/cluster setup) and link to separate reference files for advanced topics like cache stampede prevention or distributed locking.
| 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. Claims like 'provides step-by-step guidance' and 'validates outputs' are stated but never demonstrated. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of vague descriptions with no references to detailed materials, no links to examples or advanced guides, and no meaningful structural organization of content. | 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
3076d78
- 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.