Name: testland/workbox-tests
Rating: 74.4 (1 reviews)
Author: testland

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`). Use when a project already ships a Workbox-built service worker and its recipe behavior needs pinning against refactors or a version upgrade.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

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

The body is highly actionable and well-structured: executable Vitest/Playwright examples, a sequenced six-step workflow with validation checkpoints, and clean one-level-deep reference split into references/recipe-tests.md. The only weakness is conciseness — pinned version/date and version-specific numbers sit inline rather than in a deprecated section, and a few caveats recur across sections.

Suggestions

Move the time-sensitive pin (Workbox v7.4.1, May 2026) and version-specific default numbers into a dedicated 'Pinned version'/'old patterns' block referenced once, instead of restating them in Steps, Anti-patterns, and Limitations.

Consolidate the repeated CDN/workbox-sw and __WB_MANIFEST caveats into a single Limitations entry and cross-reference it from the relevant steps to remove duplication.

Tighten the Anti-patterns table by merging the two cache-namespace naming rows that make the same cacheName-override point.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with concrete code and no basic-concept padding, but it carries inline time-sensitive facts (pinned 'Workbox v7.4.1 (released May 2026)' and version-specific default numbers) outside any deprecated/old-patterns section, and repeats several caveats across Steps, Anti-patterns, and Limitations — so it is not fully tight per the time-sensitivity penalty.	2 / 3
Actionability	Provides copy-paste-ready executable code (the Vitest `__WB_MANIFEST` spec, the Playwright `imageCache` cap test, the `workbox-window` event test, the cacheable-response gate) plus concrete install/run commands, matching the fully-executable anchor.	3 / 3
Workflow Clarity	A clearly sequenced six-step authoring flow with a runner-placement decision table and explicit validation checkpoints (e.g. `await page.waitForTimeout(500)` after async pruning, build-before-test gating), with the build step flagged as non-optional — meeting the clear-sequence-with-checkpoints anchor.	3 / 3
Progressive Disclosure	The body is a concise overview that splits the other five recipe templates into a clearly signaled, one-level-deep reference (`references/recipe-tests.md`, verified to exist), matching the clear-overview-with-well-signaled-references anchor.	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, complete, and distinctive: it enumerates concrete test/assertion actions across the Workbox package family and gives an explicit 'Use when' trigger scoped to already-shipped Workbox SWs. It avoids vague fluff and reads in third person.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'pin behavior of the named recipes', 'validate `workbox-precaching` manifest injection (`__WB_MANIFEST` revisioning)', 'assert `workbox-routing` route handler matches', 'assert ... plugin gates', 'verify the `workbox-window` ... events' — matching the score-3 anchor that lists several specific concrete actions.	3 / 3
Completeness	Clearly answers both what (the enumerated test/assertion actions) and when via the explicit 'Use when a project already ships a Workbox-built service worker and its recipe behavior needs pinning against refactors or a version upgrade.' clause.	3 / 3
Trigger Term Quality	Covers natural terms a user would say — 'Workbox-built service workers', 'recipes', 'pinning', 'refactors or a version upgrade' — plus the named recipe identifiers, giving good coverage of natural terms rather than only technical jargon.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche — Workbox-built service workers pinned against refactors/upgrades — and is explicit about being distinct from authoring skills, making it unlikely to trigger for the wrong skill.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Reviewed

3 days ago

Table of Contents

Discovery Implementation Validation