progressive-web-app
Progressive Web Apps with service workers, web manifest, offline support, installation prompts. Use for installable web apps, offline functionality, push notifications, or encountering service worker registration, cache strategy, manifest configuration errors.
93
89%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
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.
This is a strong skill description that clearly defines the PWA domain with specific capabilities, natural trigger terms, and explicit 'Use for...' guidance. It covers both positive use cases (building installable web apps, offline functionality) and error scenarios (service worker registration errors, manifest configuration errors), making it highly actionable for skill selection. The description is concise yet comprehensive with no fluff or vague language.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete capabilities: service workers, web manifest, offline support, installation prompts, push notifications, cache strategy, and manifest configuration. These are all distinct, actionable concepts within the PWA domain. | 3 / 3 |
Completeness | Clearly answers both 'what' (PWAs with service workers, web manifest, offline support, installation prompts) and 'when' with an explicit 'Use for...' clause covering use cases and error scenarios like service worker registration errors and cache strategy issues. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'installable web apps', 'offline functionality', 'push notifications', 'service worker registration', 'cache strategy', 'manifest configuration'. These are terms developers naturally use when working with PWAs. | 3 / 3 |
Distinctiveness Conflict Risk | PWA is a well-defined niche with highly specific trigger terms like 'service worker', 'web manifest', 'installation prompts', and 'cache strategy' that are unlikely to conflict with other web development skills. The domain is clearly scoped. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable PWA reference skill with clean, executable code examples and efficient use of tokens. Its main weaknesses are the lack of explicit workflow sequencing with validation checkpoints (e.g., how to verify service worker registration, test offline mode) and the absence of progressive disclosure to separate advanced topics like alternative cache strategies or debugging guidance into referenced files.
Suggestions
Add explicit workflow steps connecting the sections (e.g., '1. Add manifest.json and link it in HTML, 2. Register service worker, 3. Verify in DevTools > Application tab, 4. Test offline mode').
Include a brief debugging/validation section with commands or DevTools steps to verify service worker registration and cache population.
Consider referencing separate files for advanced topics like alternative cache strategies (network-first, stale-while-revalidate) and background sync to keep the main skill focused.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. It jumps straight into manifest configuration, service worker code, install prompts, and push notifications without explaining what a PWA is or how browsers work. Every section delivers concrete code with minimal prose. | 3 / 3 |
Actionability | All code examples are executable and copy-paste ready: a complete manifest.json, a full service worker with cache-first strategy, install prompt handling, and push notification subscription. Specific and concrete throughout. | 3 / 3 |
Workflow Clarity | The sections are logically ordered (manifest → service worker → install → push → checklist), but there's no explicit sequencing connecting them. The checklist is helpful but lacks validation steps—e.g., how to verify the service worker registered correctly, how to test offline behavior, or how to debug cache issues. For a multi-step process like PWA setup, explicit validation checkpoints are missing. | 2 / 3 |
Progressive Disclosure | The content is well-sectioned and not monolithic, but it includes substantial code blocks for multiple features (service worker, install prompt, push notifications) all inline. Cache strategies beyond cache-first, background sync, or advanced service worker patterns could be referenced in separate files. No external references are provided for deeper topics. | 2 / 3 |
Total | 10 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- secondsky/claude-skills
- Commit
88da5ff
- Reviewed
Table of Contents
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.