CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/cache-coherence-patterns-reference

Pure-reference catalog of cache-coherence patterns across the request path. Defines the five-tier cache stack (browser → CDN → reverse-proxy → application → data store), the per-tier cache-writing patterns (cache-aside, write-through, write-back, write-around, refresh-ahead), and the canonical invalidation strategies (TTL-only, event-driven purge, surrogate keys, version-tagged URLs, soft purge), plus an anti-pattern table and a worked multi-tenant coherence-test example. Deep detail - the RFC 9111 Cache-Control / Vary / ETag directive tables and the cross-tier coherence + per-tier test surface - lives in references/. Use for pattern selection, Cache-Control header design, and coherence audits; use a cache-key-collision check when the question is whether two requests in an existing system collide on a concrete key scheme. Consumed by redis-cache-tests, cdn-cache-purge-tests, varnish-test-vtc-syntax, browser-cache-control-tests, and the cache-key-collision check.

75

Quality

94%

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

Overview
Quality
Evals
Security
Files

Quality

Content

100%

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

A well-structured pure-reference skill: lean, token-efficient tables with no filler, concrete decision guidance and a worked coherence test, a clear sequenced workflow with a re-check checkpoint, and clean one-level-deep progressive disclosure into two real reference files. No notable weaknesses across the scored dimensions.

DimensionReasoningScore

Conciseness

The body is dense reference material (tables, lean prose) with no explaining of concepts Claude already knows; every section earns its place, matching the 'lean and efficient; assumes Claude's competence' anchor.

3 / 3

Actionability

As an instruction-only reference it gives concrete actionable guidance — specific headers (Cache-Control: private, Vary: Authorization, content-hash ETag) and a concrete Arrange/Act/Assert test — so absence of executable code is not penalized per the code_vs_instruction scoring note.

3 / 3

Workflow Clarity

'How to use this reference' is a clear 5-step sequenced process ending in an explicit checkpoint ('re-check the design against the Anti-patterns table'), and the worked example walks the four decisions then the test; no destructive/batch validation gap applies.

3 / 3

Progressive Disclosure

Clear overview file with well-signaled one-level-deep references to two real, descriptively-labeled reference files (rfc-9111-http-caching-directives.md, cross-tier-coherence-and-test-surface.md), with deep detail appropriately split out rather than inlined.

3 / 3

Total

12

/

12

Passed

Description

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.

A highly specific, third-person description that clearly states both capability and use triggers and stakes out a distinct niche. It is somewhat over-enumerated with internal pattern jargon and misses a few of the most natural user phrasings, which keeps trigger-term quality at the mid level.

Suggestions

Lead the 'Use for...' clause with the most natural user phrasings ('stale data after writes', 'cache invalidation', 'CDN purge') before the more technical catalog terms.

Trim the full inline enumeration of every pattern name from the description; the body and references already carry that detail and the list adds length without aiding triggering.

DimensionReasoningScore

Specificity

Lists multiple specific concrete capabilities ('Defines the five-tier cache stack', 'per-tier cache-writing patterns (cache-aside, write-through...)', 'canonical invalidation strategies (TTL-only, event-driven purge...)'), matching the anchor for listing multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ('Pure-reference catalog... Defines...') and when ('Use for pattern selection, Cache-Control header design, and coherence audits'), with explicit trigger guidance, satisfying the highest anchor.

3 / 3

Trigger Term Quality

Includes some natural triggers ('Use for pattern selection, Cache-Control header design, and coherence audits'), but the description is heavy on internal catalog jargon (surrogate keys, version-tagged URLs, refresh-ahead) and omits common user phrasings like 'stale data', 'cache invalidation', or 'CDN purge'.

2 / 3

Distinctiveness Conflict Risk

Occupies a clear niche ('cache-coherence patterns across the request path') and is explicitly consumed by distinct per-tier test skills, making it unlikely to trigger for the wrong skill.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents