CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pwa-installability

Use when auditing PWA readiness, adding an install prompt, or preparing a web app for submission to Microsoft Store or Google Play via PWA Builder.

Quality

73%

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/pwa-installability/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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-organized overview with exemplary progressive disclosure: the body stays lean and points to a single, real, well-structured reference file. Weaknesses are concentrated in the body itself — motivational padding in the intro, no executable check/fix steps, and no verification checkpoint closing the audit→fix loop.

Suggestions

Cut the intro's engagement statistics and general explanation of what installable PWAs are — Claude already knows this, and it saves ~3 lines of padding.

Add one executable check to the Check section (e.g., a Lighthouse 'installable-manifest' audit or DevTools Application > Manifest) so the audit can run without opening the reference.

Surface the reference's Verification section in the body (e.g., a 'Verify' bullet in Quick Reference) so the check→fix→verify loop is visible at the overview level.

DimensionReasoningScore

Conciseness

The opening paragraph pads with general knowledge and motivational claims — "Installable PWAs appear in the browser's address bar install prompt and in app stores" and "users who install spend 3× more time in the app on average" — that Claude neither needs nor can act on. The rest (Quick Reference bullets, task sections) is tight, so this is 'mostly efficient with some unnecessary explanation' rather than noticeably verbose.

3 / 5

Actionability

The Quick Reference gives concrete criteria ("a 192×192 and 512×512 icon", "maskable variant for Android", manifest fields "name, icons, start_url, and display", "responds with 200 when offline"), but the body contains no executable code or commands — "Check whether this site meets the PWA installability criteria" and "ensure a service worker is registered" state what to do, not how, and the how is deferred to the reference. Not 2 because the criteria are specific and checkable rather than high-level hints.

3 / 5

Workflow Clarity

The Check / Fix / Explain / Code Review sections imply a task flow and the Quick Reference is a checklist, but no sequence is made explicit and verification checkpoints are absent from the body — the reference's "## Verification" section (automated and manual checks) is never surfaced. This sits at 'steps listed but checkpoints missing or implicit', not 4 where most checkpoints would be present.

3 / 5

Progressive Disclosure

The body is a ~30-line overview with clear sections, and full details are cleanly deferred to a verified, one-level-deep reference — "see `references/rule.md`" — which exists on disk (192 lines, well-headered, no further nested references). This matches the anchor for a clear overview with well-signaled one-level-deep references and appropriately split content.

5 / 5

Total

14

/

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, trigger-focused description with concrete actions, named platforms, and an explicit 'Use when' clause that keeps conflict risk minimal. The main gap is the absence of a standalone third-person capability statement ('what'), and trigger terms for the underlying manifest/service-worker work are missing.

Suggestions

Lead with a third-person capability statement (e.g., 'Audits PWA installability criteria and fixes manifest, service worker, and icon issues.') before the 'Use when' clause so the 'what' is explicit.

Add natural trigger terms users would say, such as 'web app manifest', 'service worker', 'add to home screen', or 'make my app installable'.

DimensionReasoningScore

Specificity

Names three concrete actions — "auditing PWA readiness", "adding an install prompt", and "preparing a web app for submission to Microsoft Store or Google Play via PWA Builder" — with specific platforms and tooling. Not 5 because manifest, service worker, and icon work (core to the skill) are absent from the description; not 3 because it lists several specific actions rather than only 1-2.

4 / 5

Completeness

The "when" is explicitly and concretely answered via the "Use when" clause with three trigger scenarios, and the "what" is conveyed through the action gerunds (auditing, adding an install prompt, preparing for submission). Not 5 because the 'what' lacks its own declarative capability statement — it exists only inside the when-clause; not 3 because the 'what' is clearly stated through concrete actions, more than weakly implied.

4 / 5

Trigger Term Quality

Good natural keyword coverage: "PWA", "install prompt", "Microsoft Store", "Google Play", "PWA Builder" are phrases users would plausibly say. Not 5 because common variations like "manifest", "service worker", "add to home screen", or "make my app installable" are missing; not 3 because coverage goes well beyond 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers: "PWA readiness", "install prompt", and "submission to Microsoft Store or Google Play via PWA Builder" are unlikely to fire for a generic web-deployment or service-worker skill. Matches the anchor for a clear niche with minimal conflict risk.

5 / 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/pwa-installability/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.