CtrlK
BlogDocsLog inGet started
Tessl Logo

tessl-labs/http-caching-strategy

HTTP caching for web APIs — Cache-Control headers, ETags, conditional requests,

88

25.00x
Quality

84%

Does it follow best practices?

Impact

100%

25.00x

Average score across 4 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Discovery

85%

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

This is a strong skill description that clearly defines its scope (HTTP caching for web APIs), lists specific concrete capabilities, and provides explicit trigger guidance for automatic application. The main weakness is that trigger terms lean heavily technical, which may miss users who describe their needs in simpler language.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'Cache-Control headers, ETags, conditional requests, Vary header, and no-store for sensitive data' - these are all distinct, concrete caching mechanisms.

3 / 3

Completeness

Clearly answers both what ('HTTP caching for web APIs' with specific mechanisms) AND when ('Apply AUTOMATICALLY whenever building any API endpoint that serves data') with explicit trigger guidance.

3 / 3

Trigger Term Quality

Includes relevant technical terms like 'HTTP caching', 'Cache-Control', 'ETags', 'API endpoint', but missing common user variations like 'caching responses', 'browser cache', 'HTTP headers', or simpler terms users might naturally say.

2 / 3

Distinctiveness Conflict Risk

Clear niche focused specifically on HTTP caching for APIs with distinct technical triggers (ETags, Cache-Control, Vary header) that are unlikely to conflict with other skills.

3 / 3

Total

11

/

12

Passed

Implementation

77%

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

This is a high-quality, actionable skill with excellent executable examples and clear workflow guidance for HTTP caching. The main weakness is length—the comprehensive coverage leads to some redundancy between the detailed sections, decision table, and checklist. The content would benefit from being more concise or split into a quick-reference overview with linked detailed guides.

Suggestions

Consider splitting into SKILL.md (quick reference with decision table and checklist) and CACHING-DETAILS.md (full explanations and examples) to improve progressive disclosure

Consolidate the 'Common Mistakes' section with the 'WRONG/RIGHT' examples earlier in the document to reduce repetition

DimensionReasoningScore

Conciseness

While the content is well-organized and avoids explaining basic concepts Claude knows, it's quite lengthy (~400 lines) with some repetition. The decision guide table and checklist partially duplicate information from the detailed sections, and some examples could be consolidated.

2 / 3

Actionability

Excellent actionability with fully executable TypeScript/Express code examples, specific header values, a comprehensive decision table mapping endpoint types to exact Cache-Control values, and copy-paste ready middleware patterns. Every directive is demonstrated with working code.

3 / 3

Workflow Clarity

Clear sequencing for implementing caching: the skill shows the problem first, then solutions organized by cache type, includes explicit validation via the checklist, and provides a decision guide for choosing the right approach. The ETag flow explicitly shows the conditional request handling sequence.

3 / 3

Progressive Disclosure

Content is well-structured with clear sections and a table of contents via headers, but everything is in one monolithic file. The verifiers are referenced at the end but the detailed content (400+ lines) could benefit from splitting advanced topics (ETag implementation, Vary header details) into separate reference files.

2 / 3

Total

10

/

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Reviewed

Table of Contents