Diagnose and fix Chrome MCP connection issues — run after switching macOS users when Chrome won't connect
Diagnose and fix Chrome MCP connection issues — run after switching macOS users when Chrome won't connect
npx skills add https://github.com/MSApps-Mobile/claude-plugins --skill fix-chrome-connection复制此命令并粘贴到 Claude Code 中以安装该技能
Ensures Claude's chat responses are properly formatted for RTL (right-to-left) text in Hebrew, Arabic, Persian (Farsi), Urdu, and other RTL languages — especially when mixing with English or other LTR text. Use this skill ALWAYS — it should be active on every single response when the user writes in any RTL language, mentions an RTL language, or when the conversation includes any RTL script. This skill handles bidirectional text formatting so responses look clean and readable instead of jumbled. Trigger on ANY RTL content in the conversation, even a single word in Hebrew, Arabic, Persian, or Urdu script.
Use Shopify Storefront MCP tools to search catalogs, inspect products, read and mutate carts, fetch policies, and describe shops across any MSApps / OpsAgents client store — multi-tenant, no shop hardcoded. Trigger on: "shopify", "storefront", "myshopify", "cart", "checkout", "products", "catalog", "collection", "shipping policy", "refund policy", "client store", "merchant", or any task that needs live data from a Shopify merchant. Also use when the user wants to prototype a conversational shopping flow, a recommendation agent, or a customer-support bot over a Shopify store.
Walk a merchant through installing the Symmetry theme — or any paid Theme Store theme — on any Shopify store, from Theme Store preview to live publish. Trigger on: "install Symmetry", "add Symmetry theme", "install a Shopify theme", "switch theme", "try a new theme", "publish a theme", "Shopify theme install", "theme store", or any request to change a Shopify storefront theme. Also trigger when the user links to themes.shopify.com/themes/symmetry or to any Shopify Theme Store listing.
Quickly checks whether the Claude in Chrome MCP connection is working and reports the status. Use when the user says "is chrome connected?", "check chrome", "chrome status", "test chrome connection", "is the chrome extension working?", or any variation of wanting to know if Chrome is reachable before starting browser-based work. Also use proactively before running Chrome automation tasks if there's any doubt the connection is live.
Diagnose + clean up the recurring chrome-devtools-mcp wedge — multiple stale `chrome-devtools-mcp@latest` parent processes colliding on the shared `~/.cache/chrome-devtools-mcp/chrome-profile` directory. Use when state-changing tools (new_page, navigate_page, select_page, take_snapshot) error with "The browser is already running for /Users/.../chrome-profile. Use --isolated to run multiple browser instances." while `list_pages` still works. Card
Use when: tabs_context_mcp fails, Chrome MCP is broken, user says "fix Chrome", "reconnect Chrome", "Chrome extension not responding", or after switching Claude Desktop accounts. Diagnoses and repairs broken Claude-in-Chrome MCP connections step by step, then commits any new learnings to GitHub.
| name | fix-chrome-connection |
| description | Diagnose and fix Chrome MCP connection issues — run after switching macOS users when Chrome won't connect |
This is an automated run of a scheduled task. The user is not present to answer questions. Make reasonable choices autonomously and note them in your output. For "write" actions, only take them if explicitly required by the task. When in doubt, produce a report of what you found.
You are fixing a broken Chrome MCP connection. Work through these steps in order, stopping as soon as the connection works.
Call tabs_context_mcp with createIfEmpty: false.
screencapture -x /tmp/chrome_check.png
sips -Z 1920 /tmp/chrome_check.png --out /tmp/chrome_check_small.png
Copy to workspace and Read it. Note what's visible (Chrome open? which app is in focus? any errors?).
open -a "Google Chrome"
sleep 3
Retry connection test. If connected → report success and stop.
Do NOT attempt to click UI elements on chrome://extensions — the Claude desktop app steals focus from Chrome, making coordinate-based clicking fail. Go straight to quit+relaunch:
osascript -e 'tell application "Google Chrome" to quit'
sleep 5
open -a "Google Chrome"
sleep 8
Retry connection test. If connected → report success and stop.
If all automated steps failed, report:
If the profile check doesn't help, suggest reinstalling the Claude in Chrome extension: open chrome://extensions → remove Claude in Chrome → reinstall from Chrome Web Store.
Report what you tried and what happened. Do not silently retry.