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

76%

Does it follow best practices?

Impact

100%

1.36x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./data/skills-md/0xbigboss/claude-code/playwright-best-practices/SKILL.md

Quality

Content

65%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 highly actionable, code-rich Playwright reference with strong examples and a useful checklist. Its weaknesses are repetition of the reporter guidance, the absence of explicit validation feedback loops, and the lack of file-level progressive disclosure for a large skill.

Suggestions

Consolidate the reporter/context-overflow guidance into a single section and reference it from the config, anti-patterns, and checklist instead of repeating it four times.

Extract the detailed Page Object Model, fixtures, and authentication examples into one-level-deep reference files (e.g. references/page-objects.md, references/fixtures.md) and link to them from SKILL.md to improve progressive disclosure.

Add an explicit feedback loop for test runs (run -> read failure -> trace/debug -> fix -> re-run) so the workflow has concrete validation checkpoints rather than implicit ones.

Dimension	Reasoning	Score
Conciseness	The body is code-dense and avoids explaining concepts Claude already knows, but the reporter/context-overflow guidance is repeated four times (intro, config, anti-patterns, checklist) and the ~490-line length could be tightened.	3 / 5
Actionability	Abundant copy-paste-ready, executable TypeScript and CLI commands across locators, POM, fixtures, auth, mocking, and config, covering the common Playwright testing cases comprehensively.	5 / 5
Workflow Clarity	The document is a patterns catalog rather than a sequenced workflow; ordering cues (routes before navigation, setup project before dependents) are pattern-level and implicit, with no explicit validate-to-fix-to-retry feedback loops despite test runs being batch operations.	3 / 5
Progressive Disclosure	Section headers give good internal structure, but with no bundle files the entire ~490-line body is inlined in SKILL.md and detailed material (full POM classes, fixtures, auth setup, config) that could live in one-level-deep reference files is not split out.	3 / 5
	Total	14 / 20 Passed

Description

87%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 explicitly covers both what the skill provides and when to use it, with concrete file-extension and import-based triggers. Minor weakness is the generic 'provides patterns for' framing and the absence of common synonyms like 'e2e tests'.

Dimension	Reasoning	Score
Specificity	Lists five concrete named patterns ('resilient locators, Page Object Models, fixtures, web-first assertions, and network mocking') giving comprehensive domain coverage, but the action is the generic verb 'Provides ... patterns for' rather than concrete verb-driven actions like the score-5 anchor.	4 / 5
Completeness	Explicitly answers both 'what' ('Provides Playwright test patterns for ...') and 'when' ('Must use when writing or modifying Playwright tests ...') with concrete trigger phrases including file extensions and imports.	5 / 5
Trigger Term Quality	Includes natural terms ('writing or modifying Playwright tests') plus file extensions and import markers ('.spec.ts, .test.ts files with @playwright/test imports'), but misses common synonyms like 'e2e tests', 'end-to-end tests', or 'browser tests'.	4 / 5
Distinctiveness Conflict Risk	Clearly Playwright-specific niche with distinct triggers keyed on file extensions and the @playwright/test import, giving minimal conflict risk with other skills.	5 / 5
	Total	18 / 20 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
Path: data/skills-md/0xbigboss/claude-code/playwright-best-practices/SKILL.md
Commit: 2f57aec

Reviewed: about 22 hours 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.