playwright-pro

Production-grade Playwright testing toolkit. Use when the user mentions Playwright tests, end-to-end testing, browser automation, fixing flaky tests, test migration, CI/CD testing, or test suites. Generate tests, fix flaky failures, migrate from Cypress/Selenium, sync with TestRail, run on BrowserStack. 55 templates, 3 agents, smart reporting.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

85%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 highly actionable with a clear, checkpointed workflow and concrete commands. Its main weaknesses are minor duplication/padding and, more importantly, a progressive-disclosure gap: it promises reference docs, templates, and integration files that are not actually bundled, leaving its one-level-deep references broken.

Suggestions

Ship the referenced bundle files (reference/*.md, templates/README.md, CLAUDE.md, integrations/) or remove the references so navigation does not point to missing files.

De-duplicate content: consolidate the locator guidance into one place and list the reference docs once instead of in both "What's Included" and "Quick Reference".

Trim marketing fluff in "What's Included" (e.g. "Smart hooks", "Production-grade") to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete rules and commands, but contains minor redundancy and padding: locator guidance is duplicated (Golden Rule #1 and the Locator Priority section), the six reference docs are listed twice ("What's Included" and "Quick Reference"), and the "What's Included" bullets carry mild marketing fluff ("Smart hooks").	4 / 5
Actionability	Fully actionable: concrete slash commands, an executable example walkthrough with real file paths and commands (`npx playwright test tests/auth/login.spec.ts --headed`), explicit locator API guidance, and specific retry/trace config values.	5 / 5
Workflow Clarity	Clear numbered sequence (init → generate → review → fix) with explicit validation checkpoints ("always run /pw:pw-review before committing", re-run the suite after fix, run coverage after migrate) and feedback loops for error recovery.	5 / 5
Progressive Disclosure	On-page navigation is well signaled (Quick Reference lists reference docs with one-line descriptions), but the referenced bundle files do not exist in the bundle: no `reference/` directory, no `templates/README.md`, no `CLAUDE.md`, and no `integrations/` — so the one-level-deep references point to missing files, which the rubric directs be scored against actual bundle structure.	3 / 5
	Total	17 / 20 Passed

Description

100%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 description that cleanly answers both what the skill does and when to invoke it, with concrete actions and natural trigger terms. The only minor weakness is light promotional padding ("Production-grade", "55 templates, 3 agents, smart reporting") that adds little evaluative signal.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Generate tests, fix flaky failures, migrate from Cypress/Selenium, sync with TestRail, run on BrowserStack" — giving comprehensive coverage of the toolkit's capabilities.	5 / 5
Completeness	Explicitly answers both "what" (toolkit with the listed actions) and "when" ("Use when the user mentions Playwright tests, end-to-end testing, ...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger terms users would actually say: "Playwright tests, end-to-end testing, browser automation, fixing flaky tests, test migration, CI/CD testing, or test suites" with synonyms and adjacent phrases covered.	5 / 5
Distinctiveness Conflict Risk	A clear Playwright-testing niche with distinct triggers; minimal overlap risk with other skills. Mild promotional fluff ("Production-grade", "smart reporting") does not undermine the distinct trigger surface.	5 / 5
	Total	20 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: alirezarezvani/claude-skills
Path: engineering-team/playwright-pro/skills/pw/SKILL.md
Commit: 19392f7

Reviewed: ~11 hours 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.