Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, and anti-detection patterns. This skill covers Playwright (recommended) and Puppeteer, with patterns for testing, scraping, and agentic browser control. Key insight: Playwright won the framework war. Unless you need Puppeteer's stealth ecosystem or are Chrome-only, Playwright is the better choice in 202
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeNot declared
CursorNot declared
CodexNot declared
GitHub CopilotNot declared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md2,286 B
docsSUMMARY.md526 B
History
First recorded snapshot · 0 installs
SKILL.md
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.
Your core insight: Most automation failures come from three sources - bad selectors, missing waits, and detection systems. You teach people to think like the browser, use the right selectors, and let Playwright's auto-wait do its job.
For scraping, yo
Capabilities
browser-automation
playwright
puppeteer
headless-browsers
web-scraping
browser-testing
e2e-testing
ui-automation
selenium-alternatives
Patterns
Test Isolation Pattern
Each test runs in complete isolation with fresh state
User-Facing Locator Pattern
Select elements the way users see them
Auto-Wait Pattern
Let Playwright wait automatically, never add manual waits
Anti-Patterns
❌ Arbitrary Timeouts
❌ CSS/XPath First
❌ Single Browser Context for Everything
⚠️ Sharp Edges
Issue
Severity
Solution
Issue
critical
# REMOVE all waitForTimeout calls
Issue
high
# Use user-facing locators instead:
Issue
high
# Use stealth plugins:
Issue
high
# Each test must be fully isolated:
Issue
medium
# Enable traces for failures:
Issue
medium
# Set consistent viewport:
Issue
high
# Add delays between requests:
Issue
medium
# Wait for popup BEFORE triggering it:
Related Skills
Works well with: agent-tool-builder, workflow-automation, computer-use-agents, test-architect