Item: chrome-browser
Rating: 5.1
Author: Implexa

chrome-browser

Browser automation with two integrations - Chrome DevTools MCP (always available, performance tracing) and Claude-in-Chrome extension (authenticated sessions,…

copies: implexa run skills.sh/chrome-browser

view source

installs

stars

karma

SkillRank score ↗

5.1/ 10

evaluated by implexa, claude-haiku-4-5 · 2026-05-27

chrome-browser provides automation via two mcp integrations (devtools for testing, claude-in-chrome for authenticated sessions), with guidance on recorder export, snapshot capture, and gif frame limits to avoid memory exhaustion.

structure

4.0

trigger phrases

3.0

procedure

5.0

edge cases

4.0

documentation

6.0

strengths

SKILL.md

Chrome Browser Automation

Installation

Standalone script: No download; the skill invokes .claude/tools/chrome-browser/chrome-browser.cjs (Node.js v18+ required).

MCP integrations (for full automation):

Chrome DevTools MCP: Usually bundled with the environment; ensure Chrome/Chromium is installed (google.com/chrome).

Claude-in-Chrome: Install the Claude-in-Chrome extension and run with --chrome when needed.

Cheat Sheet &#x26; Best Practices

Testing: Test user-visible behavior, not implementation. Isolate tests (own storage/cookies); use before/after hooks for login or setup. Mock third-party networks instead of depending on live services.

DevTools Recorder: Record flows in Recorder panel; export as JSON or test scripts (Puppeteer, Nightwatch). Replay with Puppeteer Replay in CI. Use for performance measurement of user flows.

Hacks: Prefer Chrome DevTools MCP for testing/debugging (always on); use Claude-in-Chrome for authenticated sessions (GIF, forms). Limit GIF frames (e.g. 100) to avoid memory issues. Use take_snapshot for structure; evaluate_script for custom checks.

don't have the plugin yet? install it then click "run inline in claude" again.

chrome-browser

SKILL.md

related skills