CtrlK
BlogDocsLog inGet started
Tessl Logo

web-cache-poisoning

Unkeyed-input cache poisoning — X-Forwarded-Host/Scheme/Port, X-Original-URL, fat-GET, parameter cloaking, oversized-header DoS, and chains to stored-XSS / open redirect via shared caches.

69

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

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

A tight, highly actionable playbook with copy-paste commands, a clear detection-to-exploitation workflow, and an explicit validation checklist; the only gap is the absence of any progressive-disclosure file structure for deeper material.

DimensionReasoningScore

Conciseness

Lean and efficient — tables and executable code dominate; the one-line definition and brief cache-deception disambiguation are domain-specific and earn their place rather than padding general knowledge.

5 / 5

Actionability

Fully executable curl commands with cache-busting, a header-iteration loop, the two-request confirm-poisoning method, and concrete exploit payloads (stored-XSS, forced redirect, param cloaking) that cover the common cases.

5 / 5

Workflow Clarity

Numbered sections (detection → matrix → PoC → chains → tools → signatures) plus an explicit Decision Gate checklist and an escalate/downgrade branch; validation is present for this risky operation, so the destructive-cap does not apply.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections with a brief overview, but it is a single ~110-line file with no bundle files or one-level-deep references to split detail into, placing it just below the reference-structured anchor.

4 / 5

Total

19

/

20

Passed

Description

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

A highly specific, distinctive description that enumerates concrete techniques, but it omits an explicit 'Use when' trigger clause, leaving the 'when' only weakly implied within the description field itself.

Suggestions

Append an explicit 'Use when...' clause naming the trigger phrases (e.g., 'Use when testing shared caches / CDNs for unkeyed-input poisoning') so the description answers 'when' as well as 'what'.

Add a few natural synonyms users might say (e.g., 'CDN poisoning', 'cache-key injection') to broaden trigger coverage beyond the technical header names.

DimensionReasoningScore

Specificity

Lists multiple concrete techniques (X-Forwarded-Host/Scheme/Port, X-Original-URL, fat-GET, parameter cloaking, oversized-header DoS) plus exploitation chains, giving comprehensive coverage of the cache-poisoning domain.

5 / 5

Completeness

The 'what' is clear and detailed, but the description itself contains no 'Use when...' trigger clause — explicit when-guidance lives only in metadata.when_to_use, so completeness caps at 3.

3 / 5

Trigger Term Quality

Includes natural terms a pentester would say ('cache poisoning', 'stored-XSS', 'open redirect', 'DoS') alongside heavy technical jargon, but lacks synonyms and broader phrasings.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (unkeyed-input cache poisoning) with distinct, specific triggers and minimal overlap with other skills.

5 / 5

Total

17

/

20

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
PurpleAILAB/Decepticon
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.