playwright-skill

Battle-tested Playwright patterns for E2E, API, component, visual, accessibility, and security testing. Covers locators, fixtures, POM, network mocking, auth flows, debugging, CI/CD (GitHub Actions, GitLab, CircleCI, Azure, Jenkins), framework recipes (React, Next.js, Vue, Angular), and migration guides from Cypress/Selenium. TypeScript and JavaScript.

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/playwright/SKILL.md

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.

The body is a well-structured, concise guide index with strong opinionated Golden Rules, but it lacks inline executable code and, critically, all of its referenced bundle files are missing — so progressive disclosure and actionability are undercut in practice.

Suggestions

Ship the referenced bundle files (core/, pom/, migration/, ci/, playwright-cli/) so the guide index actually resolves; without them navigation is broken.

Add one or two short inline code snippets in the body (e.g. a getByRole example and a web-first assertion) so the skill is actionable even before loading references.

Trim the promotional intro lines ('50+ reference guides', 'Opinionated, production-tested') to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (terse Golden Rules, no explaining what Playwright is), but two promotional intro lines ('50+ reference guides', 'Opinionated, production-tested') add mild verbosity that could be trimmed.	4 / 5
Actionability	Golden Rules give concrete directives (getByRole over CSS, never page.waitForTimeout, retries 2 in CI), but there are no inline executable code examples — all actual code lives in referenced guide files, leaving guidance incomplete in the body itself.	3 / 5
Workflow Clarity	This is a categorized guide index rather than a sequenced multi-step process, so selection-by-table is reasonably clear, but there are no sequenced steps or validation checkpoints for the testing workflows it points to.	3 / 5
Progressive Disclosure	The structure is well-organized into one-level-deep category tables that would score higher, but none of the 50+ referenced files (core/.md, pom/.md, ci/.md, playwright-cli/.md) exist in the bundle, so the signaled navigation leads nowhere.	3 / 5
	Total	13 / 20 Passed

Description

75%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.

The description is highly specific and distinctive, comprehensively listing concrete Playwright capabilities and platforms. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which limits the completeness score.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when writing or debugging Playwright E2E/API/component tests, or migrating from Cypress/Selenium.'

Include a few more natural synonyms users say, such as 'end-to-end tests', 'browser automation', or 'Playwright tests'.

Consider naming file extensions or specific Playwright terms (e.g. trace files, .spec.ts) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Enumerates many concrete capabilities (E2E, API, component, visual, a11y, security testing, locators, fixtures, POM, network mocking, auth flows, debugging, CI/CD across named platforms, framework recipes, migration guides), giving comprehensive coverage of specific actions.	5 / 5
Completeness	The 'what' is comprehensive, but there is no explicit 'Use when...' trigger clause; per rubric guidance a missing trigger clause caps completeness at 3, and 'when' is only weakly implied by domain enumeration.	3 / 5
Trigger Term Quality	Strong natural keywords ('Playwright patterns', 'E2E testing', 'Cypress/Selenium', framework names) with good coverage, but a few common synonyms users say are absent and no explicit trigger phrasing is used.	4 / 5
Distinctiveness Conflict Risk	Clearly scoped to Playwright-specific testing with distinct triggers (named frameworks, migration sources, CI platforms), creating a clear niche with minimal conflict risk.	5 / 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: 74 missing	Warning

	Total	15 / 16 Passed

Repository: zebbern/claude-code-guide
Path: skills/playwright/SKILL.md
Commit: 4eaf4ff

Reviewed: 4 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.