skills.rest
yuexps
yuexpsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

browser_cdp

Connect to Chrome browsers via CDP and scan debugging ports.

3|1|Updated Apr 21, 2026
Search Tags:#browser automation#multi-agent#cdp#chrome#port scanning#remote debugging
One-click install
npx skills add https://github.com/yuexps/QwenPaw-FNOS --skill browser-cdp-yuexps
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser_cdp
Source: https://github.com/yuexps/QwenPaw-FNOS/tree/main/app/server/src/qwenpaw/agents/skills/browser_cdp-en
Command: npx skills add https://github.com/yuexps/QwenPaw-FNOS --skill browser-cdp-yuexps

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Managing and connecting to existing Chrome browsers or scanning for available CDP ports to enable remote debugging and multi-agent sharing.

Core Features & Use Cases

  • Connect to existing Chrome: Attach to browsers already running with a CDP endpoint.
  • Scan local CDP ports: Detect available CDP ports on the local machine.
  • Specify fixed cdp_port: Launch browsers with a designated debugging port for shared access.
  • Share browser sessions across multiple agents or tools, enhancing collaborative automation.

Quick Start

Use the skill to connect to your local Chrome by specifying the cdp_url or scan for open ports on your machine.

Frequently Asked Questions about browser_cdp

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

FAQPage Schema
How do I connect to an existing Chrome browser using CDP for remote debugging?▼

To connect to an existing Chrome browser using CDP, you attach to the browser already running by specifying its CDP endpoint URL. This enables remote control and facilitates multi-agent sharing workflows.

How do I scan for available Chrome DevTools Protocol ports on my local machine?▼

You can scan local CDP ports to detect available debugging endpoints on your machine. This identifies open ports for remote debugging, allowing you to establish a working CDP connection for browser automation.

Can I specify a fixed remote debugging port to share browser sessions across multiple agents?▼

Yes, you can specify a fixed CDP port to launch Chrome with a designated debugging endpoint. This enables shared browser sessions across multiple agents or tools, enhancing collaborative automation workflows.

Do I need a working CDP connection to manage Chrome browser sessions in multi-agent workflows?▼

Yes, multi-agent browser sharing requires a working CDP connection or ports open for remote debugging. It applies to scenarios requiring explicit browser attachment and port management for collaborative automation.

What is the best way to enable cross-agent browser sharing for advanced automation?▼

The best way to enable cross-agent browser sharing is using explicit Chrome DevTools Protocol connections. This facilitates attaching to local or external Chrome browsers for remote control and session sharing in multi-agent workflows.

Related Skills

Explore More Software Engineering Skills→
GraffiohGraffioh

web-browser

Automate Chrome browser interactions via the Chrome DevTools Protocol.

Community
Advanced
sourcegraphsourcegraph
16

web-browser

Automate Chromium-based browser navigation, element interaction, and data extraction via CDP.

Official
Advanced
ai-ecoverseai-ecoverse
28

playwright-cli

Automate browser interactions via Playwright CLI with explicit tab targeting.

Official
Intermediate
roach88roach88
2

browser

Automate Chrome via Chrome DevTools Protocol without extensions or MCP tooling.

Community
Intermediate