mini-browser

runablehq/mini-browser · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/runablehq/mini-browser --skill mini-browser
0 commentsdiscussion
summary

mb is a browser CLI where each command is a small Unix tool. It talks to Chrome over CDP (port 9222) via puppeteer-core.

skill.md

mini-browser (mb) — Browser CLI for Agents

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 (only if not already available)

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.

Check if ready

# 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.

Install (only if mb is missing)

npm install -g @runablehq/mini-browser

Start Chrome (only if not running)

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

Verify

mb go "https://example.com" && mb text

Environment Variables

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 Reference

Navigation

Command Description
mb go <url> Navigate to URL (waits for networkidle)
mb url Print current URL
mb back Go back
mb forward Go forward

Observation

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

Interaction

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)

Recording

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

Tabs

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)

Other

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)

Flags

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

Usage Patterns

Observe → Act loop

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

Fill and submit a form

mb go "https://example.com/login"
mb fill "[email protected]" "Password=hunter2"
mb key Enter
mb wait url:/dashboard

Take a screenshot

mb shot page.png

Extract text

mb text "main"                   # text from <main>
mb text "#content"               # text from #content
mb text                          # full body text

Run JavaScript

mb js 'document.title'
echo 'document.querySelectorAll("a").length' | mb js -

Record a screencast

mb record start demo.mp4 --fps 30 --scale 1
# ... interact with the page ...
mb record stop

Design audit

mb audit                         # human-readable report
mb audit --json                  # structured JSON output

Dismiss overlays

Cookie banners and modals block clicks. Remove them with JS:

mb js 'document.querySelector("[class*=cookie]")?.remove()'

Wait strategies

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

Important Notes

  • Viewport is 1024×768. 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.
  • Recording state is stored in ~/.mb-recorder.json. Only one recording at a time.
  • tab close cannot close the last remaining tab.

Troubleshooting

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
how to use mini-browser

How to use mini-browser on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add mini-browser
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/runablehq/mini-browser --skill mini-browser

The skills CLI fetches mini-browser from GitHub repository runablehq/mini-browser and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/mini-browser

Reload or restart Cursor to activate mini-browser. Access the skill through slash commands (e.g., /mini-browser) or your agent's skill management interface.

Security & Verification Notice

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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

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

Competitive Analysis

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

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

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

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ 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.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.731 reviews
  • Amelia Shah· Dec 16, 2024

    Solid pick for teams standardizing on skills: mini-browser is focused, and the summary matches what you get after install.

  • Harper Shah· Dec 12, 2024

    mini-browser reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Hassan Srinivasan· Dec 12, 2024

    I recommend mini-browser for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Yash Thakker· Nov 19, 2024

    Solid pick for teams standardizing on skills: mini-browser is focused, and the summary matches what you get after install.

  • Kwame Sethi· Nov 3, 2024

    mini-browser has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Hassan White· Nov 3, 2024

    Useful defaults in mini-browser — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Aanya Desai· Oct 22, 2024

    mini-browser fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Noah Ramirez· Oct 22, 2024

    Registry listing for mini-browser matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Dhruvi Jain· Oct 10, 2024

    mini-browser is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Piyush G· Sep 25, 2024

    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

1 / 4