playwright-expert

Use when writing E2E tests with Playwright, setting up test infrastructure, or debugging flaky browser tests. Invoke to write test scripts, create page objects, configure test fixtures, set up reporters, add CI integration, implement API mocking, or perform visual regression testing. Trigger terms: Playwright, E2E test, end-to-end, browser testing, automation, UI testing, visual testing, Page Object Model, test flakiness.

Quality

82%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

64%

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

This skill provides strong, actionable code examples with good contrast between correct and incorrect patterns, making it immediately useful for Playwright test writing. However, it suffers from a disconnect between its progressive disclosure structure (referencing five detail files) and the lack of actual bundle files, and the top-level workflow is too abstract to guide complex multi-step processes. Some sections (Knowledge Reference, Output Templates) add little value and could be trimmed.

Suggestions

Create the five referenced files (selectors-locators.md, page-object-model.md, api-mocking.md, configuration.md, debugging-flaky.md) or remove the reference table to avoid broken references.

Add explicit validation checkpoints to the core workflow, e.g., after writing tests: 'Run npx playwright test --reporter=list to verify all tests pass before proceeding to CI integration.'

Remove the 'Knowledge Reference' keyword list and the vague 'Output Templates' section — they consume tokens without adding actionable guidance.

Dimension	Reasoning	Score
Conciseness	Generally efficient but includes some unnecessary elements like the 'Knowledge Reference' section which is just a keyword list adding no value, and the output templates section is vague filler. The MUST DO/MUST NOT lists partially overlap with what the code examples already demonstrate.	2 / 3
Actionability	Provides fully executable, copy-paste ready TypeScript code examples including a complete Page Object Model class, test file with assertions, and a concrete debugging workflow with specific CLI commands. The contrast between correct and incorrect patterns is highly actionable.	3 / 3
Workflow Clarity	The core workflow is listed at a high level but lacks validation checkpoints. The debugging workflow for flaky tests is well-sequenced with a clear feedback loop (run → trace → fix → verify with repeat-each=10), but the overall test-writing workflow (steps 1-5 at the top) is too abstract to guide multi-step execution reliably.	2 / 3
Progressive Disclosure	The reference table with 'Load When' guidance is a well-structured progressive disclosure pattern, but no bundle files are provided, meaning all five referenced files (selectors-locators.md, page-object-model.md, etc.) are missing. The skill inlines substantial content that could be in references while simultaneously pointing to non-existent files.	2 / 3
	Total	9 / 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.

This is a strong skill description that excels across all dimensions. It provides specific concrete actions, comprehensive trigger terms that users would naturally use, explicit 'when' guidance, and clear distinctiveness through Playwright-specific terminology. The description is well-structured and concise without unnecessary padding.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: write test scripts, create page objects, configure test fixtures, set up reporters, add CI integration, implement API mocking, and perform visual regression testing.	3 / 3
Completeness	Clearly answers both 'what' (write test scripts, create page objects, configure fixtures, etc.) and 'when' (writing E2E tests with Playwright, setting up test infrastructure, debugging flaky browser tests) with explicit trigger guidance.	3 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: 'Playwright', 'E2E test', 'end-to-end', 'browser testing', 'automation', 'UI testing', 'visual testing', 'Page Object Model', 'test flakiness'. These are terms users would naturally use when seeking help with Playwright testing.	3 / 3
Distinctiveness Conflict Risk	Clearly scoped to Playwright and E2E browser testing, with specific terms like 'Playwright', 'Page Object Model', 'visual regression testing', and 'test flakiness' that distinguish it from general testing or other test framework skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: Jeffallan/claude-skills
Commit: e8be415

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.