mcpField
B
browser-automation

browser-automation

github.com/davila7Testing & quality33.0k751 installsUpdated 1d ago
Repository

About browser-automation

browser-automation is a skill for browser testing and web scraping with tools such as Playwright and Puppeteer. It focuses on locator choices, auto-waiting, and test isolation to address common automation failures.

Key features

  1. 01Playwright, Puppeteer, and Selenium automation
  2. 02Web scraping and end-to-end testing
  3. 03User-facing locator patterns
  4. 04Auto-wait and test-isolation guidance

Use cases

  1. 01Writing browser end-to-end tests
  2. 02Debugging flaky automation tests
  3. 03Building web-scraping workflows

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/davila7/claude-code-templates --skill browser-automation

After installing, type/browser-automationin Claude Code to confirm it loaded.

Details

From the project README

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

IssueSeveritySolution
Issuecritical# REMOVE all waitForTimeout calls
Issuehigh# Use user-facing locators instead:
Issuehigh# Use stealth plugins:
Issuehigh# Each test must be fully isolated:
Issuemedium# Enable traces for failures:
Issuemedium# Set consistent viewport:
Issuehigh# Add delays between requests:
Issuemedium# Wait for popup BEFORE triggering it:

Related Skills

Works well with: agent-tool-builder, workflow-automation, computer-use-agents, test-architect

Comments

Markdown supported