CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/pwa-install-flow-tests

Test the Progressive Web App install flow (Web App Manifest validation, `beforeinstallprompt` event handling, installability criteria, install prompt UX). Covers desktop install badge, Android WebAPK minting, iOS Add to Home Screen, and the `appinstalled` event. Use when a site ships a `link rel="manifest"` and users must be able to install it - especially after a manifest, icon, or `start_url` edit that could silently drop install eligibility.

74

Quality

93%

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

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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

The body is concise and highly actionable with executable Playwright tests across the full install flow. Its main weaknesses are the absence of explicit validation checkpoints in the workflow and a lack of progressive disclosure into bundle files.

Suggestions

Add explicit validation checkpoints between steps (e.g. assert manifest criteria pass before proceeding to prompt capture, with a fix-and-retry note) to lift workflow clarity to a 3.

Split the larger Playwright test blocks or per-platform detail (e.g. iOS manual smoke-test procedure, display-mode emulation) into reference files linked from the overview to improve progressive disclosure.

Consider extracting the icon-size and manifest-field assertion helpers into a bundled script so the SKILL.md body stays a lean overview.

DimensionReasoningScore

Conciseness

Lean throughout: short framing prose, executable Playwright snippets, and tight per-step notes with no padding of concepts Claude already knows. Every section earns its place.

3 / 3

Actionability

Each step provides complete, copy-paste-ready Playwright/TypeScript test code with concrete selectors and assertions (e.g. link[rel="manifest"], icon size regexes, beforeinstallprompt capture), plus specific launch flags like --enable-features=InstallPromptForApp.

3 / 3

Workflow Clarity

Steps are numbered and sequenced with prerequisites noted (Step 2 before Step 3), but the flow lacks explicit validation checkpoints between steps; the prompt/capture path has no validate-then-fix feedback loop, capping clarity at 2 per the rubric.

2 / 3

Progressive Disclosure

Content is well-sectioned but it is a single monolithic SKILL.md with no bundle files and only one inline external link; the depth of inline code could warrant separation into reference files, landing at 'some structure but could be better organized'.

2 / 3

Total

10

/

12

Passed

Description

100%

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

The description is specific, trigger-rich, and clearly delineates both capabilities and use conditions with an explicit 'Use when' clause. It is well within the strong tier of the reference examples.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (manifest validation, beforeinstallprompt handling, installability criteria, install prompt UX) and enumerates platform-specific behaviors (desktop badge, Android WebAPK minting, iOS Add to Home Screen, appinstalled event), matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly answers both what (manifest validation, prompt handling, installability criteria, install prompt UX) and when via an explicit 'Use when a site ships a `link rel="manifest"`...' clause with concrete triggering conditions.

3 / 3

Trigger Term Quality

Includes natural terms users would say ('manifest', 'install', 'Add to Home Screen', 'WebAPK', 'beforeinstallprompt', 'appinstalled') plus the explicit `link rel="manifest"` trigger, giving good coverage of natural phrasings.

3 / 3

Distinctiveness Conflict Risk

The PWA install-flow niche is narrow and bounded by very specific triggers (`link rel="manifest"`, installability after a manifest/icon/start_url edit), making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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

Reviewed

Table of Contents