CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/cache-key-discriminator-audit

Audits whether a cache key carries every discriminator the cached response actually depends on, so two requests that must not share a slot cannot collide. Ranks identity discriminators (tenant, user, authorization scope, plan tier) above presentation ones (locale, region, currency, feature flag), maps each missing discriminator to the data-exposure or wrong-content consequence it causes, classifies each key-and-value pair into a critical / high / medium severity band (including the Python lru_cache-on-an-instance-method trap), and writes the fix as a namespaced key builder plus the matching HTTP Vary header. Use when a cache key is being designed or changed, when a per-user or per-tenant response is about to be stored in a shared cache or CDN, or when investigating a report that one user or tenant saw another's data.

80

Quality

100%

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 high-quality, expert-calibrated skill body: concise, actionable, with a clear sequenced workflow and well-structured one-level-deep references. It avoids explaining basics Claude already knows and focuses on the non-obvious discriminator-audit defect model.

DimensionReasoningScore

Conciseness

Lean and expert-facing; assumes Claude's knowledge of HTTP/caching and spends tokens only on the non-obvious defect model, severity bands, and the lru_cache mechanism, all of which earn their place.

3 / 3

Actionability

Provides copy-paste-ready executable code (the namespaced cache_key builder, the Vary header block, before/after dashboard example) plus a concrete output-shape template and regression test guidance.

3 / 3

Workflow Clarity

The 'Deriving the required discriminator set' section gives a clear 6-step sequence with explicit tier-check and severity-classification checkpoints, and pairs every critical finding with a regression test (a validation/verification feedback loop).

3 / 3

Progressive Disclosure

SKILL.md is an overview that cleanly offloads the deep lru_cache mechanism and verbatim RFC/OWASP citations to two real, well-signaled one-level-deep reference files (references/lru-cache-trap.md, references/http-cache-directives.md), both confirmed present.

3 / 3

Total

12

/

12

Passed

Description

100%

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, specific description that clearly states what the skill does and when to use it, with concrete natural trigger terms. It distinguishes itself well from neighboring cache concerns.

DimensionReasoningScore

Specificity

Names many concrete actions (ranks identity discriminators above presentation ones, maps missing discriminators to consequences, classifies into severity bands, writes a namespaced key builder plus matching HTTP Vary header).

3 / 3

Completeness

Explicitly answers both what (audits and ranks discriminators, classifies severity, writes fixes) and when via 'Use when a cache key is being designed or changed, when a per-user or per-tenant response is about to be stored... or when investigating a report that one user or tenant saw another's data'.

3 / 3

Trigger Term Quality

Uses natural terms a user or engineer would say: 'cache key', 'per-user', 'per-tenant', 'shared cache', 'CDN', 'saw another's data'.

3 / 3

Distinctiveness Conflict Risk

A clear, narrow niche (cache-key discriminator auditing) with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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