do-browser

Automates Chrome browser navigation, interaction, and inspection through the chrome-devtools-axi CLI.

2|Updated May 25, 2026
One-click install
npx skills add https://github.com/edheltzel/Do-Skills --skill do-browser-edheltzel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: do-browser
Source: https://github.com/edheltzel/Do-Skills/tree/main/skills/operations/do-browser
Command: npx skills add https://github.com/edheltzel/Do-Skills --skill do-browser-edheltzel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually testing web pages, filling forms, and debugging rendered output is repetitive and error-prone. This Skill drives a real Chrome browser through the installed chrome-devtools-axi CLI so an agent can open pages, interact with elements, capture screenshots, and inspect console or network activity deterministically. ## Core Features & Use Cases - Ref-based browser control: Open URLs, take accessibility snapshots, and click or fill elements using generation-scoped refs, with stale-ref recovery via fresh snapshots. - Story and recipe workflows: Validate YAML user stories with parallel reviewer agents (ReviewStories), execute parameterized Markdown recipes like form filling and screenshot comparison (Automate), and verify the installed tooling (Update). - Diagnostics and capture: Evaluate JavaScript, inspect console and network activity, resize viewports, run Lighthouse or performance audits, and save screenshots. - Use Case: After deploying a local dev server, ask the agent to review the stories in Stories/ExampleApp.yaml; it fans out reviewer agents that click through flows, assert on snapshots, and return a PASS/FAIL summary table with screenshots. ## Quick Start Ask the agent to open your local dev server URL in the browser, take a snapshot, and screenshot the result.

Frequently Asked Questions about do-browser

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

FAQPage Schema
How do I automate browser testing with chrome-devtools-axi?▼

Set BROWSER_CLI to the installed executable path, then run open with a URL, take a snapshot, and interact using the generation-prefixed refs it returns. Confirm every state-changing action with a fresh snapshot, eval, or screenshot, and run stop when finished.

How do I run automated user story validation on a web app?▼

Define stories as YAML files with steps and assertions, then trigger the ReviewStories workflow. It fans each story out to a parallel reviewer agent (up to eight at once) and aggregates PASS/FAIL results into a summary table with screenshot paths.

What is a STALE_REF error and how do I fix it?▼

A STALE_REF means the page rerendered and invalidated the element reference you used. Take a fresh snapshot to get replacement refs, then retry the action with the new generation-prefixed ref.

When should I use WebFetch instead of browser automation?▼

Use WebFetch when the page is public and static, since launching Chrome adds unnecessary overhead. Browser automation is for interactive tasks like form filling, clicking, screenshots, and console or network debugging.

Can this handle CAPTCHA or authenticated pages?▼

No. Pages blocked by CAPTCHA, bot detection, or complex authentication should be escalated to the do-interceptor skill, which uses real Chrome or Brave with macOS Computer Use. For simple logins, drive the browser to the human-only step and request that action.