playwright-testing

Playwright E2E testing patterns, cross-browser configuration, page objects, and CI setup. Use when creating E2E specs, visual regression suites, or configuring Playwright in CI. Trigger terms: playwright, e2e, trace, page object, cross-browser

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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.

An excellent, lean reference catalog with fully executable commands and concrete configuration guidance. Its only real weakness is workflow clarity: it offers a menu of commands and a locator decision order rather than a sequenced, validated workflow for spec authoring and CI execution.

Suggestions

Add a short sequenced workflow for the most common task (e.g., 1. write spec under tests/e2e/{feature}/, 2. run npx playwright test --ui, 3. on failure inspect trace, 4. npx playwright show-report and confirm 0 failures) with an explicit validation checkpoint before considering the suite green.

Make the verification step first-class: pair the show-report command with an explicit "suite is green only when failures == 0" checkpoint so the validation is not just an inline comment.

Cross-link the locator-priority decision order into the spec-authoring workflow so the two are presented as one coherent sequence rather than separate reference sections.

Dimension	Reasoning	Score
Conciseness	The body is dense with non-obvious operational guidance and zero concept padding — every gotcha and command earns its place and assumes Claude's competence, matching the lean/efficient anchor.	5 / 5
Actionability	Copy-paste-ready bash commands with inline comments, concrete config keys (trace, forbidOnly, retries), and a real page.route mock example fully cover the common cases.	5 / 5
Workflow Clarity	The locator priority is a sequenced decision and show-report hints at verification ("verify 0 failures"), but there is no explicit multi-step workflow with validation checkpoints for tasks like authoring and running a spec suite.	3 / 5
Progressive Disclosure	A concise overview under 50 lines with well-organized sections and one-level-deep, clearly signaled references (testing-config.md, official Playwright docs), matching the clear-navigation anchor.	5 / 5
	Total	18 / 20 Passed

Description

83%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, well-structured description that explicitly pairs capabilities with a Use-when clause and dedicated trigger terms. It is mostly distinct and specific, with only minor gaps in trigger synonym/extension coverage and slight overlap risk from generic E2E terms.

Dimension	Reasoning	Score
Specificity	Names four specific capability areas ("E2E testing patterns, cross-browser configuration, page objects, and CI setup") rather than vague abstractions, but these are domain-level buckets rather than granular atomic actions, leaving minor coverage gaps.	4 / 5
Completeness	Clearly answers "what" (the four capability areas) and "when" ("Use when creating E2E specs, visual regression suites, or configuring Playwright in CI") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Explicit trigger clause ("playwright, e2e, trace, page object, cross-browser") covers the natural terms users say, but omits common synonyms/extensions like "visual regression", "snapshot", or ".spec.ts".	4 / 5
Distinctiveness Conflict Risk	The "playwright" niche is distinct, but generic triggers like "e2e" and "cross-browser" create minor overlap risk with other E2E testing skills (e.g. Cypress), placing it just below fully distinct.	4 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: monkilabs/opencastle
Path: src/orchestrator/plugins/playwright/SKILL.md
Commit: fa0c341

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.