caching-strategies
Implements Rails caching patterns for performance optimization. Use when adding fragment caching, Russian doll caching, low-level caching, cache invalidation, or when user mentions caching, performance, cache keys, or memoization.
Install with Tessl CLI
npx tessl i github:fernandezbaptiste/rails_ai_agents --skill caching-strategies90
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
100%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 an excellent skill description that follows best practices. It uses third person voice, lists specific concrete caching patterns, includes a comprehensive 'Use when...' clause with both action triggers and keyword triggers, and is clearly scoped to Rails-specific caching rather than generic performance optimization.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'fragment caching, Russian doll caching, low-level caching, cache invalidation' - these are distinct, named caching patterns rather than vague descriptions. | 3 / 3 |
Completeness | Clearly answers both what ('Implements Rails caching patterns for performance optimization') and when ('Use when adding fragment caching... or when user mentions caching, performance, cache keys, or memoization') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'caching', 'performance', 'cache keys', 'memoization', plus specific pattern names like 'Russian doll caching' and 'fragment caching' that Rails developers would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Rails caching patterns' as the clear niche. The specific Rails-focused terminology (Russian doll caching, fragment caching) and explicit trigger terms make it unlikely to conflict with general performance or non-Rails caching skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, comprehensive Rails caching skill with excellent actionability and conciseness. The code examples are production-ready and cover all major caching patterns. The main weaknesses are the monolithic structure (could benefit from progressive disclosure to separate files) and lack of explicit validation workflows for cache invalidation strategies.
Suggestions
Split advanced topics (HTTP caching, testing, monitoring) into separate reference files and link from a condensed main skill
Add explicit validation workflow for cache invalidation: e.g., '1. Invalidate cache → 2. Verify with Rails.cache.exist? → 3. Confirm fresh data loads'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting information in tables, code blocks, and bullet points without explaining concepts Claude already knows. Every section provides actionable content without unnecessary preamble. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples throughout. Configuration snippets, model code, controller code, and test examples are all complete and runnable. | 3 / 3 |
Workflow Clarity | While individual techniques are well-documented, the skill lacks explicit validation checkpoints for cache invalidation workflows. The checklist at the end is helpful but doesn't provide a clear sequence for implementing caching with verification steps. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear sections, but it's a monolithic document (~400 lines) that could benefit from splitting advanced topics (HTTP caching, testing, monitoring) into separate reference files with links from the main skill. | 2 / 3 |
Total | 10 / 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (513 lines); consider splitting into references/ and linking | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 9 / 11 Passed | |
- 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.