CtrlK
BlogDocsLog inGet started
Tessl Logo

playwright-testing

Playwright E2E testing patterns — web-first assertions, user-visible locators, network interception, fixtures, authentication, and parallel execution. Use when building or reviewing E2E tests with Playwright, when setting up browser testing for a web app, or when migrating from Cypress or Selenium.

65

Quality

77%

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 ./.claude/skills/playwright-testing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

A high-quality, highly actionable Playwright reference with excellent executable examples and a verification checklist. Its main weaknesses are moderate verbosity from restated 'Why it matters' rationales and a monolithic single-file structure that does not progressively disclose detail into bundle files.

Suggestions

Trim or merge the 'Why it matters' paragraphs where they restate the adjacent code comments, keeping only rationale not already visible in the example.

Split the larger independent sections (e.g., Page Object Model, Authentication/storageState, Configuration) into one-level-deep reference files under references/ and link to them from a concise overview in SKILL.md.

Consider condensing the WRONG/RIGHT pairs for the simpler anti-patterns (sections 1 and 3 overlap on the auto-waiting rationale) to reduce redundant tokens.

DimensionReasoningScore

Conciseness

Mostly efficient with extensive executable code, but the repeated 'Why it matters' paragraphs frequently restate what the preceding code comments already explain, adding notable length that could be tightened.

3 / 5

Actionability

Fully executable, copy-paste-ready TypeScript throughout — complete playwright.config.ts, fixtures, page objects, network mocking, and auth setup examples cover the common cases concretely.

5 / 5

Workflow Clarity

Ten clearly numbered pattern sections plus an explicit 'Verification' checklist that acts as a review checkpoint; no validate→fix→retry feedback loop is needed since the skill involves no destructive or batch operations.

4 / 5

Progressive Disclosure

Well-structured with clearly signaled external doc references, but the ~479-line body inlines the full detailed reference rather than serving as an overview pointing to one-level-deep bundle files (no references/, scripts/, or assets/ exist).

3 / 5

Total

15

/

20

Passed

Description

83%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, third-person description that clearly states both capabilities and trigger conditions with natural keywords and migration-source synonyms. It is held back only slightly by noun-phrase capability listing and minor overlap with a related e2e-conventions skill referenced in the body.

DimensionReasoningScore

Specificity

Lists six specific capability areas ('web-first assertions, user-visible locators, network interception, fixtures, authentication, and parallel execution') with only minor coverage gaps, but they are noun-phrase topics rather than verb-action concrete actions like the anchor-5 example.

4 / 5

Completeness

Explicitly answers both what (the enumerated Playwright patterns) and when ('Use when building or reviewing E2E tests with Playwright, when setting up browser testing for a web app, or when migrating from Cypress or Selenium') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural keyword coverage ('E2E tests', 'Playwright', 'browser testing', 'web app', 'Cypress', 'Selenium') including migration-source synonyms, missing only a few variants like the full 'end-to-end testing' phrase or file extensions.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear Playwright-specific niche with distinct migration triggers, but the body's reference to a sibling 'e2e-conventions' skill signals minor overlap risk with related e2e skills.

4 / 5

Total

17

/

20

Passed

Validation

100%

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
marmelab/atomic-crm
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.