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

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/web-app-manifest/SKILL.md

Quality

Content

71%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.

The body is a well-structured overview that defers implementation detail correctly to a single, verified reference file. Its weaknesses are the introductory paragraph re-explaining well-known PWA concepts and the absence of validation checkpoints or mode-selection guidance in the Check/Fix workflow.

Suggestions

Trim or remove the intro paragraph explaining what installed PWAs do (own window, app switchers, push notifications) — Claude already knows this; keep at most one sentence of rationale.

Add a post-fix validation step to the Check/Fix workflow (e.g., re-verify the rendered HTML links the manifest and the manifest contains all required fields after edits).

Briefly state when to use each section (Check vs Fix vs Explain vs Code Review) so Claude can pick the right mode without guessing.

Dimension	Reasoning	Score
Conciseness	The body is generally lean, but the intro paragraph ("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 concepts Claude already knows — fitting anchor 3 ('Mostly efficient but includes some unnecessary explanation') rather than anchor 4, whose over-explanation is only minor.	3 / 5
Actionability	Quick Reference provides concrete, usable specifics — "<link rel=\"manifest\" href=\"/manifest.json\">", "icons (192px and 512px minimum)", "display: standalone", "theme_color" — with implementation detail appropriately deferred; minor gap is the Fix section ("Create a minimal Web App Manifest with the required fields") having no inline example, matching anchor 4.	4 / 5
Workflow Clarity	Check → Fix forms a clear sequence and Check's "verify the manifest has all required fields" acts as a checkpoint, but there is no post-fix re-validation step and the four mode sections (Check/Fix/Explain/Code Review) don't state when each applies — clear sequence with minor validation gaps, anchor 4 rather than 5.	4 / 5
Progressive Disclosure	A short, well-sectioned overview with one clearly signaled, one-level-deep reference — "see `references/rule.md`" (verified to exist and to contain the deferred code examples and framework guidance) — plus the upstream rule URL; this matches anchor 5 ('Clear overview with well-signaled one-level-deep references').	5 / 5
	Total	16 / 20 Passed

Description

78%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 and specific 'Use when' trigger clause and a clear, concrete statement of what the skill validates. Its main weaknesses are limited action coverage and the omission of common synonyms (manifest.json, PWA) alongside a somewhat generic opening clause shared with other HTML-review skills.

Dimension	Reasoning	Score
Specificity	Names the domain and two concrete actions — "reviewing templates, rendered HTML, or shared components" and "Validate the final browser-facing markup" — but stops short of the several specific actions of anchor 4, matching anchor 3 ('Names domain and 1-2 concrete actions, but not comprehensive').	3 / 5
Completeness	Explicitly answers both: 'what' via "Validate the final browser-facing markup, not just the source framework abstraction" and 'when' via "Use when reviewing templates, rendered HTML, or shared components related to Link a Web App Manifest" — concrete trigger phrases on both sides, matching anchor 5 rather than anchor 4's weaker, less specific 'when'.	5 / 5
Trigger Term Quality	Includes good natural keywords users would say ("templates", "rendered HTML", "shared components", "installability"), but misses common variations and synonyms such as "manifest.json", "PWA", or "progressive web app" — fitting anchor 4 ('Good keyword coverage; a few natural terms missing') rather than 5.	4 / 5
Distinctiveness Conflict Risk	Web app manifest installability is a clear niche, but the opening clause "reviewing templates, rendered HTML, or shared components" is generic across any HTML-review skill family, creating minor overlap risk with closely related sibling skills — anchor 4 rather than 5.	4 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/web-app-manifest/SKILL.md
Commit: 7bfd868

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.