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.

72

Quality

90%

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

87%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 tight, actionable, well-structured skill body that is lean and points to a single real helper script. Its main weakness is workflow clarity: the batch capture flow lacks an explicit validation/verification checkpoint before appending to the capture index.

Suggestions

Add an explicit verification step before appending to capture-index.jsonl, e.g. 'Verify all three screenshots (desktop/tablet/mobile) and the requests JSON exist on disk before appending the index line; on missing files, retry the route once'.

Turn 'Common failure handling' into a numbered validate→fix→retry loop (e.g. auth failure → capture /login → retry once → if still failing, write ok:false) so the feedback loop is explicit rather than implied.

Resolve the 'from the template' reference for ux_ui_map/requests/{page}.json by either inlining the template or linking to a bundled reference file.

DimensionReasoningScore

Conciseness

Lean and well-organized with no padding; it never explains concepts Claude already knows (Playwright, Next.js App Router) and every section earns its place.

5 / 5

Actionability

Provides concrete executable commands ('npm run test:e2e', 'npx playwright test e2e/<spec>.spec.ts'), exact viewport widths, specific file paths, and a numbered write-out procedure with a JSON example — copy-paste ready for the common cases.

5 / 5

Workflow Clarity

The artifact write-out steps are numbered and 'Common failure handling' gives error recovery, but this is a batch operation over many routes without an explicit validate/verify checkpoint before indexing, so the batch-operations validation cap of 3 applies.

3 / 5

Progressive Disclosure

Clear overview with a single well-signaled one-level-deep reference to scripts/derive_routes.mjs (a real, present file), no nested references, and content appropriately split into organized sections.

5 / 5

Total

18

/

20

Passed

Description

92%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, specific description that clearly states both capability and trigger conditions with minimal fluff. Trigger term coverage is good but could add a few more natural synonyms to reach the top anchor.

DimensionReasoningScore

Specificity

Names the domain and lists multiple concrete actions ('capture screenshots', 'per-page request JSON', 'capture index') with comprehensive artifact coverage, matching the anchor for listing several specific concrete actions.

5 / 5

Completeness

Explicitly answers both what ('Capture EdgeQuake WebUI routes...write artifacts immediately') and when ('Use when adding/updating Playwright E2E capture specs or when asked to automate UI screenshot collection') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('Playwright E2E capture specs', 'automate UI screenshot collection') that a user would say, but a few natural synonyms/extensions (e.g. '.spec.ts', 'screenshots') are absent, placing it just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (EdgeQuake WebUI Playwright capture) with distinct triggers, minimizing conflict risk with other skills.

5 / 5

Total

19

/

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.

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.