Curated Category 9 hand-picked skills Updated

Browser Automation for AI Coding Agents

Select the right browser automation tool for your agent's task: use the two-card default core for general browser interaction and local app QA, then choose a conditional specialist for Playwright infrastructure, a signed-in Chromium browser, profile attachment, safety isolation, remote cloud sessions, or DevTools diagnostics.

Illustration of a terminal connected to a browser window, representing agent-driven browser automation

How this guide is structured

  • Two-card default core.agent-browser for general page driving and webapp-testing for local web app QA. Together, they form the standard baseline.
  • Conditional alternatives. Seven specialist skills cover Playwright integration, active profile attachment, signed-in user-browser sessions, safety gates, remote cloud browsers, and DevTools diagnostics. Every card states why it is conditional.
  • Browser-only scope. This guide excludes scraping and data-extraction tools. Its cards serve interactive website automation, UI testing, browser-session control, or browser diagnostics.

The ten skills at a glance

A comparative index of the top picks. Click any card to navigate directly to its detailed review.

Install counts from the skills.sh registry, snapshot taken July 2026.

Default Core Skills

Recommended Baseline

The recommended two-card baseline for general browser interaction and local web application QA.

GitHub repository card for vercel-labs/agent-browser

agent-browser

728.7K installs Vercel Labs

Best for: General browser driving and low-token page interaction

agent-browser talks to Chrome directly over the DevTools Protocol without a heavy browser framework. Its core loop relies on accessibility tree snapshots that assign short refs (@e1, @e2) to interactive elements, keeping LLM token overhead minimal.

It provides commands for navigation, form filling, screenshots, and state persistence across multi-step browser tasks.

  • Accessibility tree snapshots keep prompt context small
  • Direct CDP CLI with no Playwright runtime overhead
  • Parallel sessions for multi-agent workflows
  • Official Vercel Labs skill with 728K+ registry installs
Install this skill
$npx skills add vercel-labs/agent-browser --skill agent-browser
vercel-labs/agent-browser skills.sh listing skills/agent-browser/SKILL.md
Works with + more
GitHub repository card for anthropics/skills

webapp-testing

141.2K installs Anthropic

Best for: Local web app end-to-end testing during active development

Anthropic's official skill for local web app QA. It guides agents to write native Python Playwright scripts using a reconnaissance-then-action workflow to test dynamic frontend features.

Includes a bundled with_server.py helper that handles starting and stopping local development servers around test execution.

  • Official Anthropic skill for UI verification
  • Automatic server lifecycle management during test runs
  • Reconnaissance-then-action pattern for dynamic DOMs
  • Captures screenshots and console logs for bug reporting
Install this skill
$npx skills add anthropics/skills --skill webapp-testing
anthropics/skills skills.sh listing skills/webapp-testing/SKILL.md
Works with + more

Conditional Alternatives

Specialist skills for Playwright integration, existing Chrome profiles, user-browser sessions, session safety, remote cloud browsers, and DevTools diagnostics. Each card explicitly states why it is conditional rather than default core.

GitHub repository card for microsoft/playwright-cli

playwright-cli

131.1K installs Microsoft

Best for: Projects with existing Playwright testing infrastructure

Why not default: Conditional on Playwright ecosystem: Select this when your repository already relies on Playwright testing setup or requires cross-browser engine support rather than direct CDP execution.

Maintained by Microsoft's Playwright team, this skill wraps the Playwright engine into single-purpose CLI commands for clicking, typing, and navigating.

Inherits Playwright's auto-waiting and cross-browser engine features while using element refs for compact LLM prompts.

  • Maintained by the Playwright team at Microsoft
  • Built-in auto-waiting and cross-browser support
  • Integrates cleanly with existing Playwright test suites
  • Element ref snapshot interface
Install this skill
$npx skills add microsoft/playwright-cli --skill playwright-cli
microsoft/playwright-cli skills.sh listing skills/playwright-cli/SKILL.md
Works with + more
GitHub repository card for currents-dev/playwright-best-practices-skill

playwright-best-practices

75.5K installs Currents

Best for: Authoring, refactoring, and debugging Playwright test suites

Why not default: Not a browser driver: This is a pure knowledge skill containing Playwright reference guides, not an executable browser driving tool.

