chrome-cdp-live-browser

aradotso/trending-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/aradotso/trending-skills --skill chrome-cdp-live-browser
0 commentsdiscussion
summary

Skill by ara.so — Daily 2026 Skills collection.

skill.md

chrome-cdp: Live Chrome Session for AI Agents

Skill by ara.so — Daily 2026 Skills collection.

chrome-cdp connects your AI agent directly to your running Chrome browser via the Chrome DevTools Protocol (CDP). Unlike browser automation tools that spin up fresh isolated browsers, this connects to tabs you already have open — with your logins, cookies, and current page state intact.

What It Does

  • Live session access — reads and interacts with tabs you're already logged into
  • Persistent daemon — one WebSocket daemon per tab; the "Allow debugging" modal appears once, not on every command
  • No npm install — only Node.js 22+ required
  • 100+ tab support — handles large numbers of open tabs reliably
  • Cross-origin iframe supporttype command works even inside cross-origin iframes

Installation

As a pi skill

pi install git:github.com/pasky/[email protected]

Manual (for Amp, Claude Code, Cursor, Codex, etc.)

git clone https://github.com/pasky/chrome-cdp-skill
# Copy the skills/chrome-cdp/ directory to wherever your agent loads context from

Enable Remote Debugging in Chrome

  1. Open Chrome and navigate to: chrome://inspect/#remote-debugging
  2. Toggle the "Enable remote debugging" switch

That's all. No flags, no relaunching Chrome.

The script auto-detects Chrome, Chromium, Brave, Edge, and Vivaldi on macOS, Linux, and Windows. For non-standard installs:

export CDP_PORT_FILE=/path/to/DevToolsActivePort

Key Commands

All commands use scripts/cdp.mjs as the entry point. <target> is a unique prefix of the targetId shown by list.

List Open Tabs

node scripts/cdp.mjs list
# Output:
# A1B2C3  https://github.com/pasky/chrome-cdp-skill  chrome-cdp-skill
# D4E5F6  https://mail.google.com/mail/u/0/           Gmail

Screenshot a Tab

node scripts/cdp.mjs shot A1B2
# Saves screenshot to runtime dir, prints the file path

Accessibility Tree (Semantic Snapshot)

node scripts/cdp.mjs snap A1B2
# Returns compact, semantic accessibility tree — best for understanding page structure

Full HTML or Scoped HTML

node scripts/cdp.mjs html A1B2                    # full page HTML
node scripts/cdp.mjs html A1B2 ".main-content"    # scoped to CSS selector
node scripts/cdp.mjs html A1B2 "#article-body"    # scoped to ID

Evaluate JavaScript

node scripts/cdp.mjs eval A1B2 "document.title"
node scripts/cdp.mjs eval A1B2 "window.location.href"
node scripts/cdp.mjs eval A1B2 "document.querySelectorAll('a').length"

Navigate to URL

node scripts/cdp.mjs nav A1B2 https://example.com
# Navigates and waits for page load

Network Resource Timing

node scripts/cdp.mjs net A1B2
# Shows network resource timing for the current page

Click an Element

node scripts/cdp.mjs click A1B2 "button.submit"
node scripts/cdp.mjs click A1B2 "#login-btn"
node scripts/cdp.mjs click A1B2 "[data-testid='confirm']"

Click at Coordinates

node scripts/cdp.mjs clickxy A1B2 320 480
# Clicks at CSS pixel coordinates (x=320, y=480)

Type Text

node scripts/cdp.mjs type A1B2 "Hello, world!"
# Types at the currently focused element — works in cross-origin iframes

Load More (Click Until Gone)

node scripts/cdp.mjs loadall A1B2 "button.load-more"
# Keeps clicking the selector until it disappears from the DOM

Open a New Tab

node scripts/cdp.mjs open
node scripts/cdp.mjs open https://example.com
# Note: triggers Chrome's "Allow" prompt

Stop Daemons

node scripts/cdp.mjs stop          # stop all daemons
node scripts/cdp.mjs stop A1B2     # stop daemon for specific tab

Raw CDP Command Passthrough

node scripts/cdp.mjs evalraw A1B2 "Page.getFrameTree"
node scripts/cdp.mjs evalraw A1B2 "Runtime.evaluate" '{"expression":"1+1"}'

Common Patterns

Pattern: Read a Page You're Logged Into

# List tabs to find your target
node scripts/cdp.mjs list

# Grab the accessibility tree for a semantic view
node scripts/cdp.mjs snap D4E5

# Or get scoped HTML for a specific section
node scripts/cdp.mjs html D4E5 ".email-list"

Pattern: Fill and Submit a Form

# Click the input field
node scripts/cdp.mjs click A1B2 "input[name='search']"

# Type into it
node scripts/cdp.mjs type A1B2 "my search query"

# Click submit
node scripts/cdp.mjs click A1B2 "button[type='submit']"

# Take a screenshot to verify result
node scripts/cdp.mjs shot A1B2

