Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →onyx-dot-app/browser
Core browser usage guide. Read this before running any 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.
Passed 16 of 21 test cases with the skill, and 7 of 21 without it.
and 13 more in the full report
10 fixed8 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to read documentation from https://docs.example.com/guide to extract heading outlines and content without launching Chrome or rendering JavaScript. Which command should I run?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends browser read to fetch document text without launching Chrome. | Missed | Passed |
| Uses --outline to extract document heading structures. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
Onyx Craft: for basic reads of static pages, prefer the
webfetchtool — it returns clean markdown, is faster, and is cheaper. Reach forbrowseronly when the page needs JavaScript/SPA rendering, interaction (clicks, forms, login), multi-step navigation, or visual inspection.Every
browsercommand is automatically pinned to THIS session's browser, so just use the plain commands below — do not pass--session. The browser is headless (the user does not see it); rely onsnapshotto read the page andscreenshotif you need to inspect it visually.This is a locked-down, display-less pod, so some workflows in this guide do not apply: ignore
--headed/ "show the browser window" (there is no display),--provider cloud-browser,browser plugin add, andbrowser doctor --fix(it would reinstall Chrome). Interactive 2FA that needs a visible window is not possible — drive auth throughsnapshot/fill/clickinstead.
browser open <url> # 1. Open a page
browser snapshot -i # 2. See what's on it (interactive elements only)
browser click @e3 # 3. Act on refs from the snapshot
browser snapshot -i # 4. Re-snapshot after any page change
Refs (@e1, @e2, ...) are assigned fresh on every snapshot. They become stale the moment the page changes — after clicks that navigate, form submits, dynamic re-renders, dialog opens. Always re-snapshot before your next ref interaction.
# Take a screenshot of a page
browser open https://example.com
browser screenshot home.png
browser close
# Search, click a result, and capture it
browser open https://duckduckgo.com
browser snapshot -i # find the search box ref
browser fill @e1 "browser cli"
browser press Enter
browser wait --load networkidle
browser snapshot -i # refs now reflect results
browser click @e5 # click a result
browser screenshot result.png
test cases passed, vs 7 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.