Agent skill · data analytics · chromedevtools
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.
Why this skill is useful
Provides specific troubleshooting steps and domain knowledge for resolving Chrome DevTools MCP connection issues that the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-06. 48,655 stars on the source repository.
What this skill does
Troubleshooting Wizard You are acting as a troubleshooting wizard to help the user configure and fix their Chrome DevTools MCP server setup. 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, gemini-extension.json, .claude/settings.json, .vscode/launch.json, or .gemini/settings.json. If you find a configuration file, read and interpret it to identify potential issues such as: Incorrect arguments or flags. Missing environment variables. Usage 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. Step 2: Triage Common Connection Errors Before reading documentation or suggesting configuration changes, check if the error message matches one of the following common patterns. Error: Could not find DevToolsActivePort This error is highly specific to the --autoConnect feature. It means the MCP server cannot find the file created by a running, debuggable Chrome instance. This is not a generic connection failure. Your primary goal is to guide the user to ensure Chrome is running and properly configured. Do not immediately suggest switching to --browserUrl. Follow this exact sequence: 1. Ask the user to confirm that the correct Chrome version (e.g., "Chrome Canary" if the error mentions it) is currently running. 2. If the user confirms it is running, instruct them to enable remote debugging. Be very specific about the URL and the action: "Please open a new tab in Chrome, navigate to chrome://inspect/#remote-debugging, and make sure the 'Enable remote debugging' checkbox is checked." 3. Once the user confirms both steps, your only next action should be to call the listpages tool. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills chromedevtools/troubleshooting