[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMNKYFJ626BD3GPR5PAPK3":3,"skill-same:01M7EMNKYFJ626BD3GPR5PAPK3":45},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7EMNKYFJ626BD3GPR5PAPK3","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.","baobao0303\u002FRoom_Agent","baobao0303","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F110554959?v=4","01M7EMJ6GAWBRY5JNAH4PKB10S","Lê Tấn Bảo Bảo","01M7EMJ6H0FDB2MW9G9CS2FDX4",0,"MIT","https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fpeer\u002Fskills\u002Ftroubleshooting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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_memory_snapshot`) 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#### 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- `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_memory_snapshot`) 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#### 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- `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","9a0e463878cc8f95f6e1e54f8773a42697a3fe34","profiles\u002Fpeer\u002Fskills\u002Ftroubleshooting","https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent","https:\u002F\u002Fgithub.com\u002Fbaobao0303","baobao22.work@gmail.com","2026-11-06 10:30:30",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add baobao0303\u002FRoom_Agent --skill troubleshooting",{"tool":37,"command":38},"bunx","bunx skills add baobao0303\u002FRoom_Agent --skill troubleshooting",{"tool":40,"command":41},"pnpm","pnpm dlx skills add baobao0303\u002FRoom_Agent --skill troubleshooting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fpeer\u002Fskills\u002Ftroubleshooting\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7EMX6PB6T8J2NZ21CXTRA7E","workflow-launch-exec","Launch, orchestrate, and drive end-to-end multi-agent pipelines (BA -> DESIGN -> DEV -> VERIFY) for any task.","https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fsupervisor\u002Fskills\u002Floop-and-orchestration\u002Fworkflow-launch-exec\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7EMX3197ZW7G22MV6A7K8M2","paseo-handoff","Hand off the current task to another agent with full context. Use when the user says \"handoff\", \"hand off\", \"hand this to\", or wants to pass work to another agent.","https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fsupervisor\u002Fskills\u002Floop-and-orchestration\u002Fpaseo-handoff\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7EMWZSS3TX7MJYQYZMNCCJF","loop-me","Grill me about specs for the workflows I want to build, within this workspace.","https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fsupervisor\u002Fskills\u002Floop-and-orchestration\u002Floop-me\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7EMWPP2C0D3QW8A274JQE75","loop-engineering","Use when the user wants Claude Code to keep working on its own until a goal is met — a self-running loop instead of write→wait→review→re-prompt. Helps decide if a loop is even worth building, picks manual vs automatic and open vs closed, distinguishes \u002Fgoal vs \u002Floop vs routines (\u002Fschedule), and wires up a CLOSED loop with a real verification gate (Stop hook running tests, or an LLM-judge + rubric when output isn't testable) plus a turn\u002Fbudget ceiling so it never spins forever. Triggers on \"loop\", \"döngü\", \"loop engineering\", \"auto mode\", \"run until tests pass\", \"self-running \u002F autonomous agent\", \"\u002Fgoal\", \"Stop hook\", \"ralph wiggum\".","https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fsupervisor\u002Fskills\u002Floop-and-orchestration\u002Floop-engineering\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7EMWKJ1JJ0T1P8Q09H3YFM6","handoff","Compact the current conversation into a handoff document for another agent to pick up.","https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fsupervisor\u002Fskills\u002Floop-and-orchestration\u002Fhandoff\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7EMWGSXRRGVZFQZYR4DKWHW","claude-handoff","Hand the current conversation off to a fresh background agent that picks up the work immediately.","https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fsupervisor\u002Fskills\u002Floop-and-orchestration\u002Fclaude-handoff\u002FSKILL.md",[],[]]