菜单
Use when about to use chrome-devtools MCP tools and Chrome connection fails or remote debugging needs to be enabled. Symptoms include "Could not connect to Chrome" or "Could not find DevToolsActivePort" errors.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/chenwei791129/agent-skills --skill chrome-devtools命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Operating Gmail through the `gws` (Google Workspace CLI) tool — reading, searching, labelling, archiving, deleting mail, and managing Gmail filters. Use this skill whenever a task involves triaging or reorganising a mailbox, building a label taxonomy, creating or editing Gmail filters, bulk-archiving or bulk-deleting messages, auditing what is cluttering an inbox, or any request phrased like "clean up my Gmail", "sort my inbox", "set up mail rules", "整理信箱", "建立郵件規則". Also use it whenever mail content will be summarised or acted on, because it carries the prompt-injection rules for untrusted message text. The Gmail API and the `gws` CLI have many sharp edges that silently produce wrong results — consult this skill before the first command, not after something breaks.
Evaluate whether a Claude Code skill improves task outcomes through repeated paired experiments, blind LLM judging, statistical tests, and a self-contained HTML report. Use when the user asks to benchmark, compare, validate, or quantify the effectiveness of a skill. This is a costly explicit-only workflow.
Install, reinstall, migrate, and verify Hermes Agent plugins, especially third-party standalone plugins under ~/.hermes/plugins.
基于 SOC 职业分类
正在显示 SKILL.md
| name | chrome-devtools |
| description | Use when about to use chrome-devtools MCP tools and Chrome connection fails or remote debugging needs to be enabled. Symptoms include "Could not connect to Chrome" or "Could not find DevToolsActivePort" errors. |
Chrome DevTools MCP requires Chrome running with remote debugging enabled. Without this, all mcp__chrome-devtools__* tool calls fail.
mcp__chrome-devtools__* toolRun the launch script via Bash tool:
~/.claude/skills/chrome-devtools/scripts/launch-chrome-debug.sh
The script handles everything automatically: quits existing Chrome, launches with debug flags, waits and verifies the connection. If Chrome debug mode is already running, it skips and reuses it.
If mcp__chrome-devtools__* tools are not available, guide the user to install the MCP server:
claude mcp add --scope user chrome-devtools -- npx chrome-devtools-mcp@latest --autoConnect
The user needs to restart Claude Code after installation for the MCP tools to become available.
| Error | Fix |
|---|---|
| "Could not connect to Chrome" | Run setup command |
| "Could not find DevToolsActivePort" | Quit Chrome first, then run setup command |
| Port 9222 already in use | Another debug Chrome is running; use it or kill it first |