chrome-devtools-mcp-automation — Claude Code skill
chrome-devtools-mcp-automation is a Claude Code skill for controlling Chrome through DevTools MCP. It applies to browser workflows, page debugging, and performance checks.
no license 239 installs ★ 9 updated 2026-10-09
npx skills add reason-machines/mcp-skills --skill chrome-devtools-mcp-automation -a claude-codeWhat chrome-devtools-mcp-automation does
The skill guides an agent through Chrome tasks using the Chrome DevTools MCP server. It can navigate pages, interact with controls, fill forms, and run JavaScript in the page context.
For debugging, the guidance covers console errors, network activity, and screenshots. Performance work includes trace recording, metrics, and Core Web Vitals. The chrome-devtools-mcp package must be installed; the server runs through npx.
What it helps with
- automate page navigation and browser interactions
- find JavaScript errors and failed network requests
- capture a page or element screenshot
- record a trace and collect performance metrics
Example prompts for the agent
- Check the checkout page in Chrome and find console and network errors.
- Complete the login form in Chrome and save a screenshot of the result.
- Record a page trace and collect its Core Web Vitals.
How to install chrome-devtools-mcp-automation
1Skills CLI (Vercel)
npx skills add reason-machines/mcp-skills --skill chrome-devtools-mcp-automation -a claude-code2Manually: put the files in place
~/.claude/skills/chrome-devtools-mcp-automation/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/chrome-devtools-mcp-automation/
1Skills CLI (Vercel)
npx skills add reason-machines/mcp-skills --skill chrome-devtools-mcp-automation -a codex2Manually: put the files in place
.agents/skills/chrome-devtools-mcp-automation/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add reason-machines/mcp-skills --skill chrome-devtools-mcp-automation -a cursor2Manually: put the files in place
.cursor/skills/chrome-devtools-mcp-automation/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install reason-machines/mcp-skills skills/chrome-devtools-mcp-automation2Manually: put the files in place
.github/skills/chrome-devtools-mcp-automation/SKILL.md1Skills CLI (Vercel)
npx skills add reason-machines/mcp-skills --skill chrome-devtools-mcp-automation -a gemini-cli2Platform CLI
gemini skills install https://github.com/reason-machines/mcp-skills --path skills/chrome-devtools-mcp-automationManually: put the files in place
.devin/skills/chrome-devtools-mcp-automation/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add reason-machines/mcp-skills --skill chrome-devtools-mcp-automation -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about chrome-devtools-mcp-automation
How do I install chrome-devtools-mcp-automation in Claude Code?
Run npx skills add reason-machines/mcp-skills --skill chrome-devtools-mcp-automation -a claude-code. The skill file will be at ~/.claude/skills/chrome-devtools-mcp-automation/SKILL.md.
What does chrome-devtools-mcp-automation do?
It gives an agent instructions for using Chrome through DevTools MCP to navigate pages, interact with them, debug issues, and inspect performance.
What does chrome-devtools-mcp-automation require?
It requires the chrome-devtools-mcp package, launched with npx, and Chrome. The server can connect to a browser instance that is already running.