playwright
Browser automation and E2E testing with Playwright. Auto-detects dev servers, writes clean test scripts. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use for cross-browser testing, visual regression, API testing, component testing in TypeScript/JavaScript and Python projects.
83
83%
Does it follow best practices?
Impact
75%
4.16xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
82%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 a strong description with excellent specificity and trigger term coverage. It clearly identifies the Playwright tool and lists comprehensive capabilities. The main weakness is the 'Use for...' clause which describes use cases rather than providing explicit trigger conditions for when Claude should select this skill.
Suggestions
Reframe 'Use for cross-browser testing...' to 'Use when the user mentions Playwright, browser automation, E2E tests, or asks to test web pages, forms, or login flows.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Auto-detects dev servers, writes clean test scripts, Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task.' | 3 / 3 |
Completeness | Strong 'what' section with detailed capabilities, but the 'when' guidance ('Use for cross-browser testing...') describes use cases rather than explicit trigger conditions like 'Use when the user asks about...' or 'Use when working with...'. The trigger guidance is implied rather than explicit. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'browser automation', 'E2E testing', 'Playwright', 'test pages', 'fill forms', 'screenshots', 'responsive design', 'login flows', 'cross-browser testing', 'visual regression', 'API testing', 'component testing', 'TypeScript/JavaScript', 'Python'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche with 'Playwright' as a distinct identifier, combined with specific browser automation and E2E testing context. Unlikely to conflict with general testing or coding skills due to the specific tooling and domain focus. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%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, well-structured skill with excellent actionability and workflow clarity. The critical workflow section effectively guides Claude through the server detection process before testing. Minor verbosity in the introduction and some sections could be tightened, but overall the skill provides comprehensive, executable guidance for browser automation tasks.
Suggestions
Remove the introductory sentence 'Expert knowledge for browser automation...' - Claude doesn't need this context
Consolidate the path resolution section - the explanation of common installation paths could be reduced to a single line noting to use the discovered path
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanations (e.g., 'Expert knowledge for browser automation' intro, explaining what Playwright is). The path resolution section and some setup instructions could be tightened. | 2 / 3 |
Actionability | Excellent actionability with fully executable code examples throughout - complete JavaScript/TypeScript snippets for responsive testing, login flows, link checking, and more. All examples are copy-paste ready with clear execution commands. | 3 / 3 |
Workflow Clarity | The CRITICAL WORKFLOW section provides clear numbered steps with explicit decision points (1 server vs multiple vs none). Validation is built into the workflow with server detection first, and the troubleshooting section provides error recovery guidance. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from quick start to advanced patterns. References to API_REFERENCE.md are clearly signaled with a 'When to Load References' section listing specific use cases. Content is appropriately split between main skill and reference file. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- Repository
- secondsky/claude-skills
- Commit
90d6bd7
- 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.