playwright-skill
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing. Do NOT use for quick page debugging or network inspection (use chrome-devtools instead).
85
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 covers all key dimensions well. It lists numerous specific actions, includes natural trigger terms users would use, explicitly states both what the skill does and when to use it, and even differentiates itself from a potentially conflicting skill (chrome-devtools) with a 'Do NOT use' clause. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: auto-detects dev servers, writes test scripts to /tmp, test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate browser tasks. | 3 / 3 |
Completeness | Clearly answers both 'what' (browser automation with Playwright, specific actions listed) and 'when' (explicit 'Use when user wants to test websites, automate browser interactions, validate web functionality'). Also includes a 'Do NOT use' clause which adds further clarity on when to select this skill. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'test websites', 'automate browser', 'screenshots', 'responsive design', 'login flows', 'check links', 'fill forms', 'Playwright', 'browser automation'. Also includes a helpful negative trigger distinguishing from chrome-devtools. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly carved niche around Playwright browser automation with explicit differentiation from chrome-devtools for debugging/network inspection. The 'Do NOT use' clause directly addresses potential conflict with a similar skill. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill excels at actionability with numerous executable, well-structured code examples and a clear workflow for server detection and script execution. However, it is significantly over-verbose with redundant content (responsive testing shown twice, workflow explained multiple times, tips restating obvious practices). The content would benefit greatly from aggressive trimming and moving the extensive code examples to a referenced patterns file.
Suggestions
Reduce redundancy by removing duplicate patterns (responsive design appears twice) and consolidating the workflow explanation to a single location instead of repeating it in 'Critical Workflow', 'How It Works', 'Execution Pattern', and 'Example Usage'.
Move the 'Common Patterns' code examples to a separate PATTERNS.md file and reference it from SKILL.md, keeping only 1-2 examples inline to demonstrate the execution pattern.
Remove the 'Notes' section entirely as it restates information already covered, and trim the 'Tips' section to only non-obvious guidance (remove items like 'use try-catch' and 'use console.log').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines. There is significant redundancy: the responsive design pattern appears twice (in 'Test a Page' and 'Test Responsive Design'), the execution pattern is explained multiple times, the dev server detection is repeated in workflow, execution pattern, and tips. The 'How It Works', 'Notes', and 'Example Usage' sections largely restate what's already covered. Many tips explain things Claude already knows (error handling, wait strategies). | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste ready JavaScript code examples for every pattern. Commands are concrete with specific paths, and the execution pattern is clear with real bash commands. Code examples include proper imports, async/await patterns, and are immediately runnable. | 3 / 3 |
Workflow Clarity | The critical workflow is clearly sequenced with numbered steps (detect servers → write scripts → execute). The dev server detection includes explicit branching logic (1 server/multiple/none). Error handling patterns are shown, and the troubleshooting section provides recovery steps. The login flow example shows validation via waitForURL. | 3 / 3 |
Progressive Disclosure | There is a good reference to API_REFERENCE.md for advanced usage, and helpers are summarized with a pointer to the full file. However, the main SKILL.md itself is a wall of content with too many inline code examples that could be split into a separate patterns/examples file. The common patterns section alone is massive and could benefit from being referenced rather than inline. | 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
- tech-leads-club/agent-skills
- Commit
81e7e0d
- 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.