From fd6554afb69319627bf746442ca2bd249c5dbafb Mon Sep 17 00:00:00 2001
From: Joan Leon <joan.leon@gmail.com>
Date: Tue, 9 Jun 2026 10:04:23 +0200
Subject: [PATCH] fix(browser-testing): correct chrome-devtools-mcp install
 config

Package name was wrong (@anthropic/chrome-devtools-mcp does not exist).
Adds -y to skip npx confirmation prompt and --autoConnect as the
recommended default to connect automatically to a running Chrome instance.
---
 skills/browser-testing-with-devtools/SKILL.md | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/skills/browser-testing-with-devtools/SKILL.md b/skills/browser-testing-with-devtools/SKILL.md
index 2af253b..0bef512 100644
--- a/skills/browser-testing-with-devtools/SKILL.md
+++ b/skills/browser-testing-with-devtools/SKILL.md
@@ -25,19 +25,21 @@ Use Chrome DevTools MCP to give your agent eyes into the browser. This bridges t
 
 ### Installation
 
-```bash
-# Add Chrome DevTools MCP server to your Claude Code config
-# In your project's .mcp.json or Claude Code settings:
+Add the following to your project's `.mcp.json` or Claude Code settings:
+
+```json
 {
   "mcpServers": {
     "chrome-devtools": {
       "command": "npx",
-      "args": ["@anthropic/chrome-devtools-mcp@latest"]
+      "args": ["-y", "chrome-devtools-mcp@latest", "--autoConnect"]
     }
   }
 }
 ```
 
+`-y` skips the npx install confirmation. `--autoConnect` connects automatically to a running Chrome instance (or launches one) — recommended for most users.
+
 ### Available Tools
 
 Chrome DevTools MCP provides these capabilities: