chrome-devtools
chrome devtools
What it does
- For extension tooling, use the --categoryExtensions flag.
- For memory tooling, use the --memoryDebugging flag.
- Use filePath parameter for large outputs (screenshots, snapshots, traces)
- Use pagination (pageIdx, pageSize) and filtering (types) to minimize data
- Set includeSnapshot: false on input actions unless you need updated page state
- Automation/interaction: takesnapshot (text-based, faster, better for automation)
- Visual inspection: takescreenshot (when user needs to see visual state)
Requirements & configuration
- Set includeSnapshot: false on input actions unless you need updated page state
- Visual inspection: takescreenshot (when user needs to see visual state)
Derived from the skill's own SKILL.md documentation · extracted 2026-07-23
chrome-devtools FAQ
What does the chrome-devtools skill do?
Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to `--slim` mode (MCP configuration). For extension tooling, use the --categoryExtensions flag. For memory tooling, use the --memoryDebugging flag.
What does chrome-devtools require?
Set includeSnapshot: false on input actions unless you need updated page state Visual inspection: takescreenshot (when user needs to see visual state)
How do I install chrome-devtools?
Run: npx -y skills add https://github.com/chromedevtools/chrome-devtools-mcp --skill chrome-devtools --agent claude-code — the source lives at github.com/chromedevtools/chrome-devtools-mcp.
Maintain chrome-devtools?
Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.
[](https://getagentictools.com/skills/chromedevtools-chrome-devtools-mcp-chrome-devtools?ref=badge) npx agentictools info skills/chromedevtools-chrome-devtools-mcp-chrome-devtools The second line is the CLI lookup for this page — handy in READMEs and docs.