browser-automation
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
Works with
--- name: browser-automation description: 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 license: MIT --- # 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`
More Testing skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
setup-pre-commit
mattpocock/skills
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

