Browser Automation
SkillWeb & browsingBrowser 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
Use Browser Automation in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Browser Automation and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Browser Automation skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
No other account needed.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
What this skill tells your AI
The instructions your AI receives, as published by agent-skills-hub/agent-skills-hub in skills/browser-automation/SKILL.md and read by ahel’s review.
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
Signals
- GitHub stars
- 109
- Forks
- 40
- Last commit
- Sep 2026
ahel recommends instead
Advanced
- Item type
- skill
- Key
browser-automation-agent-skills-hub- Source
- github.com/agent-skills-hub/agent-skills-hub
github.com/agent-skills-hub/agent-skills-hub
More in Web & browsing
Skill · browser-use
More in Web & browsingwebapp-testing
Skill · anthropics
More in Web & browsingplaywright-cli
Skill · microsoft
More in Web & browsingbenchmark
Skill · affaan-m
More in Web & browsingopen-source
Skill · browser-use
More in Web & browsingimpeccable
Skill · pbakaus
More in Web & browsing