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 well-crafted skill description that excels across all dimensions. It provides specific capabilities, includes natural trigger terms users would actually use, explicitly states both what the skill does and when to use it, and carves out a distinct niche in the PWA domain that won't conflict with general web development skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'service workers, web manifest, offline support, installation prompts' and specific use cases like 'installable web apps, offline functionality, push notifications'. | 3 / 3 |
Completeness | Clearly answers both what (PWAs with service workers, manifest, offline support, installation prompts) AND when with explicit 'Use for...' clause covering both feature requests and error scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Progressive Web Apps', 'service workers', 'offline', 'push notifications', 'manifest', 'cache strategy', plus error-related triggers like 'service worker registration' errors. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on PWA technology with distinct triggers like 'service worker', 'manifest configuration', 'installable web apps' that are unlikely to conflict with general web development skills. | 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 skill with excellent code examples that are immediately usable. The main weaknesses are the lack of explicit implementation sequence and missing validation/debugging guidance for common service worker issues. For a topic with multiple interconnected components, clearer workflow ordering would help.
Suggestions
Add a brief implementation sequence at the top (e.g., '1. Add manifest 2. Register service worker 3. Test offline 4. Add install prompt')
Include service worker registration code with error handling: navigator.serviceWorker.register() with .catch() for debugging
Add a troubleshooting section or link for common issues (service worker not updating, cache invalidation, HTTPS requirements)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only essential code examples without explaining what PWAs are or how browsers work. Every section delivers actionable code without padding. | 3 / 3 |
Actionability | All code examples are fully executable and copy-paste ready - complete manifest JSON, working service worker with cache strategy, install prompt handling, and push notification subscription code. | 3 / 3 |
Workflow Clarity | While individual components are clear, there's no explicit sequence for implementing a PWA (e.g., 'first add manifest, then register service worker'). The checklist helps but lacks validation steps or error handling guidance for service worker registration failures. | 2 / 3 |
Progressive Disclosure | Content is well-organized into logical sections, but for a topic this broad (service workers, caching, push notifications, installation), some content could be split into separate reference files. No links to advanced topics like cache invalidation strategies or debugging service workers. | 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
90d6bd7
- 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.