メニュー
Recover or verify Chrome MCP before UI-flow testing. Triggers when user mentions: - "chrome mcp is broken" - "chrome mcp bootstrap" - "browser broker missing" - "cannot connect to chrome mcp"
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Drive the OpenWork dev renderer with Chrome MCP and verify workspace UI flows. Triggers when user mentions: - "use Chrome MCP with OpenWork" - "hook up to pnpm dev renderer" - "add an OpenWork workspace through the UI"
Create a PR with structured evidence: build verification, UI screenshots uploaded to an ephemeral host, API test results, and a verification comment. No screenshots committed to the repo. Triggers when user mentions: - "create a pr" - "make a pr" - "open a pr" - "push and pr"
Boot up the Den dev stack and the OpenWork desktop app locally, then test common flows like sign-in, dashboard, and telemetry. Triggers when user mentions: - "test den" - "test the app locally" - "boot up den" - "den dev flow" - "test sign in"
Generate or update the internal OpenWork release changelog tracker as plain markdown release sections. Triggers when user mentions: - "generate changelog markdown" - "track this release" - "add a changelog entry"
CUPID app architecture guidance for apps/app/src/app/**
Manage Vercel environment variables for OpenWork projects from the CLI, including linking the local app directory first. Triggers when user mentions: - "add a vercel env var" - "set a vercel env var" - "vercel environment variable"
| name | chrome-mcp-bootstrap |
| description | Recover or verify Chrome MCP before UI-flow testing. Triggers when user mentions: - "chrome mcp is broken" - "chrome mcp bootstrap" - "browser broker missing" - "cannot connect to chrome mcp" |
Use this skill before any Chrome-driven verification when the browser connection is flaky or missing.
Run these in order:
pkill -f "chrome-devtools-mcp" || true
pkill -f "/Users/$USER/.cache/chrome-devtools-mcp/chrome-profile" || true
npx @different-ai/opencode-browser install
open -a "Google Chrome"
If the extension path is still broken, prefer direct Chrome DevTools MCP:
npx -y chrome-devtools-mcp@latest --help
browser_status or browser_get_tabs succeeds.initialize and tools/list succeed, then open a page.chrome-devtools-mcp process or profile can block new sessions.http://127.0.0.1:9222 only work if Chrome was started with remote debugging enabled.