CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

60

Quality

70%

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

Fix and improve this skill with Tessl

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

Quality

Content

57%

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

A well-organized, single-purpose review skill that correctly defers detail to a one-level reference file. Its weaknesses are the explanatory PWA intro and body-level guidance that describes rather than instructs, with verification left implicit.

Suggestions

Replace the PWA/manifest concept paragraph with a one-line rationale, or drop it — Claude already knows what a Web App Manifest and a PWA are.

Make the 'Check' section's verification explicit and concrete (e.g., confirm the <link rel="manifest"> tag exists in the rendered HTML and that name, short_name, icons (192/512), and start_url are present) rather than 'verify the manifest has all required fields'.

Add a small inline manifest.json snippet to the Fix section so the body is copy-paste ready, rather than only pointing to references for the full example.

DimensionReasoningScore

Conciseness

The intro paragraph explains concepts Claude already knows ('Installed PWAs launch in their own window, appear in app switchers, and can receive push notifications'), so while the Quick Reference bullets earn their place, the body includes unnecessary explanation that could be tightened.

2 / 3

Actionability

The Quick Reference gives concrete snippets ('<link rel="manifest" href="/manifest.json">', field list), but the Fix step ('Create a minimal Web App Manifest with the required fields') is abstract and the full manifest.json example is deferred to references, leaving incomplete concrete guidance in the body.

2 / 3

Workflow Clarity

The Check/Fix/Explain/Code Review sections provide a logical structure, but validation is implicit ('verify the manifest has all required fields for installability') with no concrete checkpoint, and it reads as parallel mode-guides rather than a sequenced workflow with explicit validation steps.

2 / 3

Progressive Disclosure

A concise overview with a well-signaled, one-level-deep pointer ('see references/rule.md') to a real, non-nested bundle file, matching the score-3 anchor for clear overview with easy navigation.

3 / 3

Total

9

/

12

Passed

Description

82%

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' trigger and concrete review/validate actions anchored to a specific niche. Its main weakness is the generic 'reviewing templates, rendered HTML, or shared components' opening, which is broad HTML-review territory and slightly blurs distinctiveness and action specificity.

DimensionReasoningScore

Specificity

Quotes two concrete actions with specific targets ('reviewing templates, rendered HTML, or shared components' and 'Validate the final browser-facing markup'), but the action repertoire is narrow compared to the multi-verb score-3 anchor, so it names domain and some actions without being comprehensive.

2 / 3

Completeness

Explicitly answers both: the 'when' via the 'Use when reviewing...' trigger clause and the 'what' via 'Validate the final browser-facing markup', matching the score-3 anchor with explicit triggers.

3 / 3

Trigger Term Quality

Includes natural developer terms users would actually say — 'templates, rendered HTML, shared components, Web App Manifest, installability' — giving good coverage rather than only 'some relevant keywords'.

3 / 3

Distinctiveness Conflict Risk

The 'Link a Web App Manifest for installability' niche is distinct, but the opening 'reviewing templates, rendered HTML, or shared components' is generic HTML-review boilerplate likely shared across sibling checklist skills, so it could still overlap with similar skills.

2 / 3

Total

10

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.