catalan-adobe/cdp-connect
Connect Claude Code to an existing Chrome browser via CDP (Chrome DevTools Protocol). Zero dependencies — uses Node 22 built-in WebSocket. Attach to any Chrome running with --remote-debugging-port, then navigate, click, type, screenshot, evaluate JS, read accessibility tree, and monitor console/network. Use when you need to interact with a browser the agent already started, control an existing Chrome instance, or drive browser automation without Playwright MCP. Triggers on: cdp connect, connect to browser, connect to chrome, attach to browser, interact with browser, drive browser, browser automation, control chrome, connect 9222.
99
99%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that covers all dimensions thoroughly. It provides specific concrete actions, comprehensive trigger terms, explicit 'Use when' guidance with differentiation from similar tools (Playwright MCP), and a clear technical niche (CDP protocol). The description is well-structured, uses third person voice correctly, and balances technical detail with natural language triggers.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'navigate, click, type, screenshot, evaluate JS, read accessibility tree, and monitor console/network.' Also specifies technical details like 'Node 22 built-in WebSocket' and '--remote-debugging-port'. | 3 / 3 |
Completeness | Clearly answers both 'what' (connect to Chrome via CDP, navigate, click, type, screenshot, etc.) and 'when' (explicit 'Use when...' clause with specific scenarios plus a 'Triggers on:' list of keywords). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'cdp connect', 'connect to browser', 'connect to chrome', 'attach to browser', 'browser automation', 'control chrome', 'connect 9222'. These cover many natural phrasings a user might use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — specifically targets CDP/Chrome DevTools Protocol connection to an existing browser, and explicitly differentiates itself from Playwright MCP ('drive browser automation without Playwright MCP'). The mention of port 9222 and CDP makes it clearly distinguishable from general browser automation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that is concise, actionable, and well-structured. It provides complete executable commands, a clear multi-step workflow with verification, and practical tips without over-explaining concepts Claude already knows. The security warning about external content is a thoughtful addition.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place. No unnecessary explanations of what CDP is or how WebSockets work. The prerequisites, commands, and workflow are all lean and assume Claude's competence. | 3 / 3 |
Actionability | Provides fully executable bash commands for every operation, a concrete script for locating the cdp.js file, and specific command-line examples with flags. Copy-paste ready throughout. | 3 / 3 |
Workflow Clarity | The 5-step workflow (Discover → Understand → Interact → Verify → Debug) is clearly sequenced with explicit verification via screenshot + Read tool. The script section includes error handling when cdp.js is not found. | 3 / 3 |
Progressive Disclosure | Well-organized into logical sections (Prerequisites, Script, Commands, Workflow, Tips) that are appropriately sized. The skill references an external script file (cdp.js) without deeply nesting documentation. For a skill of this size, the structure is clean and navigable. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents