Browser Automation

Modern browser automation comes down to two tools: Playwright for most use cases, Puppeteer when you need Chrome-specific stealth features. This skill teaches the fundamentals that separate reliable automation from flaky scripts. You'll learn user-facing locators (getByRole over CSS selectors), proper waiting strategies that don't rely on arbitrary timeouts, and anti-detection patterns for scraping. The examples cover testing isolated contexts, handling authentication state, and the critical distinction between controlled testing environments versus hostile scraping targets. Playwright's auto-wait and cross-browser support make it the default choice in 2025.

skills.sh installs: 5.8K
GitHub stars: 43.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add sickn33/antigravity-awesome-skills --skill browser-automation --agent claude-code

Installs into .claude/skills of the current project.

Files

Browser Automation

Use the browser tool already selected by the user or installed in the project. Playwright, Puppeteer and Selenium have different integrations; choose from actual requirements rather than unsupported success-rate claims. Modified by AAS maintainers on 2026-09-05: removed unverified comparisons and bypass defaults, clarified waiting and evidence limits.

Separate tests of applications you control from interaction with an existing authenticated browser. Do not replace the latter with a fresh unauthenticated session or extract credentials to make an automation test work.

Detailed Guide

Read the detailed guide before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.