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).
86
78%
Does it follow best practices?
Impact
100%
1.36xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xbigboss/claude-code/playwright-best-practices/SKILL.mdQuality
Discovery
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.
This is an excellent skill description that concisely covers specific capabilities, provides clear trigger conditions with file patterns and import references, and occupies a distinct niche. It uses proper third-person voice and balances brevity with completeness effectively.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions/patterns: resilient locators, Page Object Models, fixtures, web-first assertions, and network mocking. These are all distinct, concrete Playwright testing concepts. | 3 / 3 |
Completeness | Clearly answers both 'what' (Playwright test patterns for locators, POM, fixtures, assertions, mocking) and 'when' ('Must use when writing or modifying Playwright tests' with explicit file patterns and import triggers). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would use: 'Playwright', 'test', '.spec.ts', '.test.ts', '@playwright/test', 'locators', 'Page Object Models', 'fixtures', 'assertions', 'network mocking'. Good coverage of both conceptual and file-based triggers. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: specifically Playwright testing. The file extensions (.spec.ts, .test.ts) and import reference (@playwright/test) make it very unlikely to conflict with general testing or other framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive and highly actionable Playwright reference with excellent code examples and clear good/bad comparisons. Its main weaknesses are its monolithic length — covering POM, fixtures, auth, mocking, config, and debugging all inline — and the lack of a clear workflow guiding users through multi-step processes. Splitting into a concise overview with references to topic-specific files would significantly improve token efficiency and progressive disclosure.
Suggestions
Split into a concise SKILL.md overview (locator priority, web-first assertions, anti-patterns, checklist) with references to separate files like PAGES.md, FIXTURES.md, AUTH.md, and MOCKING.md for detailed patterns.
Add a brief 'Writing a New Test' workflow section with numbered steps and validation checkpoints (e.g., 1. Create spec file, 2. Set up fixtures, 3. Write test with web-first assertions, 4. Run with --reporter=line, 5. Debug failures with --trace).
Trim the BasePage abstract class example — the debug logging dependency and safeClick/safeFill wrappers are opinionated patterns that add bulk; a simpler POM example would suffice for the skill.
Remove or condense the full playwright.config.ts block since much of it is standard boilerplate; focus only on the non-obvious settings like reporter configuration and auth setup project dependencies.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally efficient with good code examples, but it's quite long (~400 lines) and includes some patterns Claude likely knows (e.g., basic POM concepts, test isolation principles). The BasePage abstract class with debug logging is more opinionated boilerplate than necessary. Some sections like Helpers and the full config could be in separate files. | 2 / 3 |
Actionability | Excellent actionability throughout — every section provides fully executable TypeScript code, concrete CLI commands, and clear good/bad comparisons. Code examples are copy-paste ready with proper imports and realistic patterns. | 3 / 3 |
Workflow Clarity | The skill covers many topics but lacks explicit multi-step workflow sequencing for common tasks like 'writing a new test from scratch' or 'adding auth to an existing project.' The checklist at the end helps, but there are no validation checkpoints or feedback loops for the test-writing process itself. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content (~400 lines) with no references to external files despite covering many distinct topics (POM, fixtures, auth, mocking, config, debugging) that would benefit from separation. The project structure section hints at organization but the skill itself doesn't practice it. | 1 / 3 |
Total | 8 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
aa009ea
- 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.