Browser Automation

by davila78da17d671b6fNo license32K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

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

Instructions onlySoftware Development
AI-generated overview

Guides browser automation with Playwright and Puppeteer for testing, scraping, and agentic browser control.

What it does
This skill provides guidance on browser automation using Playwright (recommended) and Puppeteer. It covers selector strategies, waiting patterns, test isolation, and anti-detection approaches, and lists common anti-patterns and sharp edges such as arbitrary timeouts and shared browser contexts. It is instruction-only and produces no files or scripts.
When to use it
Use it when writing or debugging browser automation for web testing, end-to-end testing, UI automation, or web scraping. It is also relevant when choosing between Playwright and Puppeteer or when dealing with flaky tests and detection systems.
Requirements
No scripts are shipped; it is instructions only. Following the guidance assumes access to Playwright or Puppeteer and a browser runtime, but the skill itself requires nothing beyond the agent.

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

Source and attribution

Source:davila7/claude-code-templatesincli-tool/components/skills/utilities/browser-automationat commit8da17d6

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Browser Automation Agent Skill | SourceWeft