CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/cdn-cache-purge-tests

Wraps CDN cache-purge testing patterns for Cloudflare (POST /zones/{zone_id}/purge_cache, single-file / everything / cache-tags / hostname / prefix), Fastly (POST purge-by-key / purge-all, surrogate-keys via Surrogate-Key header), and CloudFront (CreateInvalidation API + paths). Covers end-to-end test patterns (write origin → trigger purge → assert edge serves fresh), purge-propagation delay testing (typically 1-30s globally), surrogate-key + cache-tag patterns for group-purge, and Cache-Status header verification (cf-cache-status: HIT/MISS/BYPASS). Use when designing or auditing CDN cache-invalidation workflows.

76

Quality

95%

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

87%

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

The body is lean, highly actionable, and well-organized for a single-file skill, but its main worked example contradicts its own anti-pattern guidance on wait strategy, leaving a workflow-clarity gap.

Suggestions

Make the canonical end-to-end example poll cf-cache-status until MISS (with a timeout) instead of time.sleep(10), so it matches the Anti-patterns guidance it itself prescribes.

Define the purge_url() helper used in the multi-region example (or inline the purge call) so the snippet is fully executable rather than relying on an undefined function.

Add an explicit feedback loop for the purge-verify step (e.g., on failed assert, re-trigger purge / re-poll with backoff) since cache purging is a destructive batch operation on edge state.

DimensionReasoningScore

Conciseness

The body is dense with executable commands, code, and tables and avoids explaining concepts Claude already knows (no 'what is a CDN' preamble); nearly every token is concrete reference material.

3 / 3

Actionability

Provides copy-paste-ready curl, aws CLI, Python test functions, and CI YAML with real endpoints, headers, and asserts — concrete and executable rather than pseudocode.

3 / 3

Workflow Clarity

The canonical test has a numbered write→purge→verify sequence with asserts, but its wait step uses time.sleep(10), which the skill's own Anti-patterns section flags as wrong (fix: poll cf-cache-status until MISS), and the main example lacks that poll-until-MISS feedback loop.

2 / 3

Progressive Disclosure

A self-contained single file with clear, well-ordered sections (Overview, When to use, Authoring, Running, Parsing results, CI, Anti-patterns, Limitations, References) and one-level-deep external links plus named companion catalogs — no nested or dangling references.

3 / 3

Total

11

/

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.

The description is specific, well-triggered, and clearly scoped to CDN cache-purge testing with explicit 'Use when' guidance. It names concrete actions across three vendors without verbosity or over-claiming.

DimensionReasoningScore

Specificity

Lists multiple concrete actions per vendor — 'POST /zones/{zone_id}/purge_cache, single-file / everything / cache-tags / hostname / prefix', 'CreateInvalidation API + paths', 'surrogate-keys via Surrogate-Key header' — plus end-to-end and propagation-delay test patterns.

3 / 3

Completeness

Explicitly states both what it does ('Wraps CDN cache-purge testing patterns...') and when to use it ('Use when designing or auditing CDN cache-invalidation workflows.'), satisfying the explicit-trigger requirement.

3 / 3

Trigger Term Quality

Includes natural terms a user debugging stale content would say — 'CDN cache-purge', 'cache-invalidation workflows' — alongside the specific vendor/API vocabulary, giving good coverage of common phrasings.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (CDN cache-invalidation testing across Cloudflare/Fastly/CloudFront) with distinct triggers; written in third person ('Wraps...') with no first/second-person voice to penalize.

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