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.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill progressive-web-app89
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 effectively communicates both capabilities and trigger conditions. It uses third person voice, lists specific technical features, and includes an explicit 'Use for' clause with both positive use cases and error scenarios. The terminology is appropriately technical for the target audience while remaining naturally searchable.
| 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 use cases and specific error scenarios (service worker registration, cache strategy, manifest configuration errors). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'PWA' implied through 'Progressive Web Apps', 'service worker', 'offline', 'push notifications', 'manifest', 'cache strategy', 'installation prompts' - these are terms developers naturally use when working with PWAs. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on PWA technology with distinct triggers like 'service worker', 'web manifest', 'offline support', 'installation prompts' - unlikely to conflict with general web development or other 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 reference 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 SW 3. Test offline 4. Add install prompt')
Include service worker registration code with error handling: navigator.serviceWorker.register() with .catch()
Add a troubleshooting section or link for common issues (SW 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 strategies, push notifications), 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
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 16 Passed | |
- 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.