playwright-testing

Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), test tags (@smoke, @fast, @critical, filtering with --grep), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.

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

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.

The content is a well-structured routing layer that points to detailed reference files and includes a concrete validation workflow. Its main weakness is redundancy: the activity tables and the decision tree duplicate the same routing information, inflating token cost without adding clarity.

Suggestions

Collapse the Activity-Based Reference Guide and the Quick Decision Tree into a single navigation aid; they cover the same activities-to-files mapping twice, roughly doubling the routing tokens.

Add a one-line orientation at the top stating that all detailed guidance lives in the referenced files, so Claude knows immediately whether to read further or consult a reference.

Make the validation loop's retry feedback explicit (e.g., 'Re-run the failing test; if still failing, expand trace review to locators/waits/assertions') rather than the implicit 'Re-run tests'.

Dimension	Reasoning	Score
Conciseness	The body avoids over-explaining concepts Claude already knows, but the Activity-Based Reference Guide tables and the Quick Decision Tree cover near-identical ground, so a large portion of the routing content is duplicated and could be tightened to one structure.	3 / 5
Actionability	Each activity maps to specific reference file paths and the validation loop gives executable commands ("npx playwright test --reporter=list", "npx playwright show-trace", "npx playwright test --repeat-each=5"); minor gap is that most executable detail lives in the referenced files rather than inline.	4 / 5
Workflow Clarity	The Test Validation Loop is a clearly numbered sequence with an explicit checkpoint ("Only proceed when all tests pass") and a fix-and-re-run feedback loop; it stops short of a fuller checklist and the re-run step is somewhat implicit.	4 / 5
Progressive Disclosure	The body is a pure overview routing to one-level-deep, clearly signaled reference files organized by category (core/, testing-patterns/, advanced/, debugging/, etc.) with markdown links, making navigation easy and keeping detail out of SKILL.md.	5 / 5
	Total	16 / 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.

The description is exemplary: it opens with an explicit 'Use when' clause listing dozens of concrete triggers, then summarizes scope with a clear 'what' statement. It is highly specific, complete, and distinct.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions ("writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, mocking APIs..."), giving comprehensive coverage of specific capabilities rather than vague language.	5 / 5
Completeness	Explicitly answers both what ("Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing") and when ("Use when writing Playwright tests, fixing flaky tests...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural-language triggers users would actually say ("fixing flaky tests", "Page Object Model", "accessibility (axe-core)", "WebSockets", "@smoke, @fast, @critical, filtering with --grep"), including synonyms and tool-specific terms.	5 / 5
Distinctiveness Conflict Risk	Clear niche scoped to Playwright with distinct, tool-specific triggers; minimal conflict risk with other testing skills.	5 / 5
	Total	20 / 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: 130 missing	Warning

	Total	15 / 16 Passed

Repository: MODSetter/SurfSense
Path: .cursor/skills/playwright-testing/SKILL.md
Commit: d96e29d

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