Pattern: Extract Data with JavaScript

# Get all link hrefs on a page
node scripts/cdp.mjs eval A1B2 "Array.from(document.querySelectorAll('a')).map(a => a.href)"

# Get text content of a specific element
node scripts/cdp.mjs eval A1B2 "document.querySelector('.price').textContent.trim()"

# Get table data as JSON
node scripts/cdp.mjs eval A1B2 "
  Array.from(document.querySelectorAll('table tr')).map(row =>
    Array.from(row.querySelectorAll('td,th')).map(cell => cell.textContent.trim())
  )
"

Pattern: Navigate and Wait

# Navigate and then immediately read the page
node scripts/cdp.mjs nav A1B2 https://news.ycombinator.com
node scripts/cdp.mjs snap A1B2

Pattern: Paginated Content

# Keep loading content until "Load More" button disappears
node scripts/cdp.mjs loadall A1B2 "button[data-action='load-more']"

# Then extract all loaded content
node scripts/cdp.mjs eval A1B2 "document.querySelectorAll('.item').length"

Pattern: Script Integration (Node.js)

import { execFile } from 'node:child_process';
import { promisify } from 'node:util';

const exec = promisify(execFile);
const CDP = (...args) => exec('node', ['scripts/cdp.mjs', ...args]);

async function getPageTitle(tabPrefix) {
  const { stdout } = await CDP('eval', tabPrefix, 'document.title');
  return stdout.trim();
}

async function takeScreenshot(tabPrefix) {
  const { stdout } = await CDP('shot', tabPrefix);
  return stdout.trim(); // returns file path
}

async function navigateAndSnap(tabPrefix, url) {
  await CDP('nav', tabPrefix, url);
  const { stdout } = await CDP('snap', tabPrefix);
  return stdout;
}

// Usage
const tabs = (await CDP('list')).stdout;
console.log(tabs);

Configuration

Environment Variable Purpose
CDP_PORT_FILE Path to DevToolsActivePort file for non-standard browser installs

Daemons auto-exit after 20 minutes of inactivity — no manual cleanup needed in normal use.

Troubleshooting

"Allow debugging" modal keeps appearing

This happens if daemons aren't persisting. Make sure you're using the same scripts/cdp.mjs entry point — it manages daemon lifecycle automatically. If you switched tools mid-session, run stop and let daemons restart fresh.

Browser not detected

If auto-detection fails, find your DevToolsActivePort file and set the env var:

# macOS Chrome example
export CDP_PORT_FILE="$HOME/Library/Application Support/Google/Chrome/Default/DevToolsActivePort"

# Linux Chrome example
export CDP_PORT_FILE="$HOME/.config/google-chrome/Default/DevToolsActivePort"

Target not found / prefix ambiguous

Run list again — tab IDs change when tabs are closed/reopened. Use a longer prefix if multiple tabs share the same prefix characters.

Remote debugging toggle not visible

Ensure you're on chrome://inspect/#remote-debugging (not just chrome://inspect/). The toggle is in the top-right of the page.

Node.js version error

This project requires Node.js 22+. Check with node --version and upgrade if needed via nvm or your package manager.

Screenshots are blank or wrong size

The screenshot reflects the actual rendered viewport. If the tab is in a background window or the OS has display scaling, pixel coordinates for clickxy may need adjustment. Use snap or eval to inspect DOM state instead of relying solely on screenshots.

how to use chrome-cdp-live-browser

How to use chrome-cdp-live-browser on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add chrome-cdp-live-browser
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/aradotso/trending-skills --skill chrome-cdp-live-browser

The skills CLI fetches chrome-cdp-live-browser from GitHub repository aradotso/trending-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/chrome-cdp-live-browser

Reload or restart Cursor to activate chrome-cdp-live-browser. Access the skill through slash commands (e.g., /chrome-cdp-live-browser) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.842 reviews
  • Ganesh Mohane· Dec 28, 2024

    chrome-cdp-live-browser is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Luis Martin· Dec 20, 2024

    Keeps context tight: chrome-cdp-live-browser is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Hana Abebe· Dec 20, 2024

    Solid pick for teams standardizing on skills: chrome-cdp-live-browser is focused, and the summary matches what you get after install.

  • Carlos Agarwal· Dec 4, 2024

    I recommend chrome-cdp-live-browser for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Hiroshi Khan· Nov 23, 2024

    chrome-cdp-live-browser fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Sakshi Patil· Nov 19, 2024

    Keeps context tight: chrome-cdp-live-browser is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Kwame Reddy· Nov 11, 2024

    chrome-cdp-live-browser is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Noor Khan· Nov 3, 2024

    We added chrome-cdp-live-browser from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Hana Diallo· Oct 22, 2024

    Solid pick for teams standardizing on skills: chrome-cdp-live-browser is focused, and the summary matches what you get after install.

  • Dev Huang· Oct 14, 2024

    Registry listing for chrome-cdp-live-browser matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 42

1 / 5