Web
An agent must inspect a live flow
Load the CLI's core workflow before navigating, snapshotting controls, or testing a form.
01 / The skill · Browser automation · Companion Skill
agent-browser Skill: a doorway to the browser CLI
This Skill is a small discovery stub. It tells an agent to load version-matched browser workflows from the installed agent-browser CLI; the CLI performs the actual actions.
Publisher, source, and installation
Published by Vercel Labs · Type: Companion Skill / discovery stub
Independent guide. Vercel Labs has not endorsed Floatboat.
Upstream installation
npx skills add vercel-labs/agent-browserThis adds the Skill stub only. Browser automation requires a separate agent-browser CLI installation and browser setup.
A realistic request
The repository's primary product is the agent-browser CLI, not this SKILL.md. The Skill points the agent to `agent-browser skills get core` and specialized workflows, keeping detailed instructions aligned with the installed tool version.
Ask the agent
“Use agent-browser to test the sign-in flow. Load the current core instructions first, then report the exact step that fails.”
A useful result
A useful result separates guidance loading from CLI execution and reports observed browser behavior, not an assumed pass.
When the companion Skill matters
Use it when an agent already has the CLI available and needs the matching workflow for a browser task.
QA
A bug needs exploratory reproduction
The stub points to a specialist dogfood workflow for exploratory testing and quality review.
Desktop
The target is an Electron app
Use the CLI's dedicated Electron guidance instead of assuming a normal web-page session.
What the stub cannot do alone
- Browser automation without the separate agent-browser CLI and browser setup.
- Treating this short SKILL.md as the complete command reference.
How the browser guidance is loaded
Install the Skill and CLI separately, then load the CLI's current core or specialized instructions.
- 01
Install the companion Skill
Add the published SKILL.md to a supported agent through the upstream Skills CLI.
- 02
Prepare the CLI
Install agent-browser and its browser dependency through the upstream tool instructions.
- 03
Load the matching workflow
Get core or specialist guidance from the CLI before interacting with the target.
02 / Practical guide
The Skill routes; the CLI acts
Treat the short SKILL.md as an entry point. The installed CLI serves current core and specialist workflows before commands are run.
Is agent-browser a Skill or a tool?
The repository's main deliverable is a browser-automation CLI. It also publishes a companion SKILL.md that tells agents how to discover version-matched workflows. This page describes that Skill entry, not the CLI as a standalone product.
Why is the SKILL.md intentionally short?
The source calls it a discovery stub. Detailed workflows are served by the installed CLI through `skills get core` or a specialist name, so instructions track the tool version instead of becoming stale copies.
What you can take away
- A version-matched browser workflow
- Observed states from CLI-driven interaction
- A clear split between Skill guidance and tool execution
What to check first
- Is the CLI actually installed?
- Did the agent load `skills get core`?
- Is the requested interaction authorized?
Upstream commands
These are upstream commands, not Floatboat features.
Install the CLI separately
npm i -g agent-browserThe Skill stub alone cannot run browser commands.
Set up the browser
agent-browser installFollow the CLI's upstream installation instructions.
Load current guidance
agent-browser skills get coreThe CLI serves instructions matched to its installed version.
Explore More Agent Skills
Read another Skill guide and check its original source before using it.
Frequently Asked Questions
Does installing the Skill install the browser CLI?
No. The Skill adds a short instruction stub. The agent-browser CLI and browser setup are separate installations.
Where are the full browser instructions?
The installed CLI serves them through
agent-browser skills get core and specialist workflows such as dogfood or electron.Why does the repository look like a tool?
Because it is primarily a CLI tool. The SKILL.md is a companion component for AI agents; the two should not be classified as the same deliverable.
Can the Skill run a browser by itself?
No. The CLI performs navigation, snapshots, and interactions. The Skill tells the agent which CLI-served workflow to read first.
03 / Put it to work · Plan browser work
Keep browser observations tied to the original task
Use Floatboat to collect the goal, observations, and review decisions; browser execution still depends on the separate upstream CLI.