← Search

AutoBrowse — self-improving browser automation skill
Browser Automation 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit 6811ca3
Install test only, on the date shown. This does not guarantee the code is safe.
🔎 Install prompt analysis · 2026-10-13 : uses API keys or tokens
⚙ Needs: Node.js 18+, the browse CLI…

AutoBrowse — self-improving browser automation skill

Turn flaky browser tasks into reliable skills — an inner agent browses while the outer agent reads traces and improves the strategy until the task passes

At a glance
What
Turn flaky browser tasks into reliable skills — an inner agent browses while the outer agent reads traces and improves the strategy until the task passes
Cost
Free
Needs
Node.js 18+, the browse CLI, and an ANTHROPIC_API_KEY (each iteration burns real API calls); a Browserbase account for remote mode (paid cloud browsers) — the skill is guidance the agent follows, not software
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

AutoBrowse is a free Muse skill that turns flaky browser tasks into reliable skills through a self-improving auto-research loop. An inner agent browses a site while the outer agent reads the trace, forms one evidence-grounded hypothesis per iteration, and rewrites the navigation strategy until the task passes reliably.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 6811ca3

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: Node.js 18+, the browse CLI, and an ANTHROPIC_API_KEY (each iteration burns real API calls); a Browserbase account for remote mode (paid cloud browsers) — the skill is guidance the agent follows, not software Install "AutoBrowse — self-improving browser automation skill" for me. It gives my agent @browserbase's auto-research loop: an inner agent browses a site via the browse CLI while the outer agent reads traces, forms one evidence-grounded hypothesis per iteration, and rewrites strategy.md until the task passes reliably — multi-task parallel runs, optional CDP-traced mode, and a graduation step that turns a converged strategy into a self-contained Claude Code skill. IMPORTANT: no LICENSE file was detected in the repo (frontmatter states MIT) — fetch from the link only, and reproduce nothing beyond the link. Repository: https://raw.githubusercontent.com/browserbase/skills/6811ca31163332d9d60309cff48e77f09de37a17/skills/autobrowse/SKILL.md Pinned version: install the code at commit 6811ca31163332d9d60309cff48e77f09de37a17 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 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. 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 "autobrowse". 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. install the browse CLI, set ANTHROPIC_API_KEY, pick a task or URL to train; nothing else — it's a methodology). 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. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🧭 What this touches
  • It works with an API key or a token that you provide.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 6811ca3 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Install prompt analysis · 2026-10-13 : uses API keys or tokens
What the scan found — excerpts from the install prompt
  • uses API keys or tokens — Prerequisites: Node.js 18+, the browse CLI, and an ANTHROPIC_API_KEY (each iteration burns real API calls); a · Prérequis : Node.js 18+, la CLI browse, et une ANTHROPIC_API_KEY (chaque itération consomme de vrais appels AP
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
6811ca3 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : uses API keys or tokens

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

↔

See also

Compare: Automation skills for Muse →

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.