ワンクリックでManusで任意のスキルを実行

$pwd:

chrome-mcp-bootstrap

Name: Chrome Mcp Bootstrap
Author: different-ai

// 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"

Manusで実行

$ git log --oneline --stat

stars:51

forks:8

updated:2026年3月13日 21:53

SKILL.md

readonly

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"

Quick Usage

Use this skill before any Chrome-driven verification when the browser connection is flaky or missing.

1) Check which browser path is available

Try the browser plugin path first if the current session exposes it.
If the plugin path is unavailable, use Chrome DevTools MCP directly.

2) Repair common local issues

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

3) Minimal readiness check

Browser plugin path: confirm browser_status or browser_get_tabs succeeds.
Direct Chrome DevTools MCP path: confirm initialize and tools/list succeed, then open a page.

4) If recovery fails

Document the exact blocker.
Fall back to HTTP-level verification plus screenshots.
Do not silently skip the UI verification requirement.

Common Gotchas

The browser extension may be loaded but its native broker may still need a full Chrome restart.
A stale chrome-devtools-mcp process or profile can block new sessions.
Remote-debugging URLs like http://127.0.0.1:9222 only work if Chrome was started with remote debugging enabled.
In headless mode, prefer screenshots and page text assertions over visual-only checks.

related-skills.json

同じリポジトリ

using-openwork-with-chrome-mcp.md

from "different-ai/the-factory"

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"

2026-05-0651

make-pr.md

from "different-ai/the-factory"

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"

2026-05-0551

den-test-instructions.md

from "different-ai/the-factory"

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"

2026-05-0551

changelog-release-tracker.md

from "different-ai/the-factory"

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"

2026-04-0551

cupid-app-architecture.md

from "different-ai/the-factory"

CUPID app architecture guidance for apps/app/src/app/**

2026-03-2951

vercel-env-vars.md

from "different-ai/the-factory"

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"

2026-03-2351

package.json

"author": "different-ai"

"repository": "different-ai/the-factory"

GitHub リポジトリを開く Creator のリポジトリを見る

$ install --global

$ download --local

Manusで実行

$ useful --forSOC

コンピュータユーザーサポートスペシャリストコンピュータ・数学職15-1232L4

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"

Quick Usage

Use this skill before any Chrome-driven verification when the browser connection is flaky or missing.

1) Check which browser path is available

Try the browser plugin path first if the current session exposes it.
If the plugin path is unavailable, use Chrome DevTools MCP directly.

2) Repair common local issues

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

3) Minimal readiness check

Browser plugin path: confirm browser_status or browser_get_tabs succeeds.
Direct Chrome DevTools MCP path: confirm initialize and tools/list succeed, then open a page.

4) If recovery fails

Document the exact blocker.
Fall back to HTTP-level verification plus screenshots.
Do not silently skip the UI verification requirement.

Common Gotchas

The browser extension may be loaded but its native broker may still need a full Chrome restart.
A stale chrome-devtools-mcp process or profile can block new sessions.
Remote-debugging URLs like http://127.0.0.1:9222 only work if Chrome was started with remote debugging enabled.
In headless mode, prefer screenshots and page text assertions over visual-only checks.

chrome-mcp-bootstrap

Quick Usage

1) Check which browser path is available

2) Repair common local issues

3) Minimal readiness check

4) If recovery fails

Common Gotchas

このリポジトリの他の Skills

このリポジトリの他の Skills

Quick Usage

1) Check which browser path is available

2) Repair common local issues

3) Minimal readiness check

4) If recovery fails

Common Gotchas