browser-usage

Automates browser interactions and E2E verification using Playwright MCP accessibility snapshots.

2|Updated Jul 18, 2026
One-click install
npx skills add https://github.com/Arasz/ai-badger --skill browser-usage-arasz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-usage
Source: https://github.com/Arasz/ai-badger/tree/main/features/common/skills/browser-usage
Command: npx skills add https://github.com/Arasz/ai-badger --skill browser-usage-arasz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @playwright/mcp.

What problem does it solve? Manually testing web UIs and verifying live application behavior is slow and error-prone, and brittle CSS-selector scripts break on every UI change. This Skill drives a real browser through Playwright MCP using text-first accessibility tree snapshots and stable element reference tokens, so agents can navigate, fill forms, inspect network traffic, and verify UI flows without vision models or fragile selectors. ## Core Features & Use Cases - Accessibility-Tree Interaction: Capture page structure with browser_snapshot and click, type, or select elements via [ref=eN] tokens instead of guessing CSS selectors. - Diagnostics & Verification: Inspect console messages, network requests with headers and payloads, and take screenshots to confirm UI state and API contract adherence. - Advanced Scenarios: Manage tabs, dialogs, and mobile viewports, or run custom Playwright code via browser_run_code_unsafe for multi-step assertions. - Use Case: After deploying a new checkout flow locally, navigate to the page, fill the form via batch field population, submit, wait for the confirmation text, and check the network log to verify the order API returned the expected payload. ## Quick Start Use the browser-usage skill to open http://localhost:5173, snapshot the page, fill in the login form, and verify the dashboard loads without console errors.

Frequently Asked Questions about browser-usage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate browser testing with Playwright MCP?

Navigate to the target URL with browser_navigate, capture the accessibility tree with browser_snapshot, then interact with elements using their ref tokens via browser_click, browser_type, or browser_fill_form. Verify outcomes with browser_wait_for and screenshots.

How to fill out web forms using Playwright MCP tools?

Use browser_fill_form with a map of element refs to values for batch population, or browser_type for single inputs and browser_select_option for dropdowns. Always snapshot first to obtain valid ref tokens for each field.

When should I not use a browser automation tool?

Skip the browser for plain HTTP REST calls or JSON fetching, where curl or API clients are faster, and for CI unit tests, where native runners like vitest or dotnet test are appropriate. Static documentation queries should read local files directly.

Why do Playwright MCP element refs stop working?

Element refs become stale after any navigation, form submission, dialog, or DOM mutation because the accessibility tree is regenerated. Re-capture browser_snapshot after every UI state change to obtain fresh ref tokens.

Does Playwright MCP work in headless CI environments?

Yes, pass --headless when running in containers or CI, since headed mode fails on Linux servers without a display server or Xvfb. It supports Chrome, Firefox, WebKit, and Edge engines via the --browser flag.

Is browser_run_code_unsafe safe to use?

It executes arbitrary JavaScript in the Playwright server process, which is RCE-equivalent. Only run trusted scripts and never interpolate unescaped external input into the code string.