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.
85
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 Playwright as the tool and lists numerous concrete actions. The main weakness is the 'Use for...' clause which lists use cases rather than providing explicit trigger guidance for when Claude should select this skill.
Suggestions
Reframe 'Use for cross-browser testing...' to 'Use when the user mentions Playwright, E2E testing, browser automation, or needs to test web pages across browsers.'
| 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 on 'what' with detailed capabilities, but the 'when' clause ('Use for cross-browser testing...') describes use cases rather than explicit trigger guidance like 'Use when the user mentions...' or 'Use when working with...' | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Playwright', 'E2E testing', 'browser automation', 'screenshots', 'responsive design', 'login flows', 'cross-browser testing', 'visual regression', 'API testing', 'TypeScript/JavaScript', 'Python'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche with 'Playwright' as a distinct identifier, combined with specific triggers like 'E2E testing', 'browser automation', and 'visual regression' that are unlikely to conflict with other skills. | 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-organized skill with excellent actionability - nearly every section includes executable code examples. The workflow is clearly defined with explicit decision points for server detection. Minor verbosity in the introduction and some sections could be tightened, but overall the skill effectively teaches Playwright automation without over-explaining concepts Claude already knows.
| 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 executable code examples throughout - complete JavaScript/TypeScript snippets for responsive testing, login flows, link checking, network mocking, 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 at the end with specific use cases listed. Content is appropriately split between overview and detailed reference. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 12 / 16 Passed | |
- 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.