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 clearly defines its scope (Playwright test patterns), lists specific capabilities, and provides explicit trigger conditions including file patterns and import references. It uses proper third-person voice and is concise without being vague. The 'Must use when' clause with concrete file and import triggers is particularly strong for disambiguation.
| 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 comprehensive and highly actionable Playwright testing guide with excellent concrete examples and good/bad comparisons throughout. Its main weaknesses are its length (could benefit from splitting detailed POM and configuration examples into referenced files) and the lack of explicit validation/feedback workflows for multi-step processes like test creation and debugging cycles. The CLI context overflow prevention tip at the top is a valuable, agent-specific addition.
Suggestions
Extract the full POM examples (BasePage + LoginPage) and configuration into referenced files (e.g., POM.md, CONFIG.md) to reduce the main skill's token footprint while keeping the overview concise.
Add an explicit workflow sequence for writing/debugging tests, e.g., '1. Write test → 2. Run with --reporter=line → 3. If failure, run --debug → 4. Fix locators/assertions → 5. Re-run' with validation checkpoints.
| 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, the full BasePage abstract class with debug logging). The anti-patterns section partially duplicates guidance already given in earlier sections. | 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 real Playwright APIs, complete file paths, and proper imports. | 3 / 3 |
Workflow Clarity | The skill covers many patterns clearly but lacks explicit multi-step workflows with validation checkpoints. For example, the authentication setup flow doesn't specify what to do if auth fails, and there's no clear 'write test → run → validate → fix' feedback loop. The checklist at the end helps but is a static list rather than a sequenced workflow. | 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. However, it's a monolithic file with no references to external files for detailed topics (e.g., the full POM examples and configuration could be split out). The project structure section hints at organization but doesn't link to supplementary docs. | 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
f772de4
- 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.