CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/browser-cache-control-tests

Wraps browser-side Cache-Control testing with Playwright (Cypress for legacy stacks): asserting response Cache-Control headers from Network events, ETag round-trips (If-None-Match → 304), service-worker strategies (Workbox cacheFirst / networkFirst / staleWhileRevalidate), and reload semantics (normal vs hard). Covers MDN Cache-Control + RFC 9111. Use when auditing browser-tier caching in E2E tests. For CDN-edge purge use cdn-cache-purge-tests; for the reverse-proxy tier use varnish-test-vtc-syntax; for an app-tier store use redis-cache-tests; SWR directive semantics live in stale-while-revalidate-reference.

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 well-structured, token-efficient skill body with executable Playwright examples, a clear numbered workflow, a worked example with failure semantics, and clean one-level-deep progressive disclosure into a real reference file. Anti-patterns and Limitations sections add practical guardrails without bloat.

DimensionReasoningScore

Conciseness

The body is lean: it links MDN/RFC 9111 rather than re-explaining Cache-Control basics, assumes Claude knows the browser ecosystem, and every code block and table row carries actionable information rather than padding.

3 / 3

Actionability

Provides fully executable TypeScript specs, a concrete run command ('npx playwright test cache-tests.spec.ts'), a CI yaml snippet, and a response-API method table — copy-paste ready with specific assertions rather than pseudocode.

3 / 3

Workflow Clarity

The 'How to use' section lays out a clear 7-step numbered sequence from picking the behaviour to assert through running the cross-browser matrix, and the worked example spells out exactly what each failing assertion would catch, giving a clear feedback path.

3 / 3

Progressive Disclosure

SKILL.md stays an overview and pushes deeper recipes (CDP from-cache detection, ETag round-trip, hard reload, service workers) to a clearly signaled, one-level-deep references/playwright-cache-recipes.md, which exists as a real file; the References section organizes external docs and sibling tools separately.

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 dense, specific description that names concrete capabilities, gives an explicit use-when trigger, and actively disambiguates from sibling cache-testing skills. It uses third person throughout and avoids fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'asserting response Cache-Control headers from Network events, ETag round-trips (If-None-Match → 304), service-worker strategies (Workbox cacheFirst / networkFirst / staleWhileRevalidate), and reload semantics (normal vs hard)' — matching the top anchor for listing several specific concrete actions.

3 / 3

Completeness

Clearly answers both 'what' (wraps browser-side Cache-Control testing with the four concrete assertion types) and 'when' via the explicit 'Use when auditing browser-tier caching in E2E tests' clause, matching the top anchor.

3 / 3

Trigger Term Quality

Includes natural, searchable terms a user would say — 'Cache-Control', 'browser cache', 'E2E tests', 'ETag', '304', 'service worker', 'Workbox' — alongside the explicit 'Use when auditing browser-tier caching in E2E tests' trigger, giving good coverage rather than just technical jargon.

3 / 3

Distinctiveness Conflict Risk

Carves a clear browser-tier niche and explicitly disambiguates from siblings ('For CDN-edge purge use cdn-cache-purge-tests; for the reverse-proxy tier use varnish-test-vtc-syntax; for an app-tier store use redis-cache-tests; SWR directive semantics live in stale-while-revalidate-reference'), making wrong-skill triggering unlikely.

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