Agent skill · software engineering · aiskillstore
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.
Why this skill is useful
Adds specific commands and workflows for browser automation and interaction that the AI wouldn't reliably generate on its own.
What it needs
Requires chrome installed locally. Requires browser-use account access. About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Browser Use Direct browser control via CDP. For task-specific edits, use agent-workspace/agenthelpers.py. For setup, install, or connection problems, read https://github.com/browser-use/browser-harness/blob/main/install.md. When Not to Use A basic fetch of public information needs no browser. If a plain HTTP request can read it — a public page, an API, docs — use curl or your fetch tool, and leave the browser alone. Use browser-use when the task needs interaction (click, type, navigate), the user's logged-in session, JS rendering, or a bot-protected page. If a direct fetch fails or returns a shell page, then escalate to the browser. Domain skills are off by default. Set BHDOMAINSKILLS=1 to enable them; see the bottom section. If BHDOMAINSKILLS=1 and the task is site-specific, read every file in the matching $BHAGENTWORKSPACE/domain-skills/<site>/ directory before inventing an approach. Usage Invoke as browser-use. Use heredocs for multi-line commands. Helpers are pre-imported. run.py calls ensuredaemon() before exec. First navigation is newtab(url), not gotourl(url). The normal local flow attaches to the running Chrome/Chromium CDP endpoint. No browser ids or local profile selection. Local Chrome If the daemon cannot connect, run diagnostics: If Chrome is not running at all, the harness launches it automatically and retries — no user action needed beyond clicking Allow if a permission popup appears. If Chrome is running but remote debugging is not enabled, the harness opens: Ask the user to tick "Allow remote debugging for this browser instance" and click Allow if Chrome shows a permission popup. Then retry the same browser-use command. Remote Browsers Use Browser Use cloud for headless servers, parallel sub-agents, or isolated work. Cloud browsers are managed Chrome instances hosted by Browser Use. Each one is a fresh, isolated browser. Proactively suggest one (briefly explain why) when: The user wants multiple concurrent tasks. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/browser-use--fefdb2