CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/service-worker-lifecycle-tests

Use when a service worker needs lifecycle tests, users are stuck on an old version after deploy, or caching and offline behavior is untested. Tests each state change from installing to activated, waitUntil, skipWaiting and clients.claim, update() and a clean v1 to v2 upgrade with Playwright.

Quality

92%

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

92%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.

Excellent body content: a complete verified test spec, branch-on-inventory variants, an anti-patterns table, and failure triage with feedback loops, all backed by real one-level-deep reference files. The only room for improvement is trimming a few sentences that restate API semantics Claude already knows.

DimensionReasoningScore

Conciseness

Every section is an executable step, a decision table, or failure triage with no padded intro, but brief recaps of known concepts (the skipWaiting()/claim() semantics sentences and the shift-reload aside) could be trimmed or trusted to Claude, fitting 'efficient; minor instances of over-explanation'.

4 / 5

Actionability

The body provides a complete, verified ("15/15 passing serially on Chromium") copy-paste Playwright spec, a concrete inventory grep command, executable variant snippets for both skipWaiting/claim configurations, and specific re-run commands (--repeat-each=5), matching 'fully executable; copy-paste ready; covers the common cases'.

5 / 5

Workflow Clarity

Steps 1-7 are clearly sequenced with an inventory step that drives branching into the Step 4-5 variants, an explicit failure-triage table with a fix-and-retry feedback loop ("Fix the cause, re-run the single test with --repeat-each=5, then the whole file"), and a CI-gated coverage matrix, matching the anchor for explicit validation steps and error-recovery loops.

5 / 5

Progressive Disclosure

The body is a lean overview that keeps only the core spec (the skill's own deliverable) inline and pushes fixtures, the general harness, advanced recipes, and the coverage-matrix template into four real, one-level-deep reference files, each clearly signaled with what it contains and when to consult it.

5 / 5

Total

19

/

20

Passed

Description

88%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 description that explicitly pairs concrete 'what' actions with explicit 'use when' triggers in third-person voice, and captures the natural phrasing of users hit by stale-deploy bugs. The only weaknesses are a few missing natural synonyms (PWA, stale) and slight trigger overlap with sibling caching/offline test skills.

Suggestions

Add one or two common user synonyms such as "PWA" or "stale after deploy" to the trigger clause to broaden natural keyword coverage.

Narrow "caching and offline behavior is untested" (e.g., "lifecycle-related caching such as leftover v1 caches after an upgrade") to reduce overlap with sibling offline/cache-strategy test skills.

DimensionReasoningScore

Specificity

"Tests each state change from installing to activated, waitUntil, skipWaiting and clients.claim, update() and a clean v1 to v2 upgrade" lists multiple concrete, named actions covering the full lifecycle surface, matching the comprehensive anchor rather than the 'several actions, minor gaps' anchor.

5 / 5

Completeness

It explicitly answers 'when' with an 'Use when...' clause listing three concrete trigger scenarios, and 'what' with a clear statement of the tested behaviors, matching the anchor for both what and when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural user phrasing is present ("users are stuck on an old version after deploy", "caching and offline behavior is untested") alongside API keywords, but common synonyms like "PWA", "stale", or "not updating" are missing, so it fits 'good keyword coverage; a few natural terms missing' rather than comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The niche (service-worker lifecycle testing with Playwright) is distinct with specific triggers, but "caching and offline behavior is untested" overlaps with closely related sibling skills the body itself names (offline-fallback-tests, cache-strategy tests), so it fits 'mostly distinct; minor overlap risk' rather than minimal conflict risk.

4 / 5

Total

18

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

On this page