What it solves
Persistent browser automation for agents using Chrome/Chromium, accessibility snapshots, and compact element refs.
When to use it
Adds real-browser operation when the bottleneck is reproducing or inspecting a live UI flow, not designing the whole E2E test suite.
Best fit
Developers who need an agent to open pages, inspect interactive elements, click through flows, and preserve browser session context during QA.
Where Apiara lists it
It is included in Software Development Skills under agent-driven browser investigation.
Before using it
Best started with the official `npx skills add vercel-labs/agent-browser` path and local `agent-browser --help`; avoid granting it access to sensitive logged-in sessions until commands and data handling are reviewed.