chrome-cdp-access
Installation
SKILL.md
Chrome CDP Access — read/drive the user's live Chrome
When to Use
- User asks "can you see what I have open in my browser?" or wants you to read/drive THEIR tab (Slack, dashboards, logged-in apps — anything needing their session).
- You need page state, DOM, or console from a tab the user is actually viewing.
- NOT for general web automation — that goes to the headless browser tools.
User preference (11-ago-2026): when the user asks "can you see my browser tab?", do NOT default to computer_use screen-driving — the user explicitly doubts that path ("no creo que el camino adecuado sea usar computer use"). Prefer CDP/AppleScript direct access: more reliable, no window-visibility issues (cua-driver may not even see the Chrome window).
Decision tree
- Read-only quick check (always works, zero setup): AppleScript → URL + title of active tab.
- Full control (DOM, navigation, JS): CDP on a SECOND Chrome instance with explicit
--user-data-dir.