pwa-development

Progressive Web Apps - service workers, caching strategies, offline, Workbox

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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 with extensive copy-paste-ready code, but it is a long monolithic reference that re-explains basic PWA concepts and lacks progressive disclosure via separate reference files. Tightening redundancy and splitting advanced material into referenced files would raise the weaker dimensions.

Suggestions

Move the advanced/reference material — the full enhanced manifest, framework-specific guides (Next.js/CRA/Vite), and per-strategy caching code — into separate files under references/ and link to them from SKILL.md to improve progressive disclosure and reduce token load.

Cut the "Three Pillars of PWA" ASCII box and other basic concept explanations (what HTTPS and a service worker are) that Claude already knows, and remove the duplicated manifest/caching-strategy presentations, keeping one canonical copy.

Add a short, explicitly sequenced build/verify workflow (e.g., add manifest → register SW → choose caching strategies → validate with Lighthouse → test offline) with inline validation checkpoints to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is code-heavy and actionable, but it explains basics Claude already knows (the "Three Pillars of PWA" box on HTTPS/service-worker/manifest) and is redundant — the manifest appears three times and caching strategies appear as a table, a cheat sheet, and per-strategy code — so it could be tightened, matching the 2-anchor.	2 / 3
Actionability	It provides fully executable, copy-paste-ready code throughout — service worker lifecycle, every caching strategy, Workbox Vite and manual configs, background sync, push, and the install prompt — plus concrete commands, matching the 3-anchor for fully executable guidance.	3 / 3
Workflow Clarity	The lifecycle is sequenced and testing checklists plus a service-worker update feedback loop exist, but the skill is structured as a reference catalog rather than a cohesive validated multi-step build workflow, so checkpoints are implicit and segregated to the testing section, matching the 2-anchor.	2 / 3
Progressive Disclosure	All content sits in one ~950-line monolithic SKILL.md with no bundle files and no external references; it is well-sectioned, but material that could be split (the enhanced manifest, framework guides, full per-strategy caching code) is inline, matching the 2-anchor for content that should be separate being inline.	2 / 3
	Total	9 / 12 Passed

Description

82%

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 concise, concrete, and uses strong natural trigger terms within a clearly distinct PWA niche. Its only weakness is the absence of an explicit "Use when..." clause inside the description field itself, which keeps completeness at 2.

Suggestions

Add an explicit "Use when..." clause directly to the description field (e.g., "Use when building PWA features such as service workers, caching, or offline support") so the trigger guidance is self-contained rather than relying on the separate when-to-use field.

Consider including the common abbreviation "PWA" in the description to capture an additional natural trigger term users frequently say.

Optionally name one or two more capabilities (e.g., push notifications, installability, web app manifest) to broaden coverage of what the skill does.

Dimension	Reasoning	Score
Specificity	The description names the PWA domain plus four concrete capabilities — "service workers, caching strategies, offline, Workbox" — listing multiple specific concrete items rather than vague language, matching the 3-anchor's listing of several concrete capabilities.	3 / 3
Completeness	It clearly states what the skill covers but the description field itself contains no "Use when..." clause; the trigger guidance lives in a separate when-to-use field, so per the guideline a missing explicit trigger in the description caps completeness at 2.	2 / 3
Trigger Term Quality	It includes natural terms users actually say — "Progressive Web Apps", "service workers", "caching", "offline", "Workbox" — giving good coverage of common trigger vocabulary, matching the 3-anchor.	3 / 3
Distinctiveness Conflict Risk	The PWA niche is clearly scoped with distinct triggers (service workers, Workbox, offline), making it unlikely to fire for unrelated skills, matching the 3-anchor for a clear niche.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (961 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: alinaqi/claude-bootstrap
Commit: 9dacc46

Reviewed: about 7 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.