Browser

CDP scripts to start Chrome, navigate, run JS, screenshot, and pick DOM elements (macOS)

Tested · Works

Test report

Verdict
Tested · Works
Score
8.4/10
Tested
Jul 31, 2026
Environment
Claude Code 2.x (agent harness)
Upstream re-checked
Aug 10, 2026 · c1c7425

Cloned the repo and ran `npm install` (puppeteer-core, 0 vulnerabilities, postinstall chmod made all 5 scripts +x). To avoid start.js's `killall 'Google Chrome'` disrupting the user's live browser, I launched an isolated headless Chrome on :9222 with a temp profile and ran nav.js/eval.js/screenshot.js directly — all worked (title, link counts, IIFE object extraction, PNG to tmp). OUTPUT: on JS-rendered quotes.toscrape.com/js, baseline `curl` of raw HTML matched 0 quotes and 0 authors, while nav.js+eval.js extracted 10 quotes and author "Albert Einstein" from the rendered DOM — a decisive, quotable difference. Docked install/docs because start.js hardcodes macOS-only paths and force-kills the running Chrome, which the docs only hint at in a code comment; no malware, curl|sh, or exfiltration found.

Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works

  • Installs cleanly 4/5
  • Triggers reliably 5/5
  • Output vs. baseline 8/10
  • Docs & honesty 4/5

What Browser does

A set of Node.js puppeteer-core scripts that drive a real Chrome over the DevTools Protocol on port 9222: start Chrome, navigate tabs, evaluate JavaScript in the rendered page, take viewport screenshots, and interactively pick DOM elements. Triggers on requests to browse or scrape a website, take a page screenshot, automate a browser, or extract the rendered DOM. Because it runs JS against the live rendered page, it reads content that raw HTTP fetches miss; note the scripts hardcode macOS Chrome paths and start.js kills your running Chrome.

How to install Browser

git clone --depth 1 https://github.com/iamzhihuix/happy-claude-skills.git /tmp/browser-src
mkdir -p ~/.claude/skills
cp -R /tmp/browser-src/skills/browser ~/.claude/skills/browser
npm install --prefix ~/.claude/skills/browser
# Requires macOS + Google Chrome desktop at /Applications/Google Chrome.app (paths hardcoded in scripts/start.js).
# WARNING: start.js runs `killall 'Google Chrome'` then relaunches Chrome on :9222; it closes your existing Chrome windows.
# --profile rsyncs your real Chrome profile (cookies/logins) into ~/.cache/browser-tools.
# Scripts: start.js [--profile] | nav.js <url> [--new] | eval.js '<expr>' | screenshot.js | pick.js '<msg>'

Skills live in ~/.claude/skills/ (global) or .claude/skills/ (per-project). Restart Claude Code after installing.

Commands — how to trigger Browser

  • /browser CDP scripts to start Chrome, navigate, run JS, screenshot, and pick DOM elements (macOS)

It also activates on plain-language prompts like these:

  • Take a screenshot of this webpage
  • Scrape the product listings from this page
  • Extract the DOM structure of this site

Frequently asked questions

Is the Browser skill free?
Yes. The skill itself is free from iamzhihuix/happy-claude-skills. SkillProof publishes the install command and an independent test verdict at no cost.
Does Browser work with Claude Code?
We tested it with Claude Code 2.x (agent harness) on Jul 31, 2026. Verdict: Tested · Works. Cloned the repo and ran `npm install` (puppeteer-core, 0 vulnerabilities, postinstall chmod made all 5 scripts +x). To avoid start.js's `killall 'Google Chrome'` disrupting the user's live browser, I launched an isolated headless Chrome on :9222 with a temp profile and ran nav.js/eval.js/screenshot.js directly — all worked (title, link counts, IIFE object extraction, PNG to tmp). OUTPUT: on JS-rendered quotes.toscrape.com/js, baseline `curl` of raw HTML matched 0 quotes and 0 authors, while nav.js+eval.js extracted 10 quotes and author "Albert Einstein" from the rendered DOM — a decisive, quotable difference. Docked install/docs because start.js hardcodes macOS-only paths and force-kills the running Chrome, which the docs only hint at in a code comment; no malware, curl|sh, or exfiltration found.
What is the Browser SkillProof Score?
8.4/10 — installs cleanly 4/5, triggers reliably 5/5, output vs. baseline 8/10, docs & honesty 4/5.
How do I install Browser?
Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
Can I use Browser with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.