←Leaderboard/Browser Automation/chrome-cdp-skill
Last commit on March 17, 2026·Created on March 13, 2026

pasky/chrome-cdp-skill

“Direct programmatic access to active Chrome sessions via the DevTools Protocol”
Combined rank
#148
across all skills
In Browser Automation
#5
category rank
Stars
3.3k
+0.2% in last 7d
Forks
202
0.0% in last 7d
Watchers
11
0.0% in last 7d
Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
TL;DR

This skill provides a lightweight interface for interacting with local browser sessions using the Chrome DevTools Protocol. It enables developers to inspect, debug, and manipulate open pages without the overhead of heavy automation frameworks.

By connecting directly via WebSocket, it allows for precise control over active tabs, including the ability to capture viewport screenshots, extract accessibility tree snapshots, and evaluate JavaScript expressions in real time.

WHO IT'S FOR
AI agent / automation builders
connecting AI agents to live browser sessions
QA / test automation engineers
debugging web pages via CDP CLI commands
Frontend / Web developers
programmatically interacting with open browser tabs
Accessibility specialists
capturing accessibility tree snapshots for audit
Repository contents

1 skill file

Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.

Use this skill

Follow the documented setup, then try a first task.

I’m using

Install as a pi skill from GitHub

Installs: chrome-cdp skill · pi

Before you start
  • Node.js 22+
  • Chrome, Chromium, Brave, Edge, or Vivaldi
  • Remote debugging enabled in the browser
  • If DevToolsActivePort is stored in a non-standard location, CDP_PORT_FILE set to its full path

Platform: macOS, Linux, or Windows

  1. Run this terminal command to install the chrome-cdp skill from the documented GitHub version.

    pi install git:github.com/pasky/chrome-cdp-skill@v1.0.1
  2. In the browser, navigate to chrome://inspect/#remote-debugging and toggle the remote-debugging switch.

README.md ↗ · Checked Oct 18, 2026skills/chrome-cdp/SKILL.md ↗ · Checked Oct 18, 2026

Give it something to do.

Suggested first task

Inspect an open browser page

Uses chrome-cdp

  • Explicit approval to inspect the local browser session
  • An open page in Chrome, Chromium, Brave, Edge, or Vivaldi
  • The target page selection after open pages are listed
  • Node.js 22+
  • Remote debugging enabled
  • CDP_PORT_FILE when DevToolsActivePort uses a non-standard location
Use the chrome-cdp skill to inspect my local browser session after asking for my explicit approval. First list the open pages, then ask me which target to inspect. Use the unique targetId prefix from the list output and return a compact accessibility-tree snapshot of that page without clicking, typing, or navigating. Chrome remote debugging is already enabled, Node.js 22+ is installed, and CDP_PORT_FILE is configured if needed.
skills/chrome-cdp/SKILL.md ↗ · Checked Oct 18, 2026