SkillsBot.org

agent-browser vs Playwright CLI vs browser-use

Vercel's agent-browser, Microsoft's Playwright CLI and browser-use all let Claude drive a real browser. We gave each the same booking job on a tricky page, twice, alongside plain Claude, and checked the booking code it reported.

Tested by SkillsBot.org on . Same task, same settings, every skill installed on its own.

Our head-to-head test

We asked three browser skills to book a tour on the same page

All four set-ups booked the tour correctly in both runs. The page had a cookie banner to accept, tour times that loaded after a delay, dropdowns, a promo code and a confirmation pop-up. The difference was the setup. agent-browser was the only skill whose own tool was installed and used. Installing playwright-cli or browser-use with the skills command did not install their command-line tools. With playwright-cli, Claude used Playwright's built-in CLI instead. With browser-use, it fell back to writing Playwright scripts, so the browser-use tool itself never ran. Plain Claude was fastest because our machine already had Playwright installed; on a machine without it, you would need to install something first.

  • Works out of the boxagent-browserClaude installed agent-browser itself and drove the page with it in both runs (56 and 30 seconds).
  • If you already use Playwrightplaywright-cliWorked through npx playwright cli. It blocks file:// pages, so Claude served the page over local HTTP. The slowest: about 69 seconds.
  • Install its tool firstbrowser-useThe skill expects the browser-use command, which the skills install does not add. Both runs fell back to Playwright.

The task, word for word

Open booking.html in this folder in a real browser and book the 14:30 tour for 2 adults and 1 child, lead name Sam Lee, with promo code SAVE10. Confirm the booking, save a screenshot of the confirmation as booked.png, and tell me the booking code and the amount paid. Don't ask me questions; make reasonable choices and finish.

Results

SkillUsed it by itselfRun 1Run 2TimeAPI cost
No skill (plain Claude)
Claude Code with no skill installed
—right booking, screenshot savedright booking, screenshot saved22 s$0.18
agent-browser
by Vercel · 1,541,483 installs
2 of 2 runsright booking, screenshot savedright booking, screenshot saved43 s$0.23
playwright-cli
by Microsoft · 217,858 installs
2 of 2 runsright booking, screenshot savedright booking, screenshot saved1 min 8 s$0.32
browser-use
by Browser Use · 99,806 installs
2 of 2 runsright booking, screenshot savedright booking, screenshot saved34 s$0.20

Our machine had Chrome and the Playwright library preinstalled, which favours plain Claude. “Used it by itself” counts runs where Claude invoked the skill without being told to. When it did not, we ran the task again with the skill called by name and report that run instead, marked “called by name”. Time and cost are averages over the runs.

No skill (plain Claude)

Booking confirmation screenshot taken by plain Claude

agent-browser

Booking confirmation screenshot taken with agent-browser

playwright-cli

Booking confirmation screenshot taken with Playwright CLI

browser-use

Booking confirmation screenshot taken in the browser-use run
booked.png from run 1 of each: the same confirmation, with the same booking code, every time.

No skill (plain Claude)

Claude Code with no skill installed

  • Wrote a short Node script with Playwright: run 1 used the copy already on our machine, run 2 installed playwright-core and used the Chrome already installed.
  • Fastest in both runs (22 and 23 seconds).
  • Depends on Playwright being installed; the skills below exist partly to avoid that.

agent-browser

by Vercel · 1,541,483 installs

  • Loaded its real instructions from the CLI (agent-browser skills get core), as the skill tells it to.
  • Installed the CLI globally with npm in run 1; run 2 reused that install, which is part of why it was faster.
  • Clicked through the page using element references from accessibility snapshots.

playwright-cli

by Microsoft · 217,858 installs

  • The playwright-cli command was not installed, so Claude followed the skill's fallback and used npx playwright cli.
  • That CLI refuses file:// pages, so Claude started a local web server to open the page.
  • Worked step by step from page snapshots; the slowest of the four.

browser-use

by Browser Use · 99,806 installs

  • The browser-use command was not found in either run.
  • Claude installed Playwright for Python in a virtual environment and wrote a script instead.
  • The booking worked, but the browser-use tool itself never ran.

Each skill was installed alone with its own install command in a fresh folder, and the same prompt was run 2 times per skill plus 2 times with no skill, in Claude Code 2.1.326 in headless mode on November 17, 2026. Results come from checks we ran after each run: whether the reply contained the correct booking code (worked out from the page's own code) and the amount paid (£40.50), and whether booked.png was saved. How we test skills. Every skill we have tested.

Each skill is made and maintained by its own author, named above. SkillsBot.org is an independent directory and is not affiliated with any of them.

How to choose

You want it to work without extra setup: agent-browser. Claude installed the CLI itself with npm and used it in both runs. Its skill file is a short stub that loads the real instructions from the installed CLI, so they always match your version.

Your project already uses Playwright: Playwright CLI. The skill tells Claude to use npx playwright cli when Playwright is installed. Note that it blocks file:// pages, so local files need a local web server.

You want browser-use: install its command-line tool first (the skill's metadata installs it with uv). The skills install command adds only the instructions, and without the tool Claude fell back to plain Playwright scripts.

Do you need a browser skill at all?

If Playwright is already on your machine, plain Claude can write a script and was the fastest here. The skills help most when it is not, and on pages where step-by-step snapshots beat a one-shot script.

agent-browser vs Playwright CLI vs browser-use: FAQ

Is agent-browser better than Playwright CLI?

Both booked correctly in both runs. agent-browser worked with less setup and was faster here (about 43 seconds against 68); Playwright CLI suits projects that already use Playwright.

Does installing the browser-use skill install browser-use?

No. The skills command adds the SKILL.md only. Install the browser-use CLI separately, or Claude will fall back to other tools, as it did in both of our runs.

Why can Playwright CLI not open my local HTML file?

It blocks the file:// protocol. Serve the folder over HTTP, for example with python3 -m http.server, and open the localhost address.

Which browser skill is cheapest?

All were between about $0.18 and $0.32 per run on this task. Playwright CLI cost the most because it worked through more steps.