What problem does it solve? Connecting an AI agent to the Chrome browser the user already has open fails in confusing ways: port 9222 probes return 404 even when everything works, list_pages hangs silently while an authorization dialog waits for a click, and a wrong MCP server prefix silently connects to an isolated blank instance instead of the real browser. This Skill encodes the diagnostic discipline and scripts to avoid those misreadings. ## Core Features & Use Cases - Connection diagnosis discipline: Establishes list_pages as the sole connectivity verdict, forbidding curl probes of port 9222 and process-flag inspection that produce false negatives under --autoConnect mode. - Authorization dialog automation: Ships a UIA-based PowerShell script that auto-clicks Chrome 144+ remote debugging approval dialogs, plus a tab-enumeration script for independent cross-validation before reporting tab counts to the user. - Profile-aware launching: Starts Chrome with a validated --profile-directory (handling spaces and quoting traps) so the agent can operate specific signed-in profiles. - Use Case: The user asks "how many tabs do I have open in Chrome?" The agent calls list_pages, runs the UIA tab counter as a second evidence path, confirms both agree, and only then reports the number. ## Quick Start Ask the agent to connect to your real Chrome browser and list your currently open tabs.
