Name: progressive-web-app
Rating: 68 (1 reviews)
Author: administrakt0r

progressive-web-app

Build Progressive Web Apps (PWAs) with offline support, installability, and caching strategies. Trigger whenever the user mentions PWA, service workers, web app manifests, Workbox, 'add to home screen', or wants their web app to work offline, feel native, or be installable.

Quality

83%

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

The canonical home for this skill is progressive-web-app in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

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

Highly actionable with complete executable code and a clear sequenced workflow plus shipping checklist. Weaknesses are token efficiency (re-explained basics) and progressive disclosure (everything inlined, no reference files) for a skill this long.

Suggestions

Trim the Overview's re-explanation of PWA pillars and HTTPS/service-worker basics — assume Claude's knowledge and keep only non-obvious platform quirks.

Move the full Workbox example and detailed Edge Cases & Platform Notes into reference files (e.g. references/workbox.md, references/platform-quirks.md) and link to them one level deep from the body.

Add an inline validation checkpoint after Step 4 (e.g. 'Verify: load the app with network throttled to Offline in DevTools and confirm the app shell + offline.html serve from cache') before the final shipping checklist.

Dimension	Reasoning	Score
Conciseness	Mostly efficient executable code, but the Overview re-explains PWA pillars (HTTPS, manifests, service workers) and some platform notes restate concepts Claude already knows; these could be trimmed without losing actionable value.	3 / 5
Actionability	Provides complete, copy-paste-ready code for manifest.json, index.html, app.js, sw.js (with cacheFirst/networkFirst/staleWhileRevalidate), and a Workbox example — fully executable and covering the common cases.	5 / 5
Workflow Clarity	Steps are clearly sequenced (Step 1–4) with a shipping checklist containing verification items (DevTools SW check, offline throttle, Lighthouse audit), but per-step validation checkpoints are not embedded inline in the build flow.	4 / 5
Progressive Disclosure	Well-sectioned structure, but all ~340 lines are inlined in a single file with no bundle/reference files; the full sw.js, Workbox section, and detailed edge cases could be split into one-level-deep references.	3 / 5
	Total	15 / 20 Passed

Description

95%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, well-targeted description that clearly states both capability and trigger conditions with natural phrasing and a distinct niche. The only minor gap is slightly less granular action verbs compared to the top anchor.

Dimension	Reasoning	Score
Specificity	"Build Progressive Web Apps (PWAs) with offline support, installability, and caching strategies" names the domain plus three concrete capabilities, but the single verb "Build" with attached features is slightly less granular than the anchor-5 list of distinct actions.	4 / 5
Completeness	Explicitly states what ("Build Progressive Web Apps... with offline support, installability, and caching strategies") and when (an explicit "Trigger whenever..." clause with concrete triggers), matching the anchor-5 example.	5 / 5
Trigger Term Quality	Covers "PWA, service workers, web app manifests, Workbox, 'add to home screen'," plus natural paraphrases ("work offline, feel native, or be installable") — comprehensive natural-term coverage with synonyms a user would actually say.	5 / 5
Distinctiveness Conflict Risk	PWA is a clear niche anchored by distinctive triggers (service workers, web app manifests, Workbox, add to home screen) with minimal overlap risk against other skills.	5 / 5
	Total	19 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/progressive-web-app/SKILL.md
Commit: 6c06908

Reviewed: ~9 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.