playwright-best-practices

Provides Playwright test patterns for resilient locators, Page Object Models, fixtures, web-first assertions, and network mocking. Must use when writing or modifying Playwright tests (.spec.ts, .test.ts files with @playwright/test imports).

1.36x

Quality

—

Does it follow best practices?

Impact

100%

1.36x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

65%

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

A thorough, highly actionable Playwright reference with executable code and BAD/GOOD contrasts throughout. Its main weaknesses are length/repetition and the absence of validation checkpoints and progressive file-based disclosure.

Suggestions

Split large reference blocks (Page Object Model, fixtures, full playwright.config.ts) into separate files under references/ and link to them from SKILL.md to reduce token load and improve navigation.

Add explicit validation/feedback-loop steps for risky operations — e.g., after auth setup, assert the storageState file exists and a protected route loads; after network mocking, assert the route was intercepted before proceeding.

De-duplicate the reporter configuration (it appears both in the CLI section and in playwright.config.ts) and trim verbose inline commentary to tighten the token budget.

Dimension	Reasoning	Score
Conciseness	The body is code-first and largely free of concept re-explanation, but at ~490 lines it is lengthy and repeats configuration blocks (the reporter setup appears twice); it could be tightened without losing value.	2 / 3
Actionability	Every section ships executable, copy-paste-ready code — locator chaining, full BasePage/LoginPage classes, fixture extension, auth setup, network mocking, and a complete playwright.config.ts — with BAD/GOOD contrasts.	3 / 3
Workflow Clarity	Sections are well sequenced and capped by an anti-patterns list and checklist, but there are no explicit validation/feedback-loop checkpoints for the riskier operations (network mocking, storage-state auth), which caps workflow clarity at 2.	2 / 3
Progressive Disclosure	No bundle files exist and the entire reference lives inline in a ~490-line SKILL.md; sections are well organized, but content such as the full POM, fixtures, and config could be split into referenced files for easier navigation.	2 / 3
	Total	9 / 12 Passed

Description

100%

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 precise, third-person description that names concrete capabilities and provides an explicit 'when to use' clause anchored to Playwright-specific file and import triggers. It is distinguishable and free of vague fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'resilient locators, Page Object Models, fixtures, web-first assertions, and network mocking' — matching the anchor for enumerating specific actions.	3 / 3
Completeness	Explicitly answers both what ('Provides Playwright test patterns for...') and when ('Must use when writing or modifying Playwright tests...'), satisfying the explicit trigger-clause requirement.	3 / 3
Trigger Term Quality	Covers natural terms a user would say ('writing or modifying Playwright tests', 'Playwright tests') plus concrete file/import triggers ('.spec.ts', '.test.ts', '@playwright/test').	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to Playwright via file extensions and the '@playwright/test' import, giving it a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	12 / 12 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: NeverSight/skills_feed
Commit: 26d37ce

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