CtrlK
BlogDocsLog inGet started
Tessl Logo

playwright-migration

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

56

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/playwright/migration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%

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

The SKILL.md body is admirably concise and well-organized as a navigation hub, but it contains no actionable migration guidance itself and its two referenced guide files do not exist in the bundle, weakening both actionability and progressive disclosure.

Suggestions

Add the missing bundle files (from-cypress.md, from-selenium.md) so the index links resolve, or remove the links until the content exists.

Include at least a brief concrete starting point in the body (e.g. a sample command mapping or the first migration step) rather than relying entirely on the linked guides for actionability.

DimensionReasoningScore

Conciseness

The body is minimal and unpadded — a one-line tagline, a count, and a Guide Index table — with no concept explanation or filler, matching the lean and efficient anchor.

3 / 3

Actionability

The body offers no executable guidance — no commands, code, or migration steps — only a table pointing to guide files, which describes/navigates rather than instructs, matching the vague/abstract anchor.

1 / 3

Workflow Clarity

This is a simple navigation hub under 50 lines whose single action (pick the matching source-framework guide) is unambiguous via the index, so the simple-skill allowance lets workflow clarity score 3.

3 / 3

Progressive Disclosure

The body is a clean one-level-deep overview with a well-signaled index table, but the referenced files (from-cypress.md, from-selenium.md) are not present in the bundle, so the disclosure structure cannot be verified to resolve.

2 / 3

Total

9

/

12

Passed

Description

67%

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 specific and distinctive, clearly carving out a Playwright-migration niche with concrete deliverables. It loses points for lacking an explicit "Use when..." trigger clause and for missing common verb-style trigger variations users would naturally say.

Suggestions

Add an explicit trigger clause, e.g. "Use when migrating a test suite from Cypress or Selenium/WebDriver to Playwright, or when the user asks to move/convert/port tests to Playwright."

Include natural verb variations ("move", "convert", "port") alongside "migration" so the description matches how users phrase the request.

DimensionReasoningScore

Specificity

Names multiple concrete deliverables — "command mappings", "architecture changes", and "incremental adoption strategies" — matching the anchor for listing several specific actions, not the partial coverage of a 2.

3 / 3

Completeness

Clearly answers "what" (migration guides with three deliverable types) but provides no explicit "Use when..." trigger clause, so per the judging guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

Includes the natural framework names ("Playwright", "Cypress", "Selenium/WebDriver") and "migration", but omits common verb variations users say like "move", "convert", "port", leaving it at "some relevant keywords but missing common variations".

2 / 3

Distinctiveness Conflict Risk

The niche is explicit and narrow — moving to Playwright specifically from Cypress or Selenium/WebDriver — making it unlikely to trigger for unrelated skills, matching the clear-niche anchor.

3 / 3

Total

10

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository
zebbern/claude-code-guide
Reviewed

Table of Contents

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.