chrome-cdp

Automate local Chrome sessions via the Chrome DevTools Protocol.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/Wanger-SJTU/claw_skills --skill chrome-cdp-wanger-sjtu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chrome-cdp
Source: https://github.com/Wanger-SJTU/claw_skills/tree/main/chrome-cdp
Command: npx skills add https://github.com/Wanger-SJTU/claw_skills --skill chrome-cdp-wanger-sjtu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Interact with a local Chrome session and automate debugging, inspection, and page interactions via the Chrome DevTools Protocol.

Core Features & Use Cases

  • List open pages, capture screenshots, inspect elements, evaluate JavaScript, navigate, monitor network timing, and run arbitrary CDP commands across per-tab daemons.
  • Use cases include automated testing, UI debugging, and data collection from live pages without full browser automation frameworks.

Quick Start

Launch Chrome with remote debugging enabled, run cdp list to view targets, then try commands like cdp shot <target> to capture a screenshot.

Frequently Asked Questions about chrome-cdp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Chrome browser debugging without external dependencies?

You can automate Chrome browser debugging by using the Chrome DevTools Protocol (CDP) directly via Node.js 22+ built-in modules, enabling remote debugging to inspect pages and run scripts without external dependencies.

Can I capture screenshots and evaluate JavaScript using the Chrome DevTools Protocol?

Yes, you can capture screenshots and evaluate JavaScript using the Chrome DevTools Protocol by running commands like the screenshot and script evaluation tools against specific targets in your local Chrome session.

How do I interact with open Chrome pages for automated UI testing?

Automated UI testing is achieved by listing open page targets through the Chrome DevTools Protocol and dispatching arbitrary CDP commands across per-tab daemons to navigate, inspect elements, and interact with the page.

Do I need to install external libraries to run CDP commands for web automation?

No, you do not need external libraries to run CDP commands for web automation. The implementation relies entirely on built-in Node.js 22+ modules to control Chrome and execute web automation scripts.

What is the best way to monitor network timing and inspect elements in a local Chrome session?

The best way to monitor network timing and inspect elements in a local Chrome session is to leverage the Chrome DevTools Protocol, which allows direct interaction with page targets for data collection and debugging.

Why does the Chrome CDP automation require remote debugging to be enabled?

Chrome CDP automation requires remote debugging to be enabled because the DevTools Protocol needs a dedicated debugging port exposed by the browser to allow programmatic connection and command execution.