How do I install the Chrome Cdp skill?

Run npx skillmds@latest add dreamlab-ai/chrome-cdp in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Chrome Cdp safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Chrome Cdp?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Chrome Cdp free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Chrome Cdp?

dreamlab-ai (@dreamlab-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Chrome Cdp by dreamlab-ai — Agent Skill

Name: Chrome Cdp
Author: dreamlab-ai

Chrome Cdp

Raw Chrome DevTools Protocol scripting against a live Chrome session — direct WebSocket, no Puppeteer. Use when you need low-level CDP access: WebGPU/WebGL GPU testing, console/JS evaluation, screenshots, or performance traces on the browsercontainer GPU sidecar. For higher-level browser automation prefer the `browser` skill (chrome-devtools-mcp), which owns the canonical sidecar setup.

dreamlab-ai b2e01da 5 files · 44.5 KB Updated Sep 17, 2026

File contents

Chrome CDP Skill

Lightweight Chrome DevTools Protocol CLI. Connects directly via WebSocket to live Chrome sessions — no Puppeteer, instant connection to existing tabs. Reach for this over the browser/playwright skills only when you need raw CDP domain calls or the cdp.mjs command surface; for ordinary automation those MCP-backed skills are simpler.

Two Chrome Targets

Target	Address (from agentbox)	Address (from host)	Use Case
browsercontainer sidecar	`browsercontainer:9223`	`localhost:9222`	All browser automation — WebGPU/WebGL, screenshots, DOM

No local browser is installed in agentbox. All CDP goes through the sidecar.

WebGPU note: about:blank and data: URIs do not support WebGPU. Navigate to a real HTTP URL first (localhost/127.0.0.1 are secure by default; other HTTP origins need TREAT_AS_SECURE in docker-compose.browsercontainer.yml).

Quick Start — Sidecar (Recommended)

# Ensure sidecar is running
agentbox.sh browsercontainer up
agentbox.sh browsercontainer health

# List tabs in sidecar Chrome
scripts/cdp-sidecar.sh list

# Open your WebGPU app
scripts/cdp-sidecar.sh open http://the model host:3001

# Screenshot / accessibility snapshot
scripts/cdp-sidecar.sh shot <target>
scripts/cdp-sidecar.sh snap <target>

# Evaluate JS (check WebGPU availability)
scripts/cdp-sidecar.sh eval <target> "navigator.gpu ? 'WebGPU available' : 'No WebGPU'"

# Check GPU renderer
scripts/cdp-sidecar.sh eval <target> \
  "document.createElement('canvas').getContext('webgl2')?.getParameter(0x1F01)"

<target> is a unique prefix of the targetId from list (min 8 chars).

Quick Start — Local / Remote

# Local Chrome
DISPLAY=:1 chromium --remote-debugging-port=9222 --no-sandbox &
scripts/cdp-connect.sh 9222 list

# Any remote host (or via env vars). Canonical GPU target is the sidecar:
# browsercontainer:9223 (raw CDP via socat) — see the browser skill.
scripts/cdp-connect.sh remote-host.example:9222 list
export BROWSER_CDP_HOST=browsercontainer BROWSER_CDP_PORT=9223
scripts/cdp-connect.sh list

Where the detail lives

The full catalogs and workflows are in references/reference.md:

MCP SSE bridge (chrome-devtools-mcp, .mcp.json registration) + the 40+ tool categories table
Full cdp.mjs command table (html, nav, net, click, clickxy, type, loadall, evalraw, stop, …)
End-to-end WebGPU/WebGL testing workflow + full diagnostic
VNC monitoring, coordinates/DPR notes, architecture + network topology diagrams
Environment variables and troubleshooting commands

Related Skills

browser — canonical sidecar path (chrome-devtools-mcp SSE). Owns the shared sidecar setup block; start here for ordinary browser automation.
browser-automation — meta skill routing to the right browser tool.
playwright — browser automation via the same sidecar (chrome-devtools-mcp SSE).
host-webserver-debug — HTTPS bridge for Docker-to-host servers.

---name: chrome-cdpdescription: Raw Chrome DevTools Protocol scripting against a live Chrome session — direct WebSocket, no Puppeteer. Use when you need low-level CDP access: WebGPU/WebGL GPU testing, console/JS evaluation, screenshots, or performance traces on the browsercontainer GPU sidecar. For higher-level browser automation prefer the `browser` skill (chrome-devtools-mcp), which owns the canonical sidecar setup.---# Chrome CDP SkillLightweight Chrome DevTools Protocol CLI. Connects directly via WebSocket to liveChrome sessions — no Puppeteer, instant connection to existing tabs. Reach for thisover the `browser`/`playwright` skills only when you need raw CDP domain calls or the`cdp.mjs` command surface; for ordinary automation those MCP-backed skills are simpler.## Two Chrome Targets| Target | Address (from agentbox) | Address (from host) | Use Case ||--------|------------------------|---------------------|----------|| **browsercontainer sidecar** | `browsercontainer:9223` | `localhost:9222` | All browser automation — WebGPU/WebGL, screenshots, DOM |No local browser is installed in agentbox. All CDP goes through the sidecar.**WebGPU note:** `about:blank` and `data:` URIs do not support WebGPU.Navigate to a real HTTP URL first (`localhost`/`127.0.0.1` are secure by default;other HTTP origins need `TREAT_AS_SECURE` in docker-compose.browsercontainer.yml).## Quick Start — Sidecar (Recommended)```bash# Ensure sidecar is runningagentbox.sh browsercontainer upagentbox.sh browsercontainer health# List tabs in sidecar Chromescripts/cdp-sidecar.sh list# Open your WebGPU appscripts/cdp-sidecar.sh open http://the model host:3001# Screenshot / accessibility snapshotscripts/cdp-sidecar.sh shot <target>scripts/cdp-sidecar.sh snap <target># Evaluate JS (check WebGPU availability)scripts/cdp-sidecar.sh eval <target> "navigator.gpu ? 'WebGPU available' : 'No WebGPU'"# Check GPU rendererscripts/cdp-sidecar.sh eval <target> \ "document.createElement('canvas').getContext('webgl2')?.getParameter(0x1F01)"````<target>` is a unique prefix of the targetId from `list` (min 8 chars).## Quick Start — Local / Remote```bash# Local ChromeDISPLAY=:1 chromium --remote-debugging-port=9222 --no-sandbox &scripts/cdp-connect.sh 9222 list# Any remote host (or via env vars). Canonical GPU target is the sidecar:# browsercontainer:9223 (raw CDP via socat) — see the browser skill.scripts/cdp-connect.sh remote-host.example:9222 listexport BROWSER_CDP_HOST=browsercontainer BROWSER_CDP_PORT=9223scripts/cdp-connect.sh list```## Where the detail livesThe full catalogs and workflows are in [`references/reference.md`](references/reference.md):- **MCP SSE bridge** (`chrome-devtools-mcp`, `.mcp.json` registration) + the 40+ tool categories table- **Full `cdp.mjs` command table** (`html`, `nav`, `net`, `click`, `clickxy`, `type`, `loadall`, `evalraw`, `stop`, …)- **End-to-end WebGPU/WebGL testing workflow** + full diagnostic- **VNC monitoring**, coordinates/DPR notes, architecture + network topology diagrams- **Environment variables** and **troubleshooting** commands## Related Skills- **browser** — canonical sidecar path (chrome-devtools-mcp SSE). Owns the shared sidecar setup block; start here for ordinary browser automation.- **browser-automation** — meta skill routing to the right browser tool.- **playwright** — browser automation via the same sidecar (chrome-devtools-mcp SSE).- **host-webserver-debug** — HTTPS bridge for Docker-to-host servers.

Frequently asked questions