chrome-devtools-cli
Use this skill to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via CLI.
Install
git clone https://github.com/ChromeDevTools/chrome-devtools-mcp /tmp/chrome-devtools-mcp && ln -s /tmp/chrome-devtools-mcp/skills/chrome-devtools-cli ~/.claude/skills/chrome-devtools-cli
From README
Note: If this is your very first time using the CLI, see references/ .md for . is a one-time prerequisite and is not part of the regular AI workflow. AI Workflow Execute: Run tools directly. If you don't know the target page's ID, run chrome-devtools listpages to find it. The background server starts implicitly; do not run start/status/stop before each use. Inspect: Use chrome-devtools takesnapshot to get an element . Act: Use chrome-devtools click , chrome-devtools fill , etc. State persists across commands. Snapshot example: Permissions & File Access By default, the CLI has full filesystem access (--allowUnrestrictedPaths=true), allowing file-saving parameters (--filePath, --outputDirPath) and uploadfile to access files anywhere on the system. Pass --allowUnrestrictedPaths=false if you want to restrict file access to the OS temp directory. Command Required arguments are passed positionally; optional arguments use flags. Use --help on any command for details.
More from this repo
chrome-devtools
Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation.
a11y-debugging
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools.
