CtrlK
BlogDocsLog inGet started
Tessl Logo

playwright-ux-ui-capture

Capture EdgeQuake WebUI routes with Playwright and write artifacts immediately (screenshots + per-page request JSON + capture index). Use when adding/updating Playwright E2E capture specs or when asked to automate UI screenshot collection.

70

Quality

86%

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

72%

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

A well-organized, concise capture spec that points to a real helper script and gives concrete commands. It is held back by a missing executable Playwright spec example, an un-bundled referenced template, and no explicit validation checkpoint in the per-route capture loop.

Suggestions

Add a copy-paste-ready minimal Playwright spec snippet showing the capture pattern for one route (goto, wait for the 'page ready' signal, screenshot at each viewport) so the guidance is fully executable.

Bundle the referenced request JSON template (or inline its required shape) so 'write/update from the template' is actionable rather than pointing to a missing file.

Insert an explicit validation step in the write-out workflow (e.g. assert the screenshot file exists and is non-empty, and that the request JSON parses) before appending the capture-index line, turning the batch loop into a validate -> fix -> retry feedback loop.

DimensionReasoningScore

Conciseness

The body is lean and token-efficient: short sections, concrete values, and no explanation of concepts Claude already knows, so every line earns its place.

3 / 3

Actionability

Concrete run commands and exact viewport values are present, but there is no copy-paste-ready Playwright spec example, and 'write/update from the template' references a template file that is not bundled, leaving a key detail incomplete.

2 / 3

Workflow Clarity

The per-route write-out is a clear numbered sequence with 404/auth handling, but this batch operation lacks an explicit validation checkpoint (e.g. verify screenshot written / JSON valid) before appending the capture-index line, which caps it at 2.

2 / 3

Progressive Disclosure

The body is an overview that signals a single one-level-deep reference to a real bundled script (scripts/derive_routes.mjs, verified present), with content appropriately split and easy to navigate.

3 / 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.

A strong, third-person description that pairs concrete capabilities with an explicit 'Use when' trigger and a distinct niche. It is concise yet specific, with no notable fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Capture EdgeQuake WebUI routes', 'write artifacts immediately (screenshots + per-page request JSON + capture index)'), matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what it does and when to use it via the 'Use when adding/updating Playwright E2E capture specs or when asked to automate UI screenshot collection' clause.

3 / 3

Trigger Term Quality

Includes natural terms a user would say ('Playwright E2E capture specs', 'automate UI screenshot collection') alongside the technical artifact names, giving good coverage of likely trigger phrasings.

3 / 3

Distinctiveness Conflict Risk

The Playwright UI-capture niche with immediate artifact write-out is clearly distinguishable from other skills and unlikely to trigger for the wrong skill.

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

Repository
raphaelmansuy/edgequake
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.