A comprehensive reference skill by Currents covering locators, fixtures, Page Object Model, flaky test debugging, and CI optimization.

Provides contextual guidance for complex scenarios like WebSockets, accessibility testing, and visual regression.

  • Activity-based index across 40+ Playwright reference guides
  • Deep guidance on flaky tests and async wait patterns
  • Covers visual regression, accessibility, and API mocking
  • Written by Playwright CI observability engineers at Currents
Install this skill
$npx skills add currents-dev/playwright-best-practices-skill --skill playwright-best-practices
currents-dev/playwright-best-practices-skill skills.sh listing playwright-best-practices/SKILL.md
Works with + more
GitHub repository card for browser-use/browser-use

browser-use

92.3K installs Browser Use

Best for: Scripting actions in your logged-in local Chrome profile

Why not default: Conditional on Chrome profile attachment: Requires connecting to an existing logged-in Chrome profile with Python scripts rather than clean isolated execution.

browser-use allows agents to write Python snippets that execute against a running Chrome browser, preserving existing logins and session cookies.

Features a built-in doctor command for environment connection diagnostics and site-specific domain pattern libraries.

  • Attaches to your existing Chrome profile with active sessions
  • Python heredoc interface with pre-imported helpers
  • Built-in connection diagnostic doctor command
  • Site-specific automation pattern modules
Install this skill
$npx skills add browser-use/browser-use --skill browser-use
browser-use/browser-use skills.sh listing skills/browser-use/SKILL.md
Works with + more
GitHub repository card for tencent/browserskill

browser-skill

216 installs Tencent

Best for: Automating a website with an existing signed-in browser session while keeping user tabs explicit

Why not default: Conditional on an existing signed-in Chromium browser: Requires the bsk CLI and browser extension, and uses explicit tab borrowing for user tabs.

browser-skill automates the user's logged-in Chromium browser through an Agent Window. Its primary workflow covers reading pages, filling forms, operating tabs, testing a UI, and debugging a website with the user's existing logins.

The skill requires the bsk CLI and browser extension. It makes session ownership explicit, requires fresh page observations before interaction, and returns borrowed tabs when the session stops.

  • Uses a logged-in Chromium browser in an Agent Window
  • Reads pages, fills forms, operates tabs, and tests a UI
  • Explicit borrowing and return of user tabs
  • Fresh page refs before browser interaction
Install this skill
$npx skills add https://github.com/tencent/browserskill --skill browser-skill
tencent/browserskill skills.sh listing crates/bsk-cli/skill/SKILL.md
Works with + more
GitHub repository card for browser-act/skills

browser-act

107.8K installs BrowserAct

Best for: Multi-account isolation and privacy-sensitive operations

Why not default: Conditional on safety and isolation gates: Enforces Confirmation Gate user approvals and isolated profile sessions, adding human-in-the-loop steps for sensitive tasks.

browser-act prioritizes privacy and session safety through its Confirmation Gate protocol, requiring user approval before executing sensitive browser operations.

Supports isolated multi-browser profiles for parallel account management alongside network HAR/XHR capture capabilities.

  • Confirmation Gate protocol requires explicit approvals
  • Strict local-only storage for credentials and cookies
  • Isolated multi-browser profiles for parallel account work
  • Network waterfall capture (HAR, XHR, fetch)
Install this skill
$npx skills add browser-act/skills --skill browser-act
browser-act/skills skills.sh listing browser-act/SKILL.md
Works with + more
GitHub repository card for browserbase/skills

browser (Browserbase)

5.5K installs Browserbase

Best for: Protected sites requiring cloud proxies and CAPTCHA solving

Why not default: Conditional on remote cloud infrastructure: Requires external Browserbase cloud API keys and remote infrastructure for stealth proxies and CAPTCHA handling.

Browserbase's skill drives the browse CLI, enabling switching between local Chrome instances and remote Browserbase cloud sessions.

Remote cloud sessions provide stealth features like automatic CAPTCHA solving, residential proxies, and Browserbase Identity verification.

  • Switch between local Chrome and cloud sessions per command
  • Automatic CAPTCHA solving and residential proxy support
  • Attach to active debuggable Chrome instances
  • Designed for bot-protected and complex targets
