redis-development
Redis performance optimization and best practices. Use this skill when working with Redis data structures, Redis Query Engine (RQE), vector search with RedisVL, semantic caching with LangCache, or optimizing Redis performance.
Install with Tessl CLI
npx tessl i github:redis/agent-skills --skill redis-development85
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%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 is a solid skill description with excellent trigger term coverage and clear 'Use when' guidance. The main weakness is the vague capability statement ('performance optimization and best practices') which doesn't specify concrete actions Claude can perform. The description would benefit from listing specific operations like configuring indexes, designing key schemas, or troubleshooting slow queries.
Suggestions
Replace 'performance optimization and best practices' with specific concrete actions like 'configure indexes, design key schemas, troubleshoot slow queries, optimize memory usage'
Add more specific capability verbs to clarify what Claude can actually do (e.g., 'Analyzes Redis configurations, recommends indexing strategies, debugs query performance')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Redis) and mentions specific technologies (RQE, RedisVL, LangCache), but 'performance optimization and best practices' is vague and doesn't list concrete actions like 'configure TTL policies' or 'design key schemas'. | 2 / 3 |
Completeness | Clearly answers both what ('Redis performance optimization and best practices') and when ('Use this skill when working with Redis data structures, Redis Query Engine...') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'Redis', 'vector search', 'RedisVL', 'semantic caching', 'LangCache', 'Redis Query Engine', 'RQE', and 'Redis performance' are all terms users working with Redis would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Redis with distinct product names (RedisVL, LangCache, RQE) that are unlikely to conflict with other database or caching skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels as an index/reference document with excellent organization, concise presentation, and clear progressive disclosure to detailed rule files. However, it functions more as a table of contents than a standalone skill - it lacks any concrete code examples or executable guidance in the main file, requiring users to always navigate to external files for actionable content.
Suggestions
Add 2-3 high-impact code examples directly in the main file (e.g., a quick HNSW index creation, a pipelining example) so the skill provides immediate value without requiring file navigation
Include a brief 'Common Pitfalls' section with concrete anti-patterns and their fixes to make the skill more actionable standalone
Add validation/verification guidance for critical operations like index creation or memory configuration changes
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-organized, using tables and bullet points efficiently. It avoids explaining what Redis is or basic concepts Claude already knows, focusing purely on actionable reference material. | 3 / 3 |
Actionability | While the skill provides excellent organization and categorization of rules, it lacks concrete code examples or executable commands in the main file. It relies entirely on external rule files for actual implementation details. | 2 / 3 |
Workflow Clarity | The 'When to Apply' section provides clear triggers, and the priority table helps with sequencing decisions. However, there are no explicit validation steps or feedback loops for implementing these optimizations. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear overview, well-organized categories, and explicit one-level-deep references to individual rule files. The navigation is intuitive with the 'How to Use' section explaining where to find detailed content. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.