plugins/web/skills/cdp-connect/SKILL.md
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.
npx skillsauth add adobe/skills cdp-connectInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Connect to an existing Chrome browser via Chrome DevTools Protocol. Zero dependencies — Node 22 built-in WebSocket only.
Chrome must be running with remote debugging enabled:
# Launched manually:
chrome --remote-debugging-port=9222
# Or by a dev server that launches Chrome:
npm run dev # if it opens Chrome with --remote-debugging-port
if [[ -n "${CLAUDE_SKILL_DIR:-}" ]]; then
CDP_JS="${CLAUDE_SKILL_DIR}/scripts/cdp.js"
else
CDP_JS="$(command -v cdp.js 2>/dev/null || \
find ~/.claude -path "*/cdp-connect/scripts/cdp.js" -type f 2>/dev/null | head -1)"
fi
if [[ -z "$CDP_JS" || ! -f "$CDP_JS" ]]; then
echo "Error: cdp.js not found. Ask the user for the path." >&2
fi
Store in CDP_JS and use for all commands below.
node "$CDP_JS" list # Show all tabs with IDs
node "$CDP_JS" navigate <url> [--id <tid>] # Navigate to URL
node "$CDP_JS" eval <expr> [--id <tid>] # Evaluate JavaScript
node "$CDP_JS" screenshot <path> [--id <tid>] # Save screenshot as PNG
node "$CDP_JS" ax-tree [--id <tid>] # Accessibility tree (primary)
node "$CDP_JS" dom [--id <tid>] # Full HTML (fallback)
node "$CDP_JS" click <selector> [--id <tid>] # Click element
node "$CDP_JS" type <sel> <text> [--id <tid>] # Type into element
node "$CDP_JS" console [--timeout 10] # Stream console events
node "$CDP_JS" network [--timeout 10] # Stream network events
All commands default to port 9222. Override with --port N.
Use --id <target-id> from list output to target a specific tab.
list to see tabs and their unique IDsax-tree for page structure (prefer over dom)navigate, click, type, eval as neededscreenshot /tmp/shot.png, then Read the PNGconsole or network to stream eventsax-tree is the primary way to understand page state — semantic
roles and names are more useful than raw HTML for an agent/tmp/ and use the Read tool to vieweval supports promises: eval "await fetch('/api').then(r=>r.json())"--timeout 15CDP_TIMEOUT=10000 env var overrides default 5s timeout globallylist first and use --idtools
Use the run-workflow MCP to discover, compose, execute, publish, and save Adobe Firefly workflows. TRIGGER when: user asks what actions are available, what the MCP can do, how to process images/video/3D via workflow, wants to build/run/save/publish a workflow, OR pastes any workflow/batch/execution ID. BARE ID (UUID/workflowId/batchId) = INSPECT ONLY — call inspect_run, NEVER run_workflow_submit. ALWAYS call list_actions first for capability/discovery questions. DO NOT TRIGGER for direct Firefly API calls without MCP (use firefly-api-specs).
tools
Run predefined featured workflows via run-workflow MCP. TRIGGER when user names a featured workflow (retargeting, banners at scale, localization, packaging, banner advertising, etc.) or asks to run a known marketing/production workflow. Requires run-workflow MCP. ALWAYS call get_featured_workflow before compose_workflow. DO NOT TRIGGER for custom one-off workflows with no named template — use run-workflow skill.
tools
Migrate an Adobe Commerce App Builder project from the Integration Starter Kit or Checkout Starter Kit to the new App Management approach. Run from the root of the App Builder project to be migrated. Pass --auto to skip confirmation prompts (suitable for CI or batch use) — auto mode prints a summary of all Q&A questions answered with their defaults. Pass --doc-scan-only to scan README.md and env.dist for outdated content without modifying any files. Use when the user wants to migrate an App Builder project from the Integration Starter Kit or Checkout Starter Kit to the App Management approach, or mentions upgrading their Adobe Commerce extension architecture.
development
Add or modify webhook interceptors in an Adobe Commerce app. Use when the user wants to intercept Commerce operations to validate input, append data, or modify behavior — before or after execution. Requires a base app initialized with commerce-app-init.