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
Target: Software development & testing. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Browser Automation
- Capabilities
- Patterns
- Test Isolation Pattern
- User-Facing Locator Pattern
- Auto-Wait Pattern
- Anti-Patterns
- ❌ Arbitrary Timeouts
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 browser-automation playwright puppeteer headless-browsers web-scraping browser-testing e2e-testing ui-automation selenium-alternatives Each test runs in complete isolation with fresh state Select elements the way users see them Let Playwright wait automatically, never add manual waits | 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 reque
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- davila7/claude-code-templates
- Source file
- cli-tool/components/skills/utilities/browser-automation/SKILL.md
- Fixed revision
- 21be197f100a12b8d0dd9a211cc244c8179f84d3
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: davila7/claude-code-templates · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-09T15:01:40.701Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.