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).
88
82%
Does it follow best practices?
Impact
100%
1.36xAverage score across 3 eval scenarios
Passed
No known issues
Quality
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
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable Playwright skill with excellent concrete code examples covering all major patterns. Its main weaknesses are length (could benefit from splitting into overview + detailed references) and the lack of explicit multi-step workflows with validation checkpoints for common scenarios like setting up auth or creating a new test suite. The CLI context overflow prevention tip at the top is a valuable, non-obvious addition specific to Claude Code usage.
Suggestions
Split detailed sections (POM examples, fixture patterns, auth setup) into separate referenced files, keeping SKILL.md as a concise overview with links to each topic — this would improve both conciseness and progressive disclosure.
Add an explicit step-by-step workflow for the most common scenario (e.g., 'Adding a new Playwright test for a feature') with validation checkpoints like running the test, checking locator strictness, and verifying test isolation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but it's quite long (~400 lines) and includes some patterns Claude likely knows (e.g., basic test isolation concepts, project structure conventions). The BasePage abstract class with debug logging adds complexity that may not be needed in every context. However, most content earns its place with concrete, non-obvious patterns. | 2 / 3 |
Actionability | Excellent actionability throughout — every section provides fully executable TypeScript code, specific CLI commands, and concrete good/bad comparisons. The code examples are copy-paste ready with proper imports, types, and realistic patterns (login page, fixtures, auth setup, network mocking). | 3 / 3 |
Workflow Clarity | The skill covers many individual patterns clearly but lacks explicit multi-step workflow sequencing for common end-to-end scenarios (e.g., 'setting up a new Playwright project from scratch' or 'adding a new test for a feature'). The authentication setup has implicit ordering via project dependencies but doesn't spell out the validation/verification steps. The checklist at the end helps but is a review tool, not a workflow guide. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and a logical progression from locators to assertions to POM to fixtures to configuration. However, it's a monolithic document (~400 lines) that could benefit from splitting detailed sections (e.g., full POM examples, fixture patterns) into separate referenced files, keeping SKILL.md as a concise overview with links. | 2 / 3 |
Total | 9 / 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
e437c3c
- 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.