generate

Generate Playwright tests. Use when user says "write tests", "generate tests", "add tests for", "test this component", "e2e test", "create test for", "test this page", or "test this feature".

Quality

85%

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 content is highly actionable and well-sequenced with a clear verify-and-retry feedback loop, and it respects token budget well. Progressive disclosure is the main weakness because referenced template directories and paths do not exist as bundle files in the skill.

Suggestions

Ship the referenced templates/ bundle (auth/crud/checkout/search/forms/dashboard/settings/onboarding/api/accessibility) or replace the broken template table with inline guidance, since the cited paths have no corresponding files.

Fix the inconsistent template path style ('../pw/templates/auth/login.md' vs relative 'templates/crud/') so navigation is unambiguous.

Trim the locator-priority and assertion sections slightly, or move the full 'never use' rules into a single reference file, to tighten conciseness further.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with concrete code, locator-priority lists, and rules that assume Claude's knowledge of Playwright, though the template-selection table and some commentary could be trimmed slightly.	4 / 5
Actionability	It provides copy-paste-ready TypeScript structure, a ranked locator-priority list, GOOD/BAD assertion examples, explicit 'never use' rules, and a concrete verification command (npx playwright test) covering the common cases.	5 / 5
Workflow Clarity	The seven-step process is clearly sequenced (understand -> explore -> select templates -> generate -> match conventions -> supporting files -> verify) with an explicit verify step and a fix->retry feedback loop for test failures.	5 / 5
Progressive Disclosure	It is well-sectioned but references template paths (e.g., 'templates/crud/', '../pw/templates/auth/login.md') that have no corresponding bundle files in the skill directory, and the bulk of template content is not clearly signaled as a one-level reference.	3 / 5
	Total	17 / 20 Passed

Description

85%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 concise, third-person, and excels at completeness, trigger-term quality, and distinctiveness with an explicit 'Use when...' clause and natural phrasing. Its only weakness is specificity, since it states a single action rather than enumerating several concrete capabilities.

Suggestions

Optionally expand the 'what' clause to list a few concrete actions (e.g., 'Generate Playwright tests, scaffold fixtures, and create page objects') to raise specificity from a single action to several.

Dimension	Reasoning	Score
Specificity	It names the domain ('Generate Playwright tests') but lists only the single concrete action of test generation rather than multiple specific actions, matching the 'names domain and 1-2 concrete actions' anchor.	3 / 5
Completeness	It explicitly answers 'what' ('Generate Playwright tests') and 'when' with a concrete 'Use when user says...' clause listing trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	It provides comprehensive natural trigger phrases users would actually say ('write tests', 'generate tests', 'add tests for', 'test this component', 'e2e test', 'create test for', 'test this page', 'test this feature') with broad synonym coverage.	5 / 5
Distinctiveness Conflict Risk	The Playwright + e2e test niche with specific trigger phrases is clearly distinct from other skills and unlikely to trigger for the wrong skill.	5 / 5
	Total	18 / 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/generate/SKILL.md
Commit: 19392f7

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