CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/offline-fallback-tests

Build-an-X workflow that emits the offline-fallback test suite. Walks the eight Jake Archibald offline recipes per [web.dev/articles/offline-cookbook][off-cookbook] (`Cache only`, `Network only`, `Cache, falling back to network`, `Cache and network race`, `Network falling back to cache`, `Cache then network`, `Generic fallback`, `Service Worker side templating`), maps each recipe to its assertion shape, layers the Workbox `offlineFallback()` recipe per [developer.chrome.com/docs/workbox/modules/workbox-recipes][wb-recipes], and pins the offline storage strategy (Cache Storage vs IndexedDB vs Storage Manager `persist()`/`estimate()`) per [web.dev/learn/pwa/offline-data][off-data]. Output: a Playwright spec file with one test per route's chosen recipe + a coverage matrix mapping recipes to URL patterns. Use when a route's SW caching behavior is being chosen or changed, or when a "doesn't work offline" report needs the failing route's recipe localized.

74

Quality

93%

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

85%

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

A strong, actionable skill body with executable Playwright tests, a clear sequenced workflow, and well-structured progressive disclosure to a real reference file. The main drag is conciseness: significant redundancy across the Step 1 matrix, Step 6 coverage matrix, worked example, and anti-patterns.

Suggestions

Collapse the overlap between Step 1's recipe-matrix YAML and Step 6's coverage-matrix YAML — derive the coverage matrix from Step 1 rather than re-listing routes and recipes a second time.

Trim the worked example, which re-derives the same recipe assignments already shown in Step 1; keep only the four-regression list as the payoff.

De-duplicate the anti-patterns table against the step text so each 'Fix' column points to a step instead of restating its guidance.

DimensionReasoningScore

Conciseness

The body is information-dense and assumes Claude's competence (no SW basics explained), but not every token earns its place: Step 1's recipe matrix and Step 6's coverage matrix overlap heavily, the worked example re-lists the same recipes, and the anti-patterns table repeats guidance already given in the steps.

2 / 3

Actionability

Provides fully executable, copy-paste-ready Playwright test code (e.g. the Cache only, Network only, Storage Manager persist, and offline.html tests) plus concrete YAML manifests — no pseudocode or vague direction.

3 / 3

Workflow Clarity

Six explicitly sequenced steps with a verification gate ('CI gates on every row having a passing spec') and a coverage matrix that closes the loop, plus an anti-patterns table that gives error-recovery guidance.

3 / 3

Progressive Disclosure

The two pole recipes are inline while the remaining six templates are cleanly offloaded to a real, one-level-deep [references/recipes.md] that contains exactly the templates referenced; navigation is clearly signaled.

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.

A highly specific, complete description with explicit 'what' and 'when' triggers and clear differentiation from sibling skills. Its only weakness is verbosity: the inline eight-recipe enumeration and three reference URLs pad the field beyond what the dimensions reward.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'emits the offline-fallback test suite', 'maps each recipe to its assertion shape', 'layers the Workbox offlineFallback() recipe', 'pins the offline storage strategy', and a concrete output ('a Playwright spec file with one test per route's chosen recipe + a coverage matrix').

3 / 3

Completeness

Explicitly answers both what ('Output: a Playwright spec file ... + a coverage matrix') and when ('Use when a route's SW caching behavior is being chosen or changed, or when a "doesn't work offline" report ...').

3 / 3

Trigger Term Quality

Includes natural trigger phrasing a user would say — 'doesn't work offline' report and 'a route's SW caching behavior is being chosen or changed' — alongside domain terms like offline-fallback and PWA caching.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — per-route offline-fallback test generation — and explicitly differentiates from the authoring skill sw-cache-strategy-author and the runtime skill workbox-tests, so it is unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

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