Content
75%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, token-efficient offensive-security skill with concrete probe commands, a variant matrix, a runnable PoC with explicit confirmation criteria, and defender guidance. The main gaps are an undefined helper command/placeholders in the probe steps and the absence of an explicit error-recovery loop when a suffix probe fails.
Suggestions
Replace the undefined 'diff_response_bodies' with a concrete command (e.g., a curl | diff one-liner) and show how $TARGET/$AUTH are set so both probe steps are copy-paste ready.
Add a feedback loop after step 2: if the unauthenticated replay misses or returns 404, iterate the §3 variant table and retry, converting the variants list into an explicit error-recovery path.
Move the dated 'Known exemplars' content into a separate reference file or a clearly framed context section to keep the main body evergreen.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and table/code-driven and assumes Claude's competence (no primer on what a CDN is), but has minor trimmable spots: 'This skill covers deception. Cache poisoning is a separate (overlapping) class' restates the bullets above it, and the 'Known exemplars' section carries dated bounty figures without an 'old patterns' framing. | 4 / 5 |
Actionability | Mostly executable guidance: copy-paste curl probes with headers to inspect, a runnable Python PoC with asserts, a variant path table, and concrete nginx/Cloudflare defender config. Minor gaps: 'diff_response_bodies' is an undefined helper command, $TARGET/$AUTH are never defined, and the referenced probe site is unverifiable. | 4 / 5 |
Workflow Clarity | Clear two-step probe sequence with explicit validation checkpoints (X-Cache MISS→HIT, Content-Length consistency, unauth replay confirmation, PoC asserts). Falls short of a 5 because there is no error-recovery loop — what to try when the second request misses or returns 404 (e.g., iterating the §3 variants) is only implicit. | 4 / 5 |
Progressive Disclosure | No bundle files exist; the ~110-line body is well-sectioned with a clearly signaled 'Cross-references' section pointing one level deep (though to corpus paths outside this bundle). Severity ratings and dated exemplar content are inlined rather than split into a reference file, leaving minor organization gaps. | 4 / 5 |
Total | 16 / 20 Passed |