How do I install the Chrome Cdp skill?

Run npx skillmds@latest add tomevault-io/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?

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

Chrome Cdp by tomevault-io — Agent Skill

Name: Chrome Cdp
Author: tomevault-io

File contents

Chrome CDP

Lightweight Chrome DevTools Protocol CLI. Connects directly via WebSocket — no Puppeteer, works with 100+ tabs, instant connection.

Prerequisites

Chrome (or Chromium, Brave, Edge, Vivaldi) with remote debugging enabled: open chrome://inspect/#remote-debugging and toggle the switch
Node.js 22+ (uses built-in WebSocket)
If your browser's DevToolsActivePort is in a non-standard location, set CDP_PORT_FILE to its full path

Commands

All commands use scripts/cdp.mjs. The <target> is a unique targetId prefix from list; copy the full prefix shown in the list output (for example 6BE827FA). The CLI rejects ambiguous prefixes.

List open pages

scripts/cdp.mjs list

Take a screenshot

scripts/cdp.mjs shot <target> [file]    # default: screenshot-<target>.png in runtime dir

Captures the viewport only. Scroll first with eval if you need content below the fold. Output includes the page's DPR and coordinate conversion hint (see Coordinates below).

Accessibility tree snapshot

scripts/cdp.mjs snap <target>

Evaluate JavaScript

scripts/cdp.mjs eval <target> <expr>

Watch out: avoid index-based selection (querySelectorAll(...)[i]) across multiple eval calls when the DOM can change between them (e.g. after clicking Ignore, card indices shift). Collect all data in one eval or use stable selectors.

Other commands

scripts/cdp.mjs html    <target> [selector]   # full page or element HTML
scripts/cdp.mjs nav     <target> <url>         # navigate and wait for load
scripts/cdp.mjs net     <target>               # resource timing entries
scripts/cdp.mjs click   <target> <selector>    # click element by CSS selector
scripts/cdp.mjs clickxy <target> <x> <y>       # click at CSS pixel coords
scripts/cdp.mjs type    <target> <text>         # Input.insertText at current focus; works in cross-origin iframes unlike eval
scripts/cdp.mjs loadall <target> <selector> [ms]  # click "load more" until gone (default 1500ms between clicks)
scripts/cdp.mjs evalraw <target> <method> [json]  # raw CDP command passthrough
scripts/cdp.mjs open    [url]                  # open new tab (each triggers Allow prompt)
scripts/cdp.mjs stop    [target]               # stop daemon(s)

Coordinates

shot saves an image at native resolution: image pixels = CSS pixels × DPR. CDP Input events (clickxy etc.) take CSS pixels.

CSS px = screenshot image px / DPR

shot prints the DPR for the current page. Typical Retina (DPR=2): divide screenshot coords by 2.

Tips

Prefer snap --compact over html for page structure.
Use type (not eval) to enter text in cross-origin iframes — click/clickxy to focus first, then type.
Chrome shows an "Allow debugging" modal once per tab on first access. A background daemon keeps the session alive so subsequent commands need no further approval. Daemons auto-exit after 20 minutes of inactivity.

Source: pasky/chrome-cdp-skill — distributed by TomeVault.

---name: chrome-cdpdescription: Interact with local Chrome browser session (only on explicit user approval after being asked to inspect, debug, or interact with a page open in Chrome) Use when this capability is needed.---# Chrome CDPLightweight Chrome DevTools Protocol CLI. Connects directly via WebSocket — no Puppeteer, works with 100+ tabs, instant connection.## Prerequisites- Chrome (or Chromium, Brave, Edge, Vivaldi) with remote debugging enabled: open `chrome://inspect/#remote-debugging` and toggle the switch- Node.js 22+ (uses built-in WebSocket)- If your browser's `DevToolsActivePort` is in a non-standard location, set `CDP_PORT_FILE` to its full path## CommandsAll commands use `scripts/cdp.mjs`. The `<target>` is a **unique** targetId prefix from `list`; copy the full prefix shown in the `list` output (for example `6BE827FA`). The CLI rejects ambiguous prefixes.### List open pages```bashscripts/cdp.mjs list```### Take a screenshot```bashscripts/cdp.mjs shot <target> [file] # default: screenshot-<target>.png in runtime dir```Captures the **viewport only**. Scroll first with `eval` if you need content below the fold. Output includes the page's DPR and coordinate conversion hint (see **Coordinates** below).### Accessibility tree snapshot```bashscripts/cdp.mjs snap <target>```### Evaluate JavaScript```bashscripts/cdp.mjs eval <target> <expr>```> **Watch out:** avoid index-based selection (`querySelectorAll(...)[i]`) across multiple `eval` calls when the DOM can change between them (e.g. after clicking Ignore, card indices shift). Collect all data in one `eval` or use stable selectors.### Other commands```bashscripts/cdp.mjs html <target> [selector] # full page or element HTMLscripts/cdp.mjs nav <target> <url> # navigate and wait for loadscripts/cdp.mjs net <target> # resource timing entriesscripts/cdp.mjs click <target> <selector> # click element by CSS selectorscripts/cdp.mjs clickxy <target> <x> <y> # click at CSS pixel coordsscripts/cdp.mjs type <target> <text> # Input.insertText at current focus; works in cross-origin iframes unlike evalscripts/cdp.mjs loadall <target> <selector> [ms] # click "load more" until gone (default 1500ms between clicks)scripts/cdp.mjs evalraw <target> <method> [json] # raw CDP command passthroughscripts/cdp.mjs open [url] # open new tab (each triggers Allow prompt)scripts/cdp.mjs stop [target] # stop daemon(s)```## Coordinates`shot` saves an image at native resolution: image pixels = CSS pixels × DPR. CDP Input events (`clickxy` etc.) take **CSS pixels**.```CSS px = screenshot image px / DPR````shot` prints the DPR for the current page. Typical Retina (DPR=2): divide screenshot coords by 2.## Tips- Prefer `snap --compact` over `html` for page structure.- Use `type` (not eval) to enter text in cross-origin iframes — `click`/`clickxy` to focus first, then `type`.- Chrome shows an "Allow debugging" modal once per tab on first access. A background daemon keeps the session alive so subsequent commands need no further approval. Daemons auto-exit after 20 minutes of inactivity.---> Source: [pasky/chrome-cdp-skill](https://github.com/pasky/chrome-cdp-skill) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Chrome Cdp