troubleshooting
Uses Chrome DevTools MCP and documentation to troubleshoot connection and target issues. Trigger this skill when list_pages, new_page, or navigate_page fail, or when the server initialization fails.
Install
git clone https://github.com/ChromeDevTools/chrome-devtools-mcp /tmp/chrome-devtools-mcp && ln -s /tmp/chrome-devtools-mcp/skills/troubleshooting ~/.claude/skills/troubleshootingFrom README
Troubleshooting Wizard You are acting as a troubleshooting wizard to help the user configure and fix their Chrome DevTools MCP server . When this skill is triggered (e.g., because listpages, newpage, or navigatepage failed, or the server wouldn't start), follow this step-by-step diagnostic process: Step 1: Find and Read Configuration Your first action should be to locate and read the MCP configuration file. Search for the following files in the user's workspace: .mcp.json, .vscode/mcp.json, gemini-extension.json, or .gemini/settings.json (or user-scoped files such as /.claude.json if accessible). If you find a configuration file, read and interpret it to identify potential issues such as: Incorrect arguments or flags. Missing environment variables. of --autoConnect in incompatible environments. If you cannot find any of these files, only then should you ask the user to provide their configuration file content.
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.
chrome-devtools-cli
Used to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via...