chrome-devtools · oakoss — Claude Code skill: browser control and setup
chrome-devtools is a Claude Code skill that controls a real Chrome session through an extension or DevTools MCP to fill forms, inspect pages, and debug web apps. It works with an existing browser session.
MIT 145 installs ★ 29 updated 2026-08-17
npx skills add oakoss/agent-skills --skill chrome-devtools -a claude-codeWhat chrome-devtools does
The skill connects an agent to Chrome with your current signed-in session. The extension can navigate pages, manage tabs and forms, extract page content, and run recurring tasks on a schedule. DevTools MCP provides browser controls and access to browser state.
The extension route requires Google Chrome and the Claude Code CLI; it does not work with Brave, Arc, or Edge. DevTools MCP needs Node.js 20.19 or later and supports headless operation. CAPTCHAs and modal dialogs require manual handling. Start Claude Code with claude --chrome to enable browser tools for that session.
What it helps with
- fill forms in an authenticated browser session
- collect page data and inspect DOM state
- trace console errors and failed network requests
- save a browser workflow for recurring runs
Example prompts for the agent
- Open the page in Chrome and fill in the form using the values I give for the Name and Company fields.
- Inspect this web app for console errors and failed network requests.
- Collect the requested data from several Chrome pages and save the steps as a reusable workflow.
How to install chrome-devtools
1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill chrome-devtools -a claude-code2Manually: put the files in place
~/.claude/skills/chrome-devtools/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/chrome-devtools/
1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill chrome-devtools -a codex2Manually: put the files in place
.agents/skills/chrome-devtools/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill chrome-devtools -a cursor2Manually: put the files in place
.cursor/skills/chrome-devtools/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install oakoss/agent-skills skills/chrome-devtools2Manually: put the files in place
.github/skills/chrome-devtools/SKILL.md1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill chrome-devtools -a gemini-cli2Platform CLI
gemini skills install https://github.com/oakoss/agent-skills --path skills/chrome-devtoolsManually: put the files in place
.devin/skills/chrome-devtools/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill chrome-devtools -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
How do I install chrome-devtools in Claude Code?
Run npx skills add oakoss/agent-skills --skill chrome-devtools -a claude-code. The skill file is placed at ~/.claude/skills/chrome-devtools/SKILL.md.
What does chrome-devtools do?
It lets an agent control a real Chrome browser through an extension or DevTools MCP. Use it to work with tabs and forms, extract page data, or inspect browser logs.
What does chrome-devtools require?
The extension route requires the latest stable Google Chrome, Claude Code CLI 2.0.73+, and a Claude Pro, Team, or Enterprise plan. DevTools MCP requires Node.js 20.19+.
Source text
SKILL.md · MIT
--- name: chrome-devtools description: 'Browser automation via Chrome extension and DevTools MCP. Use when controlling a logged-in Chrome browser, automating workflows, filling forms, extracting data, debugging web apps, reading console logs, or running scheduled browser tasks. Use for browser testing, form automation, data extraction, web scraping, authenticated browsing.' license: MIT metadata: author: oakoss version: '1.0' user-invocable: false --- # Chrome DevTools Skill Control a real Chrome browser with Claude. The Chrome extension runs inside an authenticated browser session, allowing interaction with sites the user is already logged into -- Gmail, Google Docs, Notion, CRMs, and more. ## Overview Two integration paths exist: Claude Code + Chrome Extension (terminal-based browser control via `claude --chrome`) and Chrome DevTools MCP (26 browser automation tools via Model Context Protocol). Both operate on a real Chrome instance with existing logins, requiring no re-authentication. The Chrome extension also supports workflow shortcuts, scheduled recurring tasks, and multi-tab coordination independently of Claude Code. ## Quick Reference | Integration | Setup | Best For | | ----------------------- | ---------------------------------------------------------------------------- | ------------------------------------- | | Claude Code + Extension | `claude --chrome` | Terminal-based browser control | | Chrome DevTools MCP | `claude mcp add chrome-devtools --scope user npx chrome-devtools-mcp@latest` | Programmatic automation via MCP tools | | Capability | Tools/Methods | | ---------- | -------------------------------------------------------------------- | | Navigation | Navigate URLs, create/close/switch tabs, resize windows | | Input | Click, type, fill forms, drag, hover, press keys, upload files | | Extraction | Read page content, DOM state, console logs, network requests | | Debugging | Screenshots, DOM snapshots, evaluate JavaScript, performance tracing | | Emulation | Device emulation, viewport resizing | | Recording | Record browser interactions as GIFs, save workflow shortcuts | | Scheduling | Workflow shortcuts with daily/weekly/monthly/annual triggers | | Requirement | Minimum | | -------------------------- | ------------------------ | | Google Chrome | Latest stable | | Claude in Chrome Extension | 1.0.36+ | | Claude Code CLI | 2.0.73+ | | Claude Plan | Pro, Team, or Enterprise | | Node.js (DevTools MCP) | 20.19+ | **Not supported**: Other Chromium browsers (Brave, Arc, Edge), WSL, headless mode (extension path only; DevTools MCP supports headless), mobile devices. ## Common Mistakes | Mistake | Correct Pattern | | -------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | | Running browser automation without `--chrome` flag | Start Claude Code with `claude --chrome` or enable Chrome by default via `/chrome` settings | | Trying to take over existing tabs | Claude opens new tabs for tasks; it does not hijack tabs you already have open | | Not handling CAPTCHAs and modal dialogs manually | Claude pauses at CAPTCHAs, login prompts, and modals; dismiss them yourself then tell Claude to continue | | Using ambiguous instructions for form filling | Be specific about field names, values, and order; ambiguous prompts produce inconsistent results | | Requesting all console logs without filtering | Specify log patterns or error types; requesting everything floods context with noise | | Enabling Chrome by default without need | Increases context usage since browser tools are always loaded; use `--chrome` flag only when needed | | Using DevTools MCP without `--scope user` | Add `--scope user` to make the MCP server available across all projects | ## Delegation - **Automate repetitive browser workflows across sites**: Use `Task` agent with Chrome extension to fill forms, extract data, or navigate multi-step flows - **Debug frontend issues with console and network inspection**: Use `Explore` agent with DevTools MCP to capture console errors, network failures, and DOM state - **Plan complex multi-tab data extraction pipelines**: Use `Plan` agent to design the workflow steps before executing browser automation - **Record and schedule recurring browser tasks**: Use Chrome extension shortcuts with scheduling for daily/weekly automation ## References - [Claude Code Chrome integration](references/claude-code-integration.md) -- setup, capabilities, and how the extension communicates with Claude Code - [Chrome DevTools MCP tools](references/devtools-mcp.md) -- all 26 MCP tools organized by category with configuration options - [Browser automation workflows](references/automation-workflows.md) -- common patterns for testing, data extraction, and content management - [Workflow shortcuts and scheduling](references/shortcuts-scheduling.md) -- creating reusable shortcuts and scheduled recurring tasks - [Troubleshooting and best practices](references/troubleshooting.md) -- fixing connection issues, handling dialogs, and security considerations
© oakoss · MIT · oakoss/agent-skills
Similar skills
All skills for Browser and scraping →chrome-devtools by other authors comes first.