content-hash-cache-pattern

Cache expensive file processing results using SHA-256 content hashes — path-independent, auto-invalidating, with service layer separation.

1.44x

Quality

52%

Does it follow best practices?

Impact

100%

1.44x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/content-hash-cache-pattern/SKILL.md

Quality

Discovery

40%

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 identifies a clear technical niche (content-hash-based caching for file processing) with distinctive architectural details, but it reads like a feature list for a library rather than a skill selection guide. It lacks a 'Use when...' clause and natural trigger terms that would help Claude know when to select it, and the language is heavily technical rather than user-oriented.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when implementing caching for file processing, avoiding redundant computation, or when the user mentions memoization, caching results, or performance optimization for repeated file operations.'

Include natural trigger terms users might say, such as 'speed up file processing', 'avoid reprocessing', 'cache results', 'memoize', or 'performance optimization'.

Reframe the description to lead with concrete actions: e.g., 'Implements content-hash-based caching to skip redundant file processing, stores and retrieves cached results by SHA-256 hash, and separates caching logic into a service layer.'

Dimension	Reasoning	Score
Specificity	Names the domain (caching file processing results) and mentions specific techniques (SHA-256 content hashes, service layer separation), but doesn't list multiple concrete user-facing actions — it reads more like an architectural description than a list of capabilities.	2 / 3
Completeness	Describes what the skill does (caching with content hashes) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also more architectural than actionable, warranting a 1.	1 / 3
Trigger Term Quality	Includes some relevant terms like 'cache', 'file processing', 'SHA-256', and 'content hashes', but these are fairly technical. Missing natural user phrases like 'speed up', 'avoid reprocessing', 'memoize', or 'performance optimization' that users might actually say.	2 / 3
Distinctiveness Conflict Risk	The combination of SHA-256 content hashing, path-independent caching, and service layer separation is quite specific and unlikely to conflict with other skills. This describes a clear, narrow niche.	3 / 3
	Total	8 / 12 Passed

Implementation

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid, actionable skill with excellent executable code examples covering the complete content-hash caching pattern. Its main weaknesses are moderate redundancy across sections (When to Activate vs When to Use, inline rationale vs design decisions table) and lack of explicit validation/verification steps for cache operations. The pattern is well-explained but could be tightened by ~30% without losing clarity.

Suggestions

Merge 'When to Activate' and 'When to Use/When NOT to Use' into a single concise section to eliminate redundancy.

Remove the 'Key Design Decisions' table since each rationale is already explained inline next to the relevant code.

Add a validation checkpoint after cache writes (e.g., read-back verification) or at minimum note when validation is unnecessary, to strengthen workflow clarity for batch processing scenarios.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with good code examples, but includes some redundancy: 'When to Activate' and 'When to Use' sections overlap significantly, the 'Key Design Decisions' table repeats rationale already explained inline, and some best practices restate what the code already demonstrates (e.g., chunking, corruption handling).	2 / 3
Actionability	Provides fully executable Python code for every component: hashing, cache entry dataclass, read/write operations, and the service layer wrapper. Anti-patterns with concrete bad examples add further clarity. The code is copy-paste ready and covers the complete pattern.	3 / 3
Workflow Clarity	The service layer wrapper implicitly shows the workflow (hash → check cache → extract → store), but there's no explicit validation step for verifying cache integrity after writes, no guidance on cache cleanup/eviction, and no feedback loop for handling edge cases like disk-full scenarios or race conditions in concurrent access.	2 / 3
Progressive Disclosure	The content is well-structured with clear headers and logical sections, but it's a monolithic document (~130 lines of substantive content) with no references to external files. The design decisions table and anti-patterns could be separated. However, given no bundle files exist, the inline approach is somewhat justified for a self-contained skill.	2 / 3
	Total	9 / 12 Passed

Validation

90%

Warnings & errors only

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

Repository: affaan-m/everything-claude-code
Commit: 841beea

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

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.