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 strong, vendor-specific testing skill: executable curl/pytest/CI examples, per-vendor purge recipes, explicit assert-per-step test sequences, and honest Limitations and Anti-patterns sections. It is held back from the top band by a bundle inconsistency (CI steps call scripts that are not shipped), an undefined purge_url helper in the multi-region example, and a sleep-vs-poll inconsistency between the canonical test and the anti-patterns table.
Suggestions
Ship scripts/write-test-fixture.sh and scripts/purge-test-paths.sh in the bundle, or replace the CI invocations with the inline curl/pytest commands already shown, so the CI block is runnable as written.
Define or inline the purge_url() helper used in test_purge_propagates_globally so the multi-region example is self-contained.
Replace the time.sleep(10) in the canonical test with the polling loop the anti-patterns table prescribes (poll cf-cache-status until MISS with a 30s timeout) so the example and the guidance agree, and merge the duplicated cf-cache-status tables into one.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dominated by executable commands, code, and tables ('curl -X POST "https://api.cloudflare.com/..."', the cache-status table, the anti-patterns table) and assumes Claude's competence, but has trimmable redundancy: cf-cache-status values are listed in both 'Cache-Status header verification' and 'Parsing results', and the Cloudflare purge-doc link appears both in the Overview and again in References. | 4 / 5 |
Actionability | Mostly executable guidance with concrete per-vendor curl commands, a runnable pytest example, and a CI YAML snippet, but two gaps keep it from copy-paste ready: the CI block invokes './scripts/write-test-fixture.sh' and './scripts/purge-test-paths.sh' which do not exist in the bundle, and the multi-region test calls an undefined 'purge_url(API, "/api/users/1")' helper. | 4 / 5 |
Workflow Clarity | The canonical test lays out a clear numbered 1-5 sequence (origin write -> verify old -> purge -> wait -> verify fresh) with an assertion at each stage, and the anti-patterns table adds body-comparison and polling guidance. Minor validation gap: the anti-patterns prescribe 'Poll cf-cache-status until MISS (timeout 30s)' yet the canonical code itself uses 'time.sleep(10)', and no polling/retry loop is actually shown. | 4 / 5 |
Progressive Disclosure | The two references files (references/browser-cache-control.md, references/playwright-cache-recipes.md) exist, are one level deep, and are well signaled with descriptions of what lives in them; browser-tier detail is appropriately split out of SKILL.md. However, the CI section references ./scripts/write-test-fixture.sh and ./scripts/purge-test-paths.sh, and no scripts/ directory exists in the bundle - a dangling referenced path. | 4 / 5 |
Total | 16 / 20 Passed |