Browserbase Skills — Nine Recipes for Claude to Drive a Browser
Browserbase open-sourced its skills repo — nine pre-built Claude Code skills that let an agent operate a browser end-to-end. Anti-bot stealth and CAPTCHA solving in the browser skill. Serverless cloud automation deploy in the functions skill. A site-debugger skill that diagnoses and fixes failing automations. A trace skill that captures full DevTools protocol logs. Cookie sync from local Chrome to persistent contexts. UI test that does adversarial poking with an LLM in the loop.
The interesting design choice is shipping these as Skills, not as MCP servers or custom CLI bindings. Skills are Claude Code's progressive-disclosure unit — the agent sees a one-line description, pulls in the SKILL.md only when it decides the task fits. This is exactly the pattern obra/superpowers and mattpocock/skills demonstrated for general dev work, now applied to a single highly specialized vertical: browser automation under a real production cloud.
The broader play is obvious. Browserbase wants to be the default browser runtime for every Claude-driven web agent. Open-sourcing the skills is the cheapest way to get there — every Claude Code user trying "can the agent fill this form" becomes a Browserbase trial. Same playbook AWS used with the AWS CLI a decade ago, just with the agent as the user.
It also continues the pattern that the right interface for browser agents is not "give the agent the DOM" but "give the agent a small library of well-debugged playbooks." Site Debugger and Browser Trace are particularly nice — they assume things will break and give the agent the recovery path on the same shelf as the happy path. https://github.com/browserbase/skills
← Back to all articles
The interesting design choice is shipping these as Skills, not as MCP servers or custom CLI bindings. Skills are Claude Code's progressive-disclosure unit — the agent sees a one-line description, pulls in the SKILL.md only when it decides the task fits. This is exactly the pattern obra/superpowers and mattpocock/skills demonstrated for general dev work, now applied to a single highly specialized vertical: browser automation under a real production cloud.
The broader play is obvious. Browserbase wants to be the default browser runtime for every Claude-driven web agent. Open-sourcing the skills is the cheapest way to get there — every Claude Code user trying "can the agent fill this form" becomes a Browserbase trial. Same playbook AWS used with the AWS CLI a decade ago, just with the agent as the user.
It also continues the pattern that the right interface for browser agents is not "give the agent the DOM" but "give the agent a small library of well-debugged playbooks." Site Debugger and Browser Trace are particularly nice — they assume things will break and give the agent the recovery path on the same shelf as the happy path. https://github.com/browserbase/skills
Comments