Chrome Dev MCP

Collect browser-internal evidence (snapshots, Console, Network, Performance, Lighthouse, heap) from one identity-checked Chrome through the shared chrome-dev-mcp-cli. Every agent on the machine reuses one daemon-backed MCP child, so the rules below exist to keep that shared session healthy and to keep your claims honest.

Everything a page task needs is in this file. Read a reference only when its trigger below applies; the uxc-facade skill is a packaging method and is not needed to run a task.

Get a proven connection

Run helpers with zsh from this skill's directory (under bash they abort with A: unbound variable).

Invocation	Command	On success
`/chrome-dev-mcp` with no task	`zsh scripts/uxc-readiness.zsh`	Reply only `CHROME_DEV_MCP_READY`
Any page task	`zsh scripts/uxc-readiness.zsh --private-result`	Keep the `list_pages` JSON private and use it to pick the numeric `pageId`

Both run one real shared list_pages and check the UXC envelope and the tool result (data.isError). A page task runs only the private mode, once; do not run the sanitized mode first.

If readiness prints STATUS=ERROR: