playwright-migration

Step-by-step migration guides for moving to Playwright from Cypress or Selenium/WebDriver — command mappings, architecture changes, and incremental adoption strategies.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%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 exemplary dispatcher-style SKILL.md: minimal token cost, a clean decision table, and properly deferred detail. The only improvement space is a slightly richer routing layer (how to handle other source frameworks or a strategy choice) without inlining guide content.

Dimension	Reasoning	Score
Conciseness	The body is a lean 18-line router: a title, a one-line tagline, a guide count, and an index table — no re-explanation of Playwright, Cypress, or migration concepts Claude already knows. The blockquote tagline is the only flourish and costs almost nothing.	5 / 5
Actionability	The Guide Index gives unambiguous, directly executable routing ('Cypress → from-cypress.md', 'Selenium / WebDriver → from-selenium.md'), and absence of code is not penalized for an index-style instruction skill. It falls short of 5 because there is no guidance for unlisted source frameworks (e.g., WebdriverIO, Puppeteer) or for choosing between incremental and complete migration paths.	4 / 5
Workflow Clarity	This is a simple single-purpose skill under 50 lines whose single action — match the user's current framework and open the corresponding guide — is completely unambiguous, so it qualifies for the simple-skill exception. There is no multi-step or destructive process, so validation checkpoints are not applicable.	5 / 5
Progressive Disclosure	The body is exactly what a SKILL.md overview should be: a clear index with well-signaled, one-level-deep markdown links ('[from-cypress.md](from-cypress.md)', '[from-selenium.md](from-selenium.md)') and zero inlined detail that belongs in the guides. Note: the referenced guide files were not present in the review workspace, so this is scored on the structure as written; in the shipped bundle the files sit alongside SKILL.md.	5 / 5
	Total	19 / 20 Passed

Description

77%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, specific description with excellent trigger keywords and a clear niche. Its one real weakness is the absence of an explicit 'Use when...' clause, which leaves the usage trigger implied rather than stated and caps completeness at 3.

Suggestions

Append an explicit trigger clause, e.g. 'Use when migrating an existing test suite from Cypress or Selenium/WebDriver to Playwright, or when the user mentions moving/porting tests to Playwright.'

Add one or two more concrete action verbs for the deliverables (e.g., 'translate Cypress commands to Playwright equivalents, convert fixtures and custom commands, set up parallel execution') to close the specificity gap.

Optionally include natural user phrasings like 'port tests' or 'switch from Selenium' to broaden trigger coverage beyond the current keywords.

Dimension	Reasoning	Score
Specificity	'command mappings, architecture changes, and incremental adoption strategies' names the domain and several concrete deliverables. It is not 5 because 'architecture changes' and 'adoption strategies' are more abstract than fully concrete actions like 'command mappings'; it is not 3 because coverage goes well beyond 1–2 actions.	4 / 5
Completeness	The 'what' is clear (step-by-step guides with command mappings, architecture changes, adoption strategies), but there is no 'Use when...' clause or equivalent explicit trigger guidance — the 'when' is only weakly implied by 'for moving to Playwright from Cypress or Selenium/WebDriver'. Per the judging guideline, a missing explicit trigger clause caps completeness at 3; not 4 because 'when' is nowhere explicitly stated.	3 / 5
Trigger Term Quality	'Playwright', 'migration', 'Cypress', and 'Selenium/WebDriver' comprehensively cover the natural phrases a user would say when needing this skill ('migrate Cypress to Playwright', 'move off Selenium'), including the Selenium/WebDriver synonym pairing. No natural trigger term for the skill's scope is missing.	5 / 5
Distinctiveness Conflict Risk	It carves a clear niche — migrating to Playwright from two named frameworks — with distinct triggers, so risk of firing for a generic Playwright-testing skill is minimal. Anti-drift check: the anchor for 4 (minor overlap with closely related skills) fits less well than the distinct-niche anchor at 5.	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: 2 missing	Warning

	Total	15 / 16 Passed

Repository: zebbern/claude-code-guide
Path: skills/playwright/migration/SKILL.md
Commit: a2e6ee3

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