content-hash-cache-pattern

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

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./.kiro/skills/content-hash-cache-pattern/SKILL.md

Quality

Content

75%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.

The content is a well-structured, actionable design pattern with executable code and clear sequencing, held back only by a few undefined helper symbols, minor section redundancy, and a single-file layout that could split some material out.

Dimension	Reasoning	Score
Conciseness	The body is efficient with executable code and minimal over-explanation of concepts Claude already knows; the only trimmable redundancy is the overlap between the 'When to Activate' and 'When to Use' lists, keeping it just below a 5.	4 / 5
Actionability	Provides mostly executable, copy-paste-ready Python (compute_file_hash, CacheEntry, write_cache, read_cache, extract_with_cache) with minor gaps — serialize_entry/deserialize_entry, extract_text, ExtractedDocument, and logger are referenced but not defined.	4 / 5
Workflow Clarity	The Core Pattern is sequenced into clear numbered steps and the service-layer wrapper lays out cache-check -> extraction -> cache-write with graceful corruption handling; it stops short of explicit validate/retry checkpoints, so it does not reach 5.	4 / 5
Progressive Disclosure	Well-organized into clear sections with no nested references, but at ~155 lines all content lives in a single SKILL.md with no bundle files, leaving minor organization/splitting gaps relative to the score-5 anchor.	4 / 5
	Total	16 / 20 Passed

Description

58%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.

The description is specific and distinctive about a content-hash caching pattern, but it omits any explicit "Use when..." trigger guidance and leans on technical jargon over natural user phrases, capping completeness and trigger-term quality.

Suggestions

Append a 'Use when...' clause naming natural triggers, e.g. 'Use when building file processing pipelines, adding --cache/--no-cache to a CLI, or caching repeated PDF/image/text extraction.'

Soften jargon like 'service layer separation' and 'auto-invalidating' with plain-language equivalents users would actually say.

Add common synonyms/file-context terms (caching, file processing pipelines, repeated extraction) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions/mechanisms — "Cache expensive file processing results", "using SHA-256 content hashes", "path-independent, auto-invalidating", "service layer separation" — with only minor coverage gaps, fitting the score-4 anchor better than the fully comprehensive score-5 example.	4 / 5
Completeness	It clearly states the "what" (cache file processing results via content hashes) but provides no "Use when..." clause or equivalent trigger guidance in the description, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Relevant terms like "cache", "file processing", and "SHA-256 content hashes" appear, but technical jargon ("auto-invalidating", "service layer separation") dominates and common natural variations/synonyms a user would actually say are missing.	3 / 5
Distinctiveness Conflict Risk	The content-hash caching niche is mostly distinct from generic caching skills with minimal overlap risk, though the appended "service layer separation" phrase is broad enough to risk minor overlap with general architecture skills.	4 / 5
	Total	14 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

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

Reviewed: 1 day 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.