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.
Quickly install troubleshooting AI skill to your development environment via command line
Source: chromedevtools/chrome-devtools-mcp.
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:
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:
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. Source: chromedevtools/chrome-devtools-mcp.
Stable fields and commands for AI/search citations.
npx skills add https://github.com/chromedevtools/chrome-devtools-mcp --skill troubleshootingUses 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. Source: chromedevtools/chrome-devtools-mcp.
Open your terminal or command line tool (Terminal, iTerm, Windows Terminal, etc.) Copy and run this command: npx skills add https://github.com/chromedevtools/chrome-devtools-mcp --skill troubleshooting Once installed, the skill will be automatically configured in your AI coding environment and ready to use in Claude Code, Cursor, or OpenClaw
https://github.com/chromedevtools/chrome-devtools-mcp