content-hash-cache-pattern
Cache expensive file processing results using SHA-256 content hashes — path-independent, auto-invalidating, with service layer separation.
Install with Tessl CLI
npx tessl i github:affaan-m/everything-claude-code --skill content-hash-cache-pattern83
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
50%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description excels at technical specificity and carves out a distinct niche for content-hash-based caching. However, it completely lacks trigger guidance ('Use when...') which is critical for Claude to know when to select this skill. The technical jargon may also miss natural user language patterns.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when caching file processing results, avoiding redundant computation, or when files may move but content stays the same'
Include more natural user terms alongside technical ones, such as 'avoid reprocessing', 'skip unchanged files', 'memoize file operations'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Cache expensive file processing results', 'SHA-256 content hashes', 'path-independent', 'auto-invalidating', 'service layer separation'. These are concrete technical capabilities. | 3 / 3 |
Completeness | Describes what it does (caching with content hashes) but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all. | 1 / 3 |
Trigger Term Quality | Includes some relevant technical terms like 'cache', 'SHA-256', 'content hashes', but uses jargon that users might not naturally say. Missing common variations like 'caching', 'file cache', 'avoid reprocessing', or 'memoization'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche: SHA-256 content-hash-based caching for file processing. The combination of 'content hashes', 'path-independent', and 'auto-invalidating' creates a distinct technical domain unlikely to conflict with other skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that demonstrates all the qualities of good documentation: concise, actionable, well-structured, and complete. It provides executable code, clear rationale for design decisions, and practical guidance on when to use (and avoid) the pattern. The anti-patterns section adds valuable guardrails.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing executable code without explaining basic concepts Claude already knows. Every section earns its place with practical implementation details. | 3 / 3 |
Actionability | Provides fully executable Python code throughout, including complete implementations for hashing, cache read/write, and the service layer wrapper. All code is copy-paste ready. | 3 / 3 |
Workflow Clarity | The service layer wrapper clearly shows the sequence: cache check → extraction → cache write. The pattern is straightforward with explicit logging for debugging, and corruption handling provides graceful degradation. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (Core Pattern, Key Design Decisions, Best Practices, Anti-Patterns, When to Use/Not Use). Content is appropriately structured for a self-contained skill without needing external references. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 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.