CtrlK
BlogDocsLog inGet started
Tessl Logo

content-hash-cache-pattern

使用 SHA-256 内容哈希缓存高昂的文件处理结果 —— 与路径无关、自动失效且服务层分离。

53

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/content-hash-cache-pattern/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%

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

A well-structured, mostly executable pattern with a clear workflow and graceful error recovery. Its main gaps are an undefined serialization helper that the skill itself emphasizes, and minor redundancy between the two when-to-use sections.

Suggestions

Provide the serialize_entry/deserialize_entry implementation (or a concrete worked example), since manual serialization is called out as a key design decision and a warned-about anti-pattern but never shown.

Merge the '何时激活' and '适用场景' sections into a single when-to-use list to remove the duplicated guidance and tighten token efficiency.

DimensionReasoningScore

Conciseness

The prose is lean and avoids explaining basic concepts, but the '何时激活' and '适用场景' sections duplicate when-to-use guidance, so it could be tightened further.

2 / 3

Actionability

Provides concrete, mostly executable code for hashing, read/write, and the service wrapper, but serialize_entry/deserialize_entry are called yet never defined — the manual serialization the skill highlights as a key decision is left incomplete.

2 / 3

Workflow Clarity

The extract_with_cache flow is a clear check→extract→store sequence with explicit corrupt-cache recovery (try/except → None → reprocess on next run), and the design-decisions table documents that feedback loop.

3 / 3

Progressive Disclosure

The skill is a single self-contained, well-sectioned document with no need for external reference files, and the sections are clearly organized for discovery.

3 / 3

Total

10

/

12

Passed

Description

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 conveys a clear, concrete capability with a distinctive technique, but it is jargon-leaning and omits any 'Use when...' trigger guidance, leaving it at the mid anchor across all dimensions. Adding explicit trigger terms and natural user phrasing would raise it substantially.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when building file-processing pipelines that reprocess the same files, or when adding --cache/--no-cache to a CLI', to satisfy the completeness trigger requirement.

Replace jargon-heavy phrasing with natural user keywords — mention concrete cases like 'PDF parsing', 'OCR', or 'text extraction' alongside 'SHA-256 content hash'.

List one or two concrete file types or use cases in the description to improve specificity and make the niche more distinct from generic caching skills.

DimensionReasoningScore

Specificity

Names a concrete technique ('SHA-256 内容哈希') and a single action ('缓存高昂的文件处理结果'), but does not list multiple distinct actions, so it stops short of the top anchor.

2 / 3

Completeness

Clearly answers WHAT the skill does, but has no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

Includes some natural terms ('缓存', '文件处理结果') but leans technical ('SHA-256 内容哈希', '服务层分离') and omits common user phrasings like PDF parsing or text extraction.

2 / 3

Distinctiveness Conflict Risk

The content-hash caching niche is fairly specific, yet without explicit triggers it could still overlap with more general caching or file-processing skills.

2 / 3

Total

8

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
xu-xiang/everything-claude-code-zh
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.