pwa-manifest-generator
Pwa Manifest Generator - Auto-activating skill for Frontend Development. Triggers on: pwa manifest generator, pwa manifest generator Part of the Frontend Development skill category.
41
11%
Does it follow best practices?
Impact
99%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/05-frontend-dev/pwa-manifest-generator/SKILL.mdQuality
Discovery
22%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 description is essentially a placeholder that relies entirely on the skill name without providing meaningful detail about capabilities or usage triggers. It lacks concrete actions, comprehensive trigger terms, and explicit guidance on when Claude should select this skill. The duplicate trigger term suggests minimal effort in crafting the description.
Suggestions
Add specific actions the skill performs, e.g., 'Generates manifest.json files with app name, icons, theme colors, display modes, and start URL configuration for Progressive Web Apps.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user mentions PWA, progressive web app, manifest.json, web app manifest, installable web app, or add to home screen functionality.'
Add common file and technology references users might mention: '.webmanifest', 'service worker setup', 'app icons', 'splash screens'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Pwa Manifest Generator' without describing any concrete actions. It doesn't explain what generating a PWA manifest involves (e.g., creating icons, setting display modes, configuring start URLs). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just a repetition of the skill name rather than meaningful trigger guidance. No explicit 'Use when...' clause with actionable triggers. | 1 / 3 |
Trigger Term Quality | Includes 'pwa manifest generator' as a trigger term (duplicated), which is relevant but misses common variations users might say like 'web app manifest', 'manifest.json', 'progressive web app', 'add to home screen', or 'installable web app'. | 2 / 3 |
Distinctiveness Conflict Risk | The term 'PWA manifest' is fairly specific to a particular technology, reducing conflict risk with unrelated skills. However, the vague description could still overlap with general 'Frontend Development' or web configuration skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template that provides zero actionable guidance for PWA manifest generation. It contains only meta-descriptions of what the skill claims to do without any actual content, code examples, manifest schemas, or concrete instructions. Claude already knows what PWA manifests are; this skill adds nothing useful.
Suggestions
Add a complete, executable manifest.json example with all required and recommended fields (name, short_name, icons, start_url, display, theme_color, background_color)
Include icon size requirements and generation guidance (e.g., 192x192, 512x512 for maskable icons)
Provide validation steps or a checklist for PWA manifest completeness (e.g., Lighthouse PWA audit criteria)
Remove all meta-description content ('This skill activates when...', 'Capabilities include...') and replace with actual technical guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. It explains what triggers the skill and describes capabilities in abstract terms without any concrete information about PWA manifests. | 1 / 3 |
Actionability | No concrete code, commands, or examples are provided. The skill describes what it can do ('provides step-by-step guidance', 'generates production-ready code') but never actually does any of it. Zero executable content. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for generating a PWA manifest, no validation checkpoints, and no actual process to follow. The content is purely meta-description. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, no examples file, no schema reference. The content is a shallow placeholder with no depth to disclose. | 1 / 3 |
Total | 4 / 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
994edc4
- 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.