04-core-use-chrome-devtools-mcp-for-browser-automationlisted

CORE - never delete. HARD MANDATE: trigger for ANY browser work - opening a page, clicking/filling/verifying UI, screenshots, mobile/responsive checks, network/console inspection, perf/Lighthouse, running an Apps Script function from the editor, or ANY online research/web search (search via Google only, skip stale AI-overview blocks, dork when it sharpens the query). The chrome-devtools MCP drives a real logged-in browser and is the mandatory Tier-4 visual/mobile gate plus the verify-interactive-elements step; reasoning from CSS/HTML is never a substitute. Also covers the Step-0 active-account identity gate, the on-demand auto-Allow clicker, credential-entry reality (account-switch first; no local Chrome password store), and the iframe-flattening decision tree. Lists the tools by job.
markkennethbadilla/public-agent-provisioning · ★ 0 · AI & Automation · score 72

Install: claude install-skill markkennethbadilla/public-agent-provisioning

# Use the chrome-devtools MCP for Browser Automation (CORE) **Why:** It drives a real browser, the only way to truly verify UI, mobile layout, and interactions (reasoning from CSS is not enough). It is mandatory for the Tier-4 boot-and-DRIVE gate and for verifying interactive elements before declaring anything done. **The browser is Chrome, and the MCP ATTACHES to it - it never launches its own.** The agent shares the user''s REAL logged-in session (all their Google/Slack/etc. accounts) so there is no "launch a browser first" step and no profile-lock fight. You just call the tools and the MCP connects to the already-running Chrome. Chrome is Chromium-based, so every tool drives it exactly like Chrome. ## The connection model - attach, never launch The `--remote-debugging-port` launch flag is **BANNED as a LAW** (see below). Attach uses one of two paths: 1. **SUPPORTED (target state): in-browser remote-debugging + `--autoConnect`.** Enable the remote-debugging server once, inside Chrome, at `chrome://inspect/#remote-debugging` (the Chromium equivalent of `chrome://inspect/#remote-debugging`; Chromium 144+ feature). Follow the dialog to allow incoming debugging connections. Then the MCP is wired with `--autoConnect`, which auto-connects to the running browser for the configured channel''s user-data-dir - no port on the launch command line. The first MCP tool call shows an in-browser "Allow" permission dialog; the auto-Allow watcher (below) clicks it. 2. **CURREN