chrome-devtools
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.
What this skill does
# 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
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.