pwa-development
Progressive Web Apps - service workers, caching strategies, offline, Workbox
50
39%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/pwa-development/SKILL.mdQuality
Discovery
37%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 essentially a comma-separated list of topic keywords with no verbs, actions, or usage guidance. While the trigger terms themselves are relevant and specific to the PWA domain, the lack of any stated capabilities or 'Use when...' clause makes it very weak as a skill selector among many options.
Suggestions
Add concrete action verbs describing what the skill does, e.g., 'Implements service workers, configures caching strategies, enables offline functionality, and sets up Workbox for Progressive Web Apps.'
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about making a web app work offline, setting up service workers, configuring PWA manifests, or implementing caching with Workbox.'
Consider including file types or related terms like 'manifest.json', 'sw.js', or 'web app manifest' to further improve trigger coverage and distinctiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists topic areas ('service workers, caching strategies, offline, Workbox') but does not describe any concrete actions. There are no verbs indicating what the skill actually does—it reads more like a tag list than a capability description. | 1 / 3 |
Completeness | There is no explicit 'what does this do' (no actions described) and no 'when should Claude use it' clause. It is essentially a list of keywords with no guidance on selection triggers, which per the rubric caps completeness and warrants a low score. | 1 / 3 |
Trigger Term Quality | The terms 'Progressive Web Apps', 'service workers', 'caching strategies', 'offline', and 'Workbox' are all natural keywords a user would mention when seeking help in this domain. Good coverage of common variations and specific technologies. | 3 / 3 |
Distinctiveness Conflict Risk | The mention of PWA-specific technologies like 'service workers', 'Workbox', and 'offline' provides some distinctiveness, but without concrete actions it could overlap with general web development or caching-related skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, executable code examples covering the full PWA landscape, which is its primary strength. However, it is severely bloated — it reads like comprehensive documentation rather than a focused skill file, explaining many concepts Claude already knows and inlining content that should be in separate reference files. The lack of progressive disclosure and the absence of a clear guided workflow with validation steps significantly reduce its effectiveness as a SKILL.md.
Suggestions
Reduce the main SKILL.md to a concise overview (~100 lines) covering core requirements, basic service worker, and strategy selection, then split detailed content into separate files like CACHING_STRATEGIES.md, WORKBOX.md, PUSH_NOTIFICATIONS.md, and TESTING.md with clear links.
Remove content Claude already knows: the offline.html full page, responsive image patterns, code splitting basics, explanations of what HTTPS/service workers are, and the exhaustive icon size list in the enhanced manifest.
Add an explicit step-by-step workflow for creating a PWA from scratch with validation checkpoints (e.g., 'After registering SW, verify in DevTools > Application > Service Workers before proceeding to caching setup').
Consolidate the two manifest examples into just the minimum required one, and move the enhanced manifest to a reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~600+ lines. Includes extensive content Claude already knows (what HTTPS is, what a service worker is, basic HTML/CSS for offline pages, responsive image patterns, code splitting). The 'Enhanced Manifest' with every possible icon size and the full offline.html page are unnecessary padding. Much of this is reference documentation, not skill-specific guidance. | 1 / 3 |
Actionability | All code examples are fully executable and copy-paste ready — service worker registration, caching strategies, Workbox configuration, push notifications, install prompts. Concrete commands for installation and framework-specific setup are provided. | 3 / 3 |
Workflow Clarity | The checklists (manifest checklist, testing checklist, before/after launch) provide good structure, and the service worker lifecycle is shown. However, there's no clear step-by-step workflow for building a PWA from scratch with validation checkpoints — it reads more like a reference than a guided process. No explicit 'validate then proceed' feedback loops for the build/deploy process. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content with no references to external files. Everything — manifest details, all caching strategies, offline handling, push notifications, performance optimization, framework guides, testing — is inlined into a single massive document. The content desperately needs to be split into separate files (e.g., CACHING.md, WORKBOX.md, PUSH.md) with a concise overview pointing to them. | 1 / 3 |
Total | 7 / 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 — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (962 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- alinaqi/claude-bootstrap
- Commit
d4ddb03
- 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.