CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

web-app-manifest

Use when reviewing templates, rendered HTML, or shared components related to Link a Web App Manifest for installability. Validate the final browser-facing markup, not just the source framework abstraction.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, lean single-rule skill: concrete quick-reference bullets, unambiguous Check/Fix/Explain/Code Review sections, and a properly deferred one-level reference that exists and carries the implementation detail. The main cost is the opening concept paragraph, which re-explains knowledge Claude already has and duplicates the reference file verbatim, plus a Fix step that leans on the reference for the executable manifest JSON.

Suggestions

Delete or drastically compress the opening paragraph — it explains PWA/manifest basics Claude already knows and duplicates references/rule.md's 'Why It Matters' section word-for-word.

Inline a minimal complete manifest.json (or explicitly point the Fix section at the example in references/rule.md) so the fix is copy-paste executable from the body alone.

DimensionReasoningScore

Conciseness

The opening paragraph — 'A Web App Manifest is the minimum requirement for a site to be installable as a Progressive Web App. Installed PWAs launch in their own window, appear in app switchers, and can receive push notifications. Even for non-PWA sites, the manifest improves...' — explains basic manifest/PWA concepts Claude already knows and duplicates the 'Why It Matters' section of references/rule.md verbatim. The rest (Quick Reference, Check/Fix/Explain/Code Review) is lean and directive, so this sits at 'mostly efficient with some unnecessary explanation' rather than a clear 4, since roughly a quarter of the body is trimmable padding counted twice across the bundle.

3 / 5

Actionability

The Quick Reference is concrete and near copy-paste: 'Link manifest.json with <link rel="manifest" href="/manifest.json">', 'Include name, short_name, icons (192px and 512px minimum), and start_url', 'Set display: standalone', 'Set theme_color'. It is not anchor 5 because the Fix step ('Create a minimal Web App Manifest with the required fields') lacks a complete inline manifest example — the executable JSON is deferred to references/rule.md — leaving minor gaps executable from the body alone.

4 / 5

Workflow Clarity

This is a simple, single-purpose review skill under 50 lines with unambiguous actions, so the simple-skill exception applies: 'Check if this HTML file has a Web App Manifest linked. If so, verify the manifest has all required fields for installability' provides the validation, 'Fix' the remediation, and 'Flag exact elements, attributes, and routes where the rendered HTML violates the rule' the review output. The operation is neither destructive nor batch, so no validation cap applies.

5 / 5

Progressive Disclosure

The body is a concise overview with a single, clearly signaled, one-level-deep reference — 'For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`' — and the referenced file exists and holds the full detail (complete examples, display-mode table, icon requirements, verification steps). Content is appropriately split between summary and reference, matching anchor 5; the small duplicated intro paragraph is penalized under conciseness rather than double-counted here.

5 / 5

Total

17

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with an explicit 'Use when' clause, concrete review targets, and a sharp what/scope distinction (rendered markup vs. framework abstraction). Its main gaps are missing natural synonyms (PWA, manifest.json) and no mention of the fix/create capability the skill also supports.

Suggestions

Add natural synonyms users would actually say — 'PWA', 'Progressive Web App', 'manifest.json', 'home screen' — to broaden trigger coverage.

Mention the fix capability (creating and linking a minimal manifest), not just review and validation, so the 'what' covers all the skill's modes.

Vary the 'reviewing templates, rendered HTML, or shared components' framing from sibling rule skills to reduce trigger competition among closely related HTML-review skills.

DimensionReasoningScore

Specificity

The description lists concrete, well-scoped actions — 'reviewing templates, rendered HTML, or shared components' and 'Validate the final browser-facing markup, not just the source framework abstraction' — with specific objects and a clear scope distinction. It stays at 4 rather than 5 because it covers only review/validation and omits the fix/create capability the skill body actually provides.

4 / 5

Completeness

Both questions are answered explicitly and concretely: 'Use when reviewing templates, rendered HTML, or shared components related to Link a Web App Manifest for installability' gives the 'when' with specific trigger surfaces, and 'Validate the final browser-facing markup, not just the source framework abstraction' gives the 'what' with scope. This matches the anchor-5 example pattern of an explicit 'Use when' clause plus a clear capability statement.

5 / 5

Trigger Term Quality

Good natural keywords are present: 'templates', 'rendered HTML', 'shared components', 'Web App Manifest', 'installability'. It falls short of anchor 5 because common synonyms and file-level terms users would naturally say — 'PWA', 'Progressive Web App', 'manifest.json', 'home screen' — are missing.

4 / 5

Distinctiveness Conflict Risk

'Link a Web App Manifest for installability' is a clear niche with distinct triggers, but the generic 'reviewing templates, rendered HTML, or shared components' scaffolding is shared by sibling HTML-review rules, creating minor overlap risk with closely related skills — fitting anchor 4 rather than the fully distinct anchor 5.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/web-app-manifest/SKILL.md

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.