Browser Use
Direct browser control via CDP for web interaction — automation, scraping, testing, screenshots
- What
- Direct browser control via CDP for web interaction — automation, scraping, testing, screenshots
- Cost
- Free
- Needs
- uv package manager; install via `uv tool install browser-use` (or the documented harness install); a Chrome/Chromium browser available
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the official browser-use skill: direct browser control through CDP via the `browser-use` CLI — navigate, click, type, scroll, take screenshots, extract rendered content, and run domain-specific site skills. Designed for tasks that need interaction, a logged-in session, JS rendering, or bot-protected pages; the skill explicitly says to prefer plain HTTP fetch when no interaction is needed. By @browser-use, listed here with credit to its creator. Honest caveats: requires the `browser-use` CLI installed (via uv) and a Chrome/Chromium setup; the agent workspace model means helpers are pre-imported and conventions matter (one working tab per task). Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: uv package manager; install via `uv tool install browser-use` (or the documented harness install); a Chrome/Chromium browser available Install "Browser Use" for me. Direct browser control via CDP for web interaction — automation, scraping, testing, screenshots Repository: https://github.com/browser-use/browser-use 1. Fetch the SKILL.md file for the browser-use-browser-use skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "browser-use-browser-use". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.