[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F699SF9PS1MFJSHYZX4025":3,"skill-same:01M7F699SF9PS1MFJSHYZX4025":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7F699SF9PS1MFJSHYZX4025","troubleshooting",null,"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.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Ftroubleshooting\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: troubleshooting\ndescription: 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.\n---\n\n## Troubleshooting Wizard\n\nYou 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 `list_pages`, `new_page`, or `navigate_page` failed, or the server wouldn't start), follow this step-by-step diagnostic process:\n\n### Step 1: Find and Read Configuration\n\nYour 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\u002Fsettings.json`, `.vscode\u002Flaunch.json`, or `.gemini\u002Fsettings.json`.\n\nIf you find a configuration file, read and interpret it to identify potential issues such as:\n\n- Incorrect arguments or flags.\n- Missing environment variables.\n- Usage of `--autoConnect` in incompatible environments.\n\nIf you cannot find any of these files, only then should you ask the user to provide their configuration file content.\n\n### Step 2: Triage Common Connection Errors\n\nBefore reading documentation or suggesting configuration changes, check if the error message matches one of the following common patterns.\n\n#### Error: `Could not find DevToolsActivePort`\n\nThis 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.\n\nYour 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:\n\n1. **Ask the user to confirm that the correct Chrome version** (e.g., \"Chrome Canary\" if the error mentions it) is currently running.\n2. **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:\u002F\u002Finspect\u002F#remote-debugging`, and make sure the 'Enable remote debugging' checkbox is checked.\"\n3. **Once the user confirms both steps, your only next action should be to call the `list_pages` tool.** This is the simplest and safest way to verify if the connection is now successful. Do not retry the original, more complex command yet.\n4. **If `list_pages` succeeds, the problem is resolved.** If it still fails with the same error, then you can proceed to the more advanced steps like suggesting `--browserUrl` or checking for sandboxing issues.\n\n#### Symptom: Server starts but creates a new empty profile\n\nIf the server starts successfully but `list_pages` returns an empty list or creates a new profile instead of connecting to the existing Chrome instance, check for typos in the arguments.\n\n- **Check for flag typos:** For example, `--autoBronnect` instead of `--autoConnect`.\n- **Verify the configuration:** Ensure the arguments match the expected flags exactly.\n\n#### Symptom: Missing Tools \u002F Only 9 tools available\n\nIf the server starts successfully but only a limited subset of tools (like `list_pages`, `get_console_message`, `lighthouse_audit`, `take_heapsnapshot`) are available, this is likely because the MCP client is enforcing a **read-only mode**.\n\nAll tools in `chrome-devtools-mcp` are annotated with `readOnlyHint: true` (for safe, non-modifying tools) or `readOnlyHint: false` (for tools that modify browser state, like `emulate`, `click`, `navigate_page`). To access the full suite of tools, the user must disable read-only mode in their MCP client (e.g., by exiting \"Plan Mode\" in Gemini CLI or adjusting their client's tool safety settings).\n\n#### Symptom: Extension tools are missing or extensions fail to load\n\nIf the tools related to extensions (like `install_extension`) are not available, or if the extensions you load are not functioning:\n\n1. **Check for the `--categoryExtensions` flag**: Ensure this flag is passed in the MCP server configuration to enable the extension category tools.\n2. **Make sure the MCP server in configured to launch Chrome instead of connecting to an instance**: Chrome before 149 is not able to load extensions when connecting to an existing instance (`--auto-connect`, `--browserUrl`).\n\n#### Other Common Errors\n\nIdentify other error messages from the failed tool call or the MCP initialization logs:\n\n- `Target closed`\n- \"Tool not found\" (check if they are using `--slim` which only enables navigation and screenshot tools).\n- Missing `pageId`: Page-scoped tools require a `pageId` argument. Call `list_pages` to find active page IDs.\n- `ProtocolError: Network.enable timed out` or `The socket connection was closed unexpectedly`\n- `Error [ERR_MODULE_NOT_FOUND]: Cannot find module`\n- Any sandboxing or host validation errors.\n\n### Step 3: Read Known Issues\n\nRead the contents of https:\u002F\u002Fgithub.com\u002FChromeDevTools\u002Fchrome-devtools-mcp\u002Fblob\u002Fmain\u002Fdocs\u002Ftroubleshooting.md to map the error to a known issue. Pay close attention to:\n\n- Sandboxing restrictions (macOS Seatbelt, Linux containers).\n- WSL requirements.\n- `--autoConnect` handshakes, timeouts, and requirements (requires **running** Chrome 144+).\n\n### Step 4: Formulate a Configuration\n\nBased on the exact error and the user's environment (OS, MCP client), formulate the correct MCP configuration snippet. Check if they need to:\n\n- Pass `--browser-url=http:\u002F\u002F127.0.0.1:9222` instead of `--autoConnect` (e.g. if they are in a sandboxed environment like Claude Desktop).\n- Enable remote debugging in Chrome (`chrome:\u002F\u002Finspect\u002F#remote-debugging`) and accept the connection prompt. **Ask the user to verify this is enabled if using `--autoConnect`.**\n- Add `--logFile \u003Cabsolute_path_to_log_file>` to capture debug logs for analysis.\n- Increase `startup_timeout_ms` (e.g. to 20000) if using Codex on Windows.\n\n_If you are unsure of the user's configuration, ask the user to provide their current MCP server JSON configuration._\n\n### Step 5: Run Diagnostic Commands\n\nIf the issue is still unclear, run diagnostic commands to test the server directly:\n\n- Run `npx chrome-devtools-mcp@latest --help` to verify the installation and Node.js environment.\n- If you need more information, run `DEBUG=* npx chrome-devtools-mcp@latest --logFile=\u002Ftmp\u002Fcdm-test.log` to capture verbose logs. Analyze the output for errors.\n\n### Step 6: Check GitHub for Existing Issues\n\nIf https:\u002F\u002Fgithub.com\u002FChromeDevTools\u002Fchrome-devtools-mcp\u002Fblob\u002Fmain\u002Fdocs\u002Ftroubleshooting.md does not cover the specific error, check if the `gh` (GitHub CLI) tool is available in the environment. If so, search the GitHub repository for similar issues:\n`gh issue list --repo ChromeDevTools\u002Fchrome-devtools-mcp --search \"\u003Cerror snippet>\" --state all`\n\nAlternatively, you can recommend that the user checks https:\u002F\u002Fgithub.com\u002FChromeDevTools\u002Fchrome-devtools-mcp\u002Fissues and https:\u002F\u002Fgithub.com\u002FChromeDevTools\u002Fchrome-devtools-mcp\u002Fdiscussions for help.\n","## Troubleshooting Wizard\n\nYou 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 `list_pages`, `new_page`, or `navigate_page` failed, or the server wouldn't start), follow this step-by-step diagnostic process:\n\n### Step 1: Find and Read Configuration\n\nYour 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\u002Fsettings.json`, `.vscode\u002Flaunch.json`, or `.gemini\u002Fsettings.json`.\n\nIf you find a configuration file, read and interpret it to identify potential issues such as:\n\n- Incorrect arguments or flags.\n- Missing environment variables.\n- Usage of `--autoConnect` in incompatible environments.\n\nIf you cannot find any of these files, only then should you ask the user to provide their configuration file content.\n\n### Step 2: Triage Common Connection Errors\n\nBefore reading documentation or suggesting configuration changes, check if the error message matches one of the following common patterns.\n\n#### Error: `Could not find DevToolsActivePort`\n\nThis 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.\n\nYour 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:\n\n1. **Ask the user to confirm that the correct Chrome version** (e.g., \"Chrome Canary\" if the error mentions it) is currently running.\n2. **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:\u002F\u002Finspect\u002F#remote-debugging`, and make sure the 'Enable remote debugging' checkbox is checked.\"\n3. **Once the user confirms both steps, your only next action should be to call the `list_pages` tool.** This is the simplest and safest way to verify if the connection is now successful. Do not retry the original, more complex command yet.\n4. **If `list_pages` succeeds, the problem is resolved.** If it still fails with the same error, then you can proceed to the more advanced steps like suggesting `--browserUrl` or checking for sandboxing issues.\n\n#### Symptom: Server starts but creates a new empty profile\n\nIf the server starts successfully but `list_pages` returns an empty list or creates a new profile instead of connecting to the existing Chrome instance, check for typos in the arguments.\n\n- **Check for flag typos:** For example, `--autoBronnect` instead of `--autoConnect`.\n- **Verify the configuration:** Ensure the arguments match the expected flags exactly.\n\n#### Symptom: Missing Tools \u002F Only 9 tools available\n\nIf the server starts successfully but only a limited subset of tools (like `list_pages`, `get_console_message`, `lighthouse_audit`, `take_heapsnapshot`) are available, this is likely because the MCP client is enforcing a **read-only mode**.\n\nAll tools in `chrome-devtools-mcp` are annotated with `readOnlyHint: true` (for safe, non-modifying tools) or `readOnlyHint: false` (for tools that modify browser state, like `emulate`, `click`, `navigate_page`). To access the full suite of tools, the user must disable read-only mode in their MCP client (e.g., by exiting \"Plan Mode\" in Gemini CLI or adjusting their client's tool safety settings).\n\n#### Symptom: Extension tools are missing or extensions fail to load\n\nIf the tools related to extensions (like `install_extension`) are not available, or if the extensions you load are not functioning:\n\n1. **Check for the `--categoryExtensions` flag**: Ensure this flag is passed in the MCP server configuration to enable the extension category tools.\n2. **Make sure the MCP server in configured to launch Chrome instead of connecting to an instance**: Chrome before 149 is not able to load extensions when connecting to an existing instance (`--auto-connect`, `--browserUrl`).\n\n#### Other Common Errors\n\nIdentify other error messages from the failed tool call or the MCP initialization logs:\n\n- `Target closed`\n- \"Tool not found\" (check if they are using `--slim` which only enables navigation and screenshot tools).\n- Missing `pageId`: Page-scoped tools require a `pageId` argument. Call `list_pages` to find active page IDs.\n- `ProtocolError: Network.enable timed out` or `The socket connection was closed unexpectedly`\n- `Error [ERR_MODULE_NOT_FOUND]: Cannot find module`\n- Any sandboxing or host validation errors.\n\n### Step 3: Read Known Issues\n\nRead the contents of https:\u002F\u002Fgithub.com\u002FChromeDevTools\u002Fchrome-devtools-mcp\u002Fblob\u002Fmain\u002Fdocs\u002Ftroubleshooting.md to map the error to a known issue. Pay close attention to:\n\n- Sandboxing restrictions (macOS Seatbelt, Linux containers).\n- WSL requirements.\n- `--autoConnect` handshakes, timeouts, and requirements (requires **running** Chrome 144+).\n\n### Step 4: Formulate a Configuration\n\nBased on the exact error and the user's environment (OS, MCP client), formulate the correct MCP configuration snippet. Check if they need to:\n\n- Pass `--browser-url=http:\u002F\u002F127.0.0.1:9222` instead of `--autoConnect` (e.g. if they are in a sandboxed environment like Claude Desktop).\n- Enable remote debugging in Chrome (`chrome:\u002F\u002Finspect\u002F#remote-debugging`) and accept the connection prompt. **Ask the user to verify this is enabled if using `--autoConnect`.**\n- Add `--logFile \u003Cabsolute_path_to_log_file>` to capture debug logs for analysis.\n- Increase `startup_timeout_ms` (e.g. to 20000) if using Codex on Windows.\n\n_If you are unsure of the user's configuration, ask the user to provide their current MCP server JSON configuration._\n\n### Step 5: Run Diagnostic Commands\n\nIf the issue is still unclear, run diagnostic commands to test the server directly:\n\n- Run `npx chrome-devtools-mcp@latest --help` to verify the installation and Node.js environment.\n- If you need more information, run `DEBUG=* npx chrome-devtools-mcp@latest --logFile=\u002Ftmp\u002Fcdm-test.log` to capture verbose logs. Analyze the output for errors.\n\n### Step 6: Check GitHub for Existing Issues\n\nIf https:\u002F\u002Fgithub.com\u002FChromeDevTools\u002Fchrome-devtools-mcp\u002Fblob\u002Fmain\u002Fdocs\u002Ftroubleshooting.md does not cover the specific error, check if the `gh` (GitHub CLI) tool is available in the environment. If so, search the GitHub repository for similar issues:\n`gh issue list --repo ChromeDevTools\u002Fchrome-devtools-mcp --search \"\u003Cerror snippet>\" --state all`\n\nAlternatively, you can recommend that the user checks https:\u002F\u002Fgithub.com\u002FChromeDevTools\u002Fchrome-devtools-mcp\u002Fissues and https:\u002F\u002Fgithub.com\u002FChromeDevTools\u002Fchrome-devtools-mcp\u002Fdiscussions for help.\n",{"name":5,"description":7},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Ftroubleshooting",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill troubleshooting",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill troubleshooting",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill troubleshooting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Ftroubleshooting\u002FSKILL.md",true,[],[47,54,59,66,73,80],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":55,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]