browser-automation
You are a browser automation expert who has debugged thousands of flaky tests and built scrapers that run for years without breaking. You've seen the evolution from Selenium to Puppeteer to Playwright and understand exactly when each tool shines.
37
Quality
22%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/browser-automation/SKILL.mdQuality
Discovery
22%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 description reads as a persona/resume statement rather than a functional skill description. It uses first/second person framing ('You are') which violates the third-person voice requirement, lacks concrete actions, and provides no guidance on when to use the skill. The technical tool names provide some searchability but don't compensate for the missing structure.
Suggestions
Rewrite in third person with concrete actions: 'Automates browser interactions using Playwright/Puppeteer/Selenium. Builds web scrapers, handles dynamic content, debugs flaky tests, and manages browser sessions.'
Add explicit trigger guidance: 'Use when the user mentions browser automation, web scraping, Playwright, Puppeteer, Selenium, or needs to automate clicking, form filling, or data extraction from websites.'
Include natural user phrases: Add terms like 'scrape website', 'automate clicking', 'extract data from webpage', 'headless browser' that users would naturally say.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'browser automation expert' and 'debugged thousands of flaky tests' without listing any concrete actions. It describes persona/experience rather than specific capabilities like 'automate form filling' or 'scrape web data'. | 1 / 3 |
Completeness | The description only vaguely addresses 'what' (browser automation expertise) and completely lacks any 'when' guidance. There is no 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('Selenium', 'Puppeteer', 'Playwright', 'browser automation', 'scrapers', 'flaky tests') but these are more technical jargon than natural user phrases. Missing common terms like 'web scraping', 'automate browser', 'click buttons', 'fill forms'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of specific tools (Selenium, Puppeteer, Playwright) provides some distinctiveness, but 'browser automation' and 'scrapers' are broad enough to potentially overlap with general web development or testing skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content appears incomplete or corrupted - it's truncated mid-sentence and the Sharp Edges table contains placeholder 'Issue' text instead of actual issues. While the structure shows promise with clear sections for patterns and anti-patterns, there's virtually no executable code, no concrete examples, and no actionable guidance that would help Claude perform browser automation tasks.
Suggestions
Add complete, executable Playwright code examples for each pattern (e.g., show actual user-facing locator syntax like `page.getByRole('button', { name: 'Submit' })`)
Replace placeholder 'Issue' text in Sharp Edges table with actual issues (e.g., 'Arbitrary timeouts', 'CSS selectors for dynamic content') and provide complete code solutions
Complete the truncated 'For scraping, yo' section with concrete scraping workflow steps including rate limiting and stealth configuration
Add a Quick Start section with a minimal working example that demonstrates the core auto-wait and user-facing locator patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content includes some unnecessary persona description at the top that Claude doesn't need, but the patterns/anti-patterns sections are reasonably concise. The 'core insight' paragraph adds value but could be tighter. | 2 / 3 |
Actionability | The skill is severely lacking in concrete, executable guidance. Pattern names are listed without code examples, anti-patterns have no code showing what to avoid or do instead, and the Sharp Edges table has placeholder 'Issue' text with solution comments but no actual code. | 1 / 3 |
Workflow Clarity | There is no clear workflow or sequence of steps. The content appears truncated ('For scraping, yo') and the Sharp Edges table contains placeholder text rather than actual guidance. No validation checkpoints or process flows are defined. | 1 / 3 |
Progressive Disclosure | The document has reasonable section structure (Capabilities, Patterns, Anti-Patterns, Sharp Edges, Related Skills) but lacks any references to detailed documentation. The content that exists is all inline with no signposting to deeper resources. | 2 / 3 |
Total | 6 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
9c177eb
- 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.