Install this skill
$npx skills add browserbase/skills --skill browser
browserbase/skills skills.sh listing skills/browser/SKILL.md
Works with + more
GitHub repository card for ChromeDevTools/chrome-devtools-mcp

chrome-devtools

6.3K installs Chrome DevTools team

Best for: Performance traces, memory leak profiling, and network debugging

Why not default: Conditional on deep diagnostics: Tailored for low-level DevTools performance profiling and memory analysis rather than routine page driving or app QA.

Official MCP server from the Chrome DevTools team giving agents deep access to performance traces, network request inspection, and heap snapshots.

Encourages routing large trace files and diagnostic outputs directly to disk to prevent context window pollution.

  • Built and maintained by the Chrome DevTools team
  • Performance profiling, network waterfalls, and memory dumps
  • Disk output routing keeps large traces out of context
  • Includes sibling skills for LCP and accessibility debugging
Install this skill
$npx skills add ChromeDevTools/chrome-devtools-mcp --skill chrome-devtools
ChromeDevTools/chrome-devtools-mcp skills.sh listing skills/chrome-devtools/SKILL.md
Works with + more

Browser Skill Selection Guide

Start by choosing the browser target—an existing signed-in profile, a clean isolated profile, or a remote session—and review browser engine and profile tradeoffs. Then route your implementation based on exact requirements rather than generic lists:

General Automation

Choose agent-browser (Default Core) for direct CDP navigation with low token overhead via accessibility tree refs.

Local App QA

Choose webapp-testing (Default Core) for Anthropic's Playwright test workflow with automated local server lifecycle control.

Playwright Ecosystem

Use playwright-cli for CLI Playwright execution, or playwright-best-practices for authoring and debugging suites.

Profile Attachment

Choose browser-use when your agent needs to operate inside your active, logged-in local Chrome profile.

Isolation & Safety

Choose browser-act for Confirmation Gate approvals and isolated multi-browser profile environments.

Remote Cloud Browsing

Choose browser (Browserbase) when accessing protected sites requiring residential proxies and CAPTCHA solving.

Diagnostics & Memory

Choose chrome-devtools for DevTools MCP server performance profiling, memory leak detection, and network waterfalls.

Signed-In Chromium

Choose browser-skill when the agent must use an existing signed-in Chromium browser through an Agent Window with explicit tab borrowing.

Manage your skills with LazySkills

As you install browser automation and testing skills, LazySkills helps you manage them from your terminal. It shows which skills are installed, verifies per-agent visibility (Claude Code, Cursor, Codex, opencode), and flags configuration issues.

curl -fsSL https://lazyskills.sh/install | sh
Learn more about LazySkills

Frequently Asked Questions

What is the recommended default setup for browser automation?

Start with the two-card default core: agent-browser for general page interaction and direct CDP browser control, and webapp-testing for local application QA and end-to-end test execution with server lifecycle management.

When should I choose Playwright over the direct CDP default?

Choose playwright-cli if your project already uses Playwright infrastructure and needs Playwright's cross-browser engine features. Add playwright-best-practices when your agent needs reference guides for writing, refactoring, or fixing Playwright test suites.

How do profile attachment and isolation skills differ?

browser-use attaches directly to your running local Chrome instance to preserve active logins and session state. browser-act focuses on safety and isolation, providing Confirmation Gate approvals and separate multi-account browser environments.

When are remote cloud browsers or DevTools diagnostics required?

Use browser (Browserbase) when targeting protected websites that require remote cloud browsers, residential proxies, or automatic CAPTCHA solving. Use chrome-devtools when you need low-level performance profiling, memory leak detection, or network waterfall traces.

When does browser-skill fit better than the default core?

Use browser-skill when the task must operate a user's existing signed-in Chromium browser and needs an Agent Window, explicit tab borrowing, or a browser extension. It covers reading pages, filling forms, tab operation, UI testing, and website debugging, but requires the bsk CLI and extension.

How do I install these skills for my AI agent?

Every skill installs via the open skills CLI using the exact command listed on its card (e.g. npx skills add vercel-labs/agent-browser --skill agent-browser). LazySkills allows you to manage installed skills and inspect per-agent visibility from your terminal.

Related guides

More curated skill catalogs to keep browsing.

by Alvin