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.
36
3%
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
7%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 very weak description that essentially only provides the skill's name and category without explaining what it does or when to use it. It lacks concrete actions, meaningful trigger terms, and any explicit usage guidance. The only slight positive is that 'PWA manifest' is a somewhat distinctive domain.
Suggestions
Add concrete actions the skill performs, e.g., 'Generates manifest.json files for Progressive Web Apps, including app name, icons, theme colors, display mode, and start URL configuration.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about PWA setup, manifest.json, web app manifest, progressive web app configuration, add-to-home-screen, or making a website installable.'
Remove the duplicate trigger term and expand with natural variations users would actually say, such as 'web app manifest', 'manifest.json', 'installable web app', 'PWA icons'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Pwa Manifest Generator') and its category ('Frontend Development') but does not describe any concrete actions like generating manifest.json files, configuring icons, setting display modes, or specifying start URLs. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no explicit 'Use when...' clause explaining when Claude should select this skill. The 'Triggers on' line is just a repeated keyword, not meaningful guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'pwa manifest generator' repeated twice. It misses natural variations users would say like 'web app manifest', 'manifest.json', 'progressive web app', 'PWA setup', 'service worker', or 'add to home screen'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'PWA manifest' is fairly niche and unlikely to conflict with many other skills, but the lack of specificity about what it actually does (vs. other PWA-related skills) and the generic 'Frontend Development' category reduce its distinctiveness somewhat. | 2 / 3 |
Total | 5 / 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 with no actual instructional content. It repeatedly references 'pwa manifest generator' without ever explaining what a PWA manifest contains, how to generate one, or providing any code examples. It fails on every dimension because it contains zero actionable information.
Suggestions
Add a concrete, executable example of a complete manifest.json file with all required and recommended fields (name, short_name, icons, start_url, display, theme_color, background_color, etc.).
Provide a step-by-step workflow: 1) Create manifest.json with specific fields, 2) Link it in HTML via <link rel='manifest'>, 3) Validate using Chrome DevTools or a manifest validator tool.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill rather than teaching the task—replace with actual guidance and code.
Add common patterns and variations (e.g., different display modes, icon size requirements, maskable icons) with concrete examples rather than vague references to 'best practices'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It repeats 'pwa manifest generator' numerous times without providing any actual guidance, code, or useful content. Every section describes meta-information about the skill rather than teaching anything. | 1 / 3 |
Actionability | There is zero concrete guidance—no manifest.json example, no code snippets, no specific fields or values, no commands. The content only vaguely describes what the skill could do without actually doing it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The 'step-by-step guidance' is merely claimed in a bullet point but never provided. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive structure with no meaningful organization. There are no references to detailed files, no quick-start section, and no navigation to deeper content. The sections are boilerplate headers with no real content beneath them. | 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
3076d78
- 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.