playwright-master
Browser automation expert - E2E tests, web scraping, UI testing
Install with Tessl CLI
npx tessl i github:TurnaboutHero/oh-my-antigravity --skill playwright-masterOverall
score
61%
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
33%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies the domain and lists capability categories but lacks specificity in concrete actions and completely omits trigger guidance. It reads more like a title than a description that would help Claude distinguish when to use this skill among many options.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks to automate browser interactions, write Playwright/Puppeteer scripts, scrape websites, or create end-to-end tests'
Expand with specific concrete actions such as 'navigate pages, click elements, fill forms, capture screenshots, wait for elements, handle authentication flows'
Include common tool names and file extensions users might mention: 'Playwright, Puppeteer, Selenium, .spec.ts, test automation'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (browser automation) and lists some actions (E2E tests, web scraping, UI testing), but these are high-level categories rather than concrete specific actions like 'fill forms' or 'extract tables'. | 2 / 3 |
Completeness | Only addresses 'what' at a high level; completely missing a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'E2E tests', 'web scraping', 'UI testing', but missing common variations users might say such as 'Playwright', 'Puppeteer', 'Selenium', 'automate browser', 'click buttons', 'fill forms on websites'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Web scraping' could overlap with general HTTP/API skills, and 'UI testing' is somewhat generic. However, 'browser automation' and 'E2E tests' provide some distinctiveness for this domain. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, executable Playwright examples with good coverage of common patterns (selectors, waits, page objects, scraping). However, it includes unnecessary persona framing and capability lists that Claude already knows, and lacks explicit validation/debugging workflows for handling test failures or scraping errors. The content would benefit from trimming the fluff and adding error handling guidance.
Suggestions
Remove the persona introduction and 'Core Capabilities' bullet list - Claude knows what Playwright does
Add a debugging/validation workflow section: what to do when tests fail, how to diagnose flaky tests, retry strategies
Split advanced topics (API interception, mobile emulation, video recording) into separate reference files since they're mentioned but not covered
Remove the closing tagline - it adds no instructional value
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary elements like the persona framing ('You are Playwright Master'), the tagline at the end, and the 'Core Capabilities' bullet list which Claude already knows about Playwright. | 2 / 3 |
Actionability | Provides fully executable TypeScript code examples that are copy-paste ready, including complete test structures, selector patterns, wait strategies, page object patterns, and a web scraping example with proper imports and async handling. | 3 / 3 |
Workflow Clarity | The test examples show clear patterns (Navigate → Interact → Assert), but there's no explicit workflow for debugging failed tests, no validation checkpoints for scraping operations, and no guidance on error recovery or retry strategies for flaky tests. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear section headers, but everything is inline in one file. For a skill of this size (~100 lines of content), advanced topics like API interception, mobile emulation, and video recording mentioned in capabilities could be split into separate reference files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
91%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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 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.