Labsco
Labsco/Repos/browserbase/skills
REPO PACKAGE

browserbase skills

OFFICIAL
browserbase · publisher3,623 repository starsgithub.com/browserbase/skills
16skills
1ready to use

The fourteen automation skills split into a basic layer and a debugging layer. browser, browserbase-cli, functions, cookie-sync, fetch, and search cover the building blocks — opening a remote or local session, running platform API commands, deploying automation as a cloud function, reusing your logged-in cookies, and fetching a URL or a search result without a full browser. On top of that sit browser-trace and browser-to-api, which turn a captured run into a per-page trace or a best-effort OpenAPI spec; autobrowse, which iterates a task against its own trace until it passes; ui-test and agent-experience, which run adversarial QA and developer-experience audits; safe-browser, which builds a domain-allowlisted agent with no raw CDP access; webmcp-gen, which authors WebMCP init scripts; and browser-use-to-stagehand, which migrates existing browser-use (Python) scripts onto Stagehand v3.

company-research, competitor-analysis, and event-prospecting are a different product: all three call the Browserbase Search API to find companies or people, score them against a stated ICP, and compile the results into an HTML report — a target-company list, a competitor comparison with pricing and mentions, or a conference speaker list ranked by fit. None of the three build or test browser automation; they read as sales and GTM tooling that happens to ship in the same repository.

READ THE FULL ANALYSIS

One skill ships blind. browserbase-cli carries no description in its own frontmatter at all — the README says it wraps the same CLI for sessions, projects, contexts, extensions, and the dashboard, but nothing in the skill file itself tells an agent when to reach for it, so that characterization comes from the README rather than the skill's own trigger text.

What it costs to run any of them is not yet checked. All 17 skills carry an unverified dependency label rather than ready, account_key, or local_tool, so we can't yet say which ones need a Browserbase account and API key versus which run against a local Chrome profile with --local. Given that browse talks to Browserbase's own session infrastructure, assume most of the automation layer needs an account until that gets checked.

Checked from the repository's own skill files and README, 19 September 2026; we have not run any of the 17 end to end.

1Work with nothing else to set up.
3,623Stars on the GitHub repository, at last check.