mb is a browser CLI where each command is a small Unix tool. It talks to Chrome over CDP (port 9222) via puppeteer-core.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionmini-browserExecute the skills CLI command in your project's root directory to begin installation:
Fetches mini-browser from runablehq/mini-browser and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate mini-browser. Access via /mini-browser in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
28
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
28
stars
mb is a browser CLI where each command is a small Unix tool. It talks to Chrome over CDP (port 9222) via puppeteer-core.
Setup is only needed when mb is not installed or Chrome is not reachable.
Run these checks first — if both pass, skip straight to the Command Reference.
# 1. Is mb installed?
which mb && echo "mb: ok" || echo "mb: MISSING"
# 2. Is Chrome listening on CDP?
curl -sf http://127.0.0.1:9222/json/version > /dev/null && echo "chrome: ok" || echo "chrome: NOT RUNNING"
If both print "ok", everything is ready — go use mb commands directly.
mb is missing)npm install -g @runablehq/mini-browser
mb-start-chrome
This launches Chrome with --remote-debugging-port=9222, a fresh profile, and a
1024×768 window. It no-ops if Chrome is already running.
To kill and relaunch:
mb-restart-chrome
mb go "https://example.com" && mb text
| Variable | Default | Description |
|---|---|---|
CHROME_PORT |
9222 |
CDP port |
CHROME_BIN |
auto-detected | Path to Chrome/Chromium binary |
CHROME_PID_FILE |
<scripts>/.chrome-pid |
PID file location |
CHROME_USER_DATA_DIR |
<scripts>/.chrome-profile |
Chrome profile directory |
| Command | Description |
|---|---|
mb go <url> |
Navigate to URL (waits for networkidle) |
mb url |
Print current URL |
mb back |
Go back |
mb forward |
Go forward |
| Command | Description |
|---|---|
mb text [selector] |
Visible text content (default: body) |
mb shot [file] |
Screenshot to PNG (default: ./shot.png) |
mb snap |
List interactive elements with coordinates |
| Command | Description |
|---|---|
mb click <x> <y> |
Click at coordinates |
mb type [x y] <text> |
Type text (with coords: selects first) |
mb fill <k=v...> |
Fill form fields by label/name/placeholder |
mb key <key...> |
Press keys (Enter, Tab, Meta+a) |
mb move <x> <y> |
Hover at coordinates |
mb drag <x1> <y1> <x2> <y2> |
Drag between points |
mb scroll [dir] [px] |
Scroll (default: down 500) |
| Command | Description |
|---|---|
mb record start <file> |
Start recording (.webm, .mp4, .gif) |
mb record stop |
Stop recording and save |
mb record status |
Check if recording is active |
| Command | Description |
|---|---|
mb tab list |
List open tabs |
mb tab new [url] |
Open new tab, print index |
mb tab close [n] |
Close tab (default: last) |
| Command | Description |
|---|---|
mb js <code> |
Run JavaScript in page context |
mb wait <target> |
Wait for ms / selector / networkidle / url:pattern |
mb audit |
Design audit (palette, typography, contrast, a11y, SEO) |
mb logs |
Stream console logs (Ctrl+C to stop) |
| Flag | Default | Description |
|---|---|---|
--timeout <ms> |
30000 | Command timeout |
--tab <n> |
0 | Target tab index |
--json |
false | Structured JSON output |
--right |
false | Right-click |
--double |
false | Double-click |
--fps <n> |
30 | Recording frame rate |
--scale <n> |
1 | Recording scale factor |
The standard agent loop: snapshot the page, pick an element, act on it.
mb snap # list interactive elements with (x, y)
mb click 512 380 # click the button at those coordinates
mb wait networkidle # wait for the page to settle
mb snap # observe again
mb go "https://example.com/login"
mb fill "[email protected]" "Password=hunter2"
mb key Enter
mb wait url:/dashboard
mb shot page.png
mb text "main" # text from <main>
mb text "#content" # text from #content
mb text # full body text
mb js 'document.title'
echo 'document.querySelectorAll("a").length' | mb js -
mb record start demo.mp4 --fps 30 --scale 1
# ... interact with the page ...
mb record stop
mb audit # human-readable report
mb audit --json # structured JSON output
Cookie banners and modals block clicks. Remove them with JS:
mb js 'document.querySelector("[class*=cookie]")?.remove()'
mb wait 2000 # sleep 2 seconds
mb wait ".modal" # wait for selector to appear
mb wait networkidle # wait for no network activity
mb wait url:/dashboard # wait for URL to contain string
snap only returns elements in the current viewport — scroll and snap again to find more.text uses querySelector — returns first match only. Use text "main" over text "p" for better results.go waits for networkidle. For heavy SPAs, follow up with wait ".selector".type with coordinates triple-clicks first to select existing text, then types the replacement.fill field matching order: aria-label → placeholder → name attr → id → label text → CSS selector (use #/./[ prefix).--json output: snap → [{role, name, x, y, state}], tab list → [{index, url, title}], logs → JSON lines, audit → full audit object.~/.mb-recorder.json. Only one recording at a time.tab close cannot close the last remaining tab.| Problem | Fix |
|---|---|
| "Chrome not found" | Set CHROME_BIN=/path/to/chrome |
| Connection refused | Run mb-start-chrome first |
| Stale recording state | Delete ~/.mb-recorder.json |
| Chrome window wrong size | mb-restart-chrome (creates fresh profile) |
| Element not in snap output | mb scroll down 500 then mb snap again |
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
manaflow-ai/cmux
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Solid pick for teams standardizing on skills: mini-browser is focused, and the summary matches what you get after install.
mini-browser reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend mini-browser for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: mini-browser is focused, and the summary matches what you get after install.
mini-browser has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in mini-browser — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
mini-browser fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for mini-browser matched our evaluation — installs cleanly and behaves as described in the markdown.
mini-browser is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in mini-browser — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 31