Chrome Dev MCP

Use the managed chrome-dev-mcp-cli facade for browser-internal evidence. It reuses one identity-checked MCP child instead of starting one child per agent session. Keep host-native registration only as an explicit compatibility and rollback path.

Require the locally configured safe wrapper, launcher, and pinned UXC 0.17.0 facade. Never silently fall back to a host-native server because doing so recreates the per-session runtime fan-out this skill is designed to avoid.

Keep the user contract simple

Let the user remember only /chrome-dev-mcp. Handle connection checks, recovery, profile gates, shared-session reuse, and explicit pageId routing internally. With no additional task, return only CHROME_DEV_MCP_READY after sanitized shared readiness. When the same invocation includes a page task, use the readiness-plus-task fast path below instead of discarding a list_pages result that the task immediately needs. On failure, report one failing layer and one required action.

Execute the slash entry

Treat /chrome-dev-mcp without a task as a readiness-only action. Treat the same invocation with a page task as readiness-plus-task.