CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/workbox-tests

Test Workbox-built service workers - pin behavior of the named recipes (`pageCache`, `staticResourceCache`, `imageCache`, `googleFontsCache`, `offlineFallback`, `warmStrategyCache`) per [developer.chrome.com/docs/workbox/modules/workbox-recipes][wb-recipes]; validate `workbox-precaching` manifest injection (`__WB_MANIFEST` revisioning); assert `workbox-routing` route handler matches; assert `workbox-expiration` and `workbox-cacheable-response` plugin gates; and verify the `workbox-window` registration helper events (`installed`, `waiting`, `controlling`, `activated`). Cache-strategy design (which strategy per route type, TTL + version-bump invalidation, migrating a hand-rolled sw.js to Workbox) lives in references/cache-strategy-design.md. Use when a project ships (or is adopting) a Workbox service worker and its strategy choices or recipe behavior need pinning against refactors or a version upgrade.

72

Quality

90%

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

86%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 well-structured, highly actionable testing skill with executable code throughout and clean progressive disclosure into two verified reference files. The main gaps are minor over-explanation of Workbox basics, a time-sensitive version pin outside a deprecated section, and no explicit test-failure feedback loop.

Suggestions

Move the pinned Workbox version (v7.4.1, May 2026) into a dedicated 'Versioning' note or a reference file so the time-sensitive pin stays out of the main flow and is easy to update on upgrade.

Trim inline restatements of what each Workbox package does (e.g. 'precacheAndRoute() is the entry point exported from workbox-precaching ... it precaches a file set', 'workbox-window is the page-side companion ...') — Claude knows these; keep only the test-relevant behavior.

Add an explicit feedback loop for failing recipe tests (e.g. a short symptom→cause→fix triage block, building on the existing Anti-patterns table) so the authoring workflow ends in a verify-and-recover step.

DimensionReasoningScore

Conciseness

The body is mostly lean code and tables, but it restates what each Workbox package does ('precacheAndRoute() is the entry point...', 'workbox-window is the page-side companion...') and pins v7.4.1 / May 2026 outside a deprecated/old-patterns section, which the rubric flags as a conciseness penalty.

4 / 5

Actionability

Provides copy-paste-ready, fully executable Vitest and Playwright specs plus install commands and CI YAML covering the common cases (precache manifest, imageCache cap, workbox-window events, cacheable-response gate).

5 / 5

Workflow Clarity

A clear six-step authoring sequence with a runner-selection table, explicit Running/CI sections, and an anti-patterns triage table; however it lacks an explicit fail→diagnose→fix feedback loop within the authoring workflow itself.

4 / 5

Progressive Disclosure

Acts as an overview keeping the representative tests inline and delegating cleanly to two real one-level-deep references (verified references/cache-strategy-design.md and references/recipe-tests.md), each well-signaled with markdown links.

5 / 5

Total

18

/

20

Passed

Description

92%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 strong, third-person description that names concrete actions across the entire Workbox testing surface and pairs them with an explicit, trigger-rich 'Use when' clause. Its only soft spot is a slight tilt toward Workbox jargon over user-natural synonyms in the trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across the full Workbox surface — 'pin behavior of the named recipes', 'validate workbox-precaching manifest injection', 'assert workbox-routing route handler matches', 'assert workbox-expiration and workbox-cacheable-response plugin gates', 'verify the workbox-window registration helper events' — matching the comprehensive-coverage anchor.

5 / 5

Completeness

Clearly states what the skill does and ends with an explicit 'Use when a project ships (or is adopting) a Workbox service worker and its strategy choices or recipe behavior need pinning against refactors or a version upgrade' — concrete trigger phrases for both what and when.

5 / 5

Trigger Term Quality

Good natural-term coverage ('Workbox service worker', 'recipe behavior', 'version upgrade', 'refactors', 'sw.js') but leans heavily on technical jargon (plugin/event names) rather than the full synonym set a user might say, so it sits just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear Workbox-only niche with distinct triggers (named recipes, __WB_MANIFEST, workbox-window events) and minimal overlap risk with the sibling service-worker skills it names.

5 / 5

Total

19

/

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

Reviewed

Table of Contents