メニュー
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 に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/chenwei791129/agent-skills --skill chrome-devtoolsコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
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.
| 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 |