core
Core agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.
Install
git clone https://github.com/vercel-labs/agent-browser /tmp/agent-browser && ln -s /tmp/agent-browser/skill-data/core ~/.claude/skills/coreFrom README
agent-browser core Fast browser automation CLI for AI agents. Chrome/Chromium via CDP, no Playwright or Puppeteer dependency. Accessibility-tree snapshots with compact @eN refs let agents interact with pages in 200-400 tokens instead of parsing raw HTML. Most normal web tasks (navigate, read, click, fill, extract, screenshot) are covered here. Load a specialized skill when the task falls outside browser web pages — see When to load another skill. The core loop Open the page and check the response for a WebMCP summary. If an advertised tool directly matches the authorized task, prefer that tool to reconstructing the same operation with DOM interactions. Fetch only its metadata, check the input schema and intended effect against the user request, then invoke it: Browser responses automatically announce WebMCP tools on first discovery and when the catalog changes. Summaries contain only names, brief descriptions, origins, and frame IDs.