content-hash-cache-pattern

Cache expensive file processing results using SHA-256 content hashes — path-independent, auto-invalidating, with service layer separation. Use when repeated file processing is slow and results should be cached and invalidated by content rather than path.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%Weight 40%Scale 1-5

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

A high-quality, code-dense skill body with fully executable examples, clear design rationale, and useful anti-patterns. The main weaknesses are mild redundancy across the multiple when-to-use sections and a monolithic structure that keeps everything inline.

Suggestions

Consolidate the three overlapping trigger sections ('When to Activate', 'When to Use', and the description) into a single 'When to use' block to remove redundancy.

Drop the 'Key Design Decisions' table or trim it to decisions not already justified by inline code comments and the 'Why content hash?' note.

If the skill grows, move the extended anti-patterns or serialization details into a references/ file and link to it one level deep to better exercise progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly lean code-first content that assumes Claude's Python competence, with minor redundancy: trigger guidance is repeated across 'When to Activate', 'When to Use', and the description, and the Key Design Decisions table re-states rationale already implicit in the code comments.	4 / 5
Actionability	Fully executable, copy-paste-ready implementations for every component (compute_file_hash, CacheEntry, write_cache, read_cache, extract_with_cache), plus concrete anti-patterns showing exactly what to avoid.	5 / 5
Workflow Clarity	The service-layer wrapper lays out a clear runtime sequence (check cache -> extract -> store) with a graceful-corruption feedback path (invalid JSON returns None -> reprocess), but it is presented as a pattern catalog rather than an explicitly checkpointed workflow.	4 / 5
Progressive Disclosure	Well-organized into clearly labeled sections with no nested references, but the skill is monolithic (no bundle files, all content inline) and at ~155 lines exceeds the under-50-line simple-skill threshold that would let structure alone merit a 5.	4 / 5
	Total	17 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-structured description that explicitly states both what the skill does and when to use it, with concrete technical specifics and a distinct niche. Minor room to broaden trigger-term coverage with file-type synonyms.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete specifics ('SHA-256 content hashes', 'path-independent, auto-invalidating', 'service layer separation'), but the action set is essentially one capability (caching) with attributes rather than many distinct actions, leaving minor coverage gaps.	4 / 5
Completeness	Clearly answers both: the 'what' ('Cache expensive file processing results using SHA-256 content hashes... with service layer separation') and an explicit 'when' ('Use when repeated file processing is slow and results should be cached and invalidated by content rather than path').	5 / 5
Trigger Term Quality	Good natural keyword coverage with phrases users would say ('repeated file processing is slow', 'cached and invalidated by content'), though it lacks file extensions and common synonyms like '.pdf' or 'OCR'.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (content-hash-based caching with auto-invalidation and SRP service-layer separation) with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/content-hash-cache-pattern/SKILL.md
Commit: e04ea0b

Reviewed: 2 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.