What does the Browser Setup AI skill do?

Configure the browser tool for Clacky. Guides the user through Chrome or Edge setup, verifies the connection, and writes ~/.clacky/browser.yml. Supports macOS, Linux, and WSL (Windows Chrome/Edge via remote debugging). Trigger on: "browser setup", "setup browser", "配置浏览器", "browser config", "browser doctor". Subcommands: setup, doctor.

Why use Browser Setup on TypingMind?

Because you install it once and use it with any model. Browser Setup is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Browser Setup in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/clacky-ai/openclacky/tree/main/lib/clacky/default_skills/browser-setup. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Browser Setup?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Browser Setup?

As many as you like. As long as a model supports skills, you can use Browser Setup with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Browser Setup AI skill free?

Yes. It is published on GitHub by clacky-ai under the MIT license. You only pay your own AI provider for the tokens you use.

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Browser Setup by clacky-ai — AI Skill for Any LLM

Browser Setup Skill

Configure the browser tool for Clacky. Config is stored at ~/.clacky/browser.yml.

Region-Aware Download Links

Whenever you show the user a link to download or upgrade Chrome/Edge, pick the right one for their region instead of always using google.com.

Treat the user as in China when any of these is true:

The user is talking to you in Chinese
The system locale is Chinese (echo $LANG contains zh_CN / zh_)
A previous run of install_browser.sh reported Region: china (visible in its output)
curl -s --max-time 3 https://www.google.com -o /dev/null -w "%{http_code}" returns 000 while baidu.com works

Use these links accordingly:

Region	Chrome	Edge
China	https://www.google.cn/chrome/	https://www.microsoft.com/zh-cn/edge
Global	https://www.google.com/chrome/	https://www.microsoft.com/edge

When unsure, show both lines (label them "China:" and "Global:") so the user can pick.

Command Parsing

User says	Subcommand
`browser setup`, `配置浏览器`, `setup browser`	setup
`browser doctor`	doctor

If no subcommand is clear, default to setup.

`setup`

Core Strategy: Progressive validation with clear next steps at each failure point.

Step 1 — Ensure Node.js is installed

Check Node.js version:

bash
node --version 2>/dev/null

Parse the version. If Node.js is missing or version < 20:

Run the bundled installer to automatically install Node.js:

bash
bash ~/.clacky/scripts/install_browser.sh

If the script exits 0 → Node.js is now installed. Proceed to Step 2.

If the script exits non-zero or doesn't exist:

❌ Node.js 20+ is required for browser automation.

Please install Node.js from: https://nodejs.org

Let me know when done and I'll continue.

Wait for user confirmation, then retry this step once. If still failing, stop.

Step 2 — Ensure chrome-devtools-mcp is installed

Check if installed:

bash
chrome-devtools-mcp --version 2>/dev/null

If found and exits 0 → skip to Step 3.

If missing, run the bundled installer:

bash
bash ~/.clacky/scripts/install_browser.sh

If the script exits non-zero or doesn't exist:

❌ Failed to install chrome-devtools-mcp automatically.

Please run manually:
npm install -g chrome-devtools-mcp@latest
Let me know when done.

Wait for user confirmation, then verify installation:

bash
chrome-devtools-mcp --version 2>/dev/null

If still missing after user confirms, stop with error message.

Step 3 — Verify Chrome/Edge is running with remote debugging

CRITICAL: Do NOT attempt browser() calls yet. First check if the browser is reachable using the API:

bash
curl -s http://${CLACKY_SERVER_HOST}:${CLACKY_SERVER_PORT}/api/browser/status

This returns JSON with daemon_running and enabled status. Ignore the result for now — we just need to see if the Clacky server is running.

Now attempt a browser connection to detect Chrome:

bash
browser(action="status")

If this succeeds → Chrome is running and reachable. Proceed to Step 4.

If this fails → The error message will indicate the specific issue. Parse it carefully:

Case A: "Chrome/Edge is not running or remote debugging is not enabled"

This is the most common case. The system can't find Chrome's DevToolsActivePort file or the port is not reachable.

Action: Guide the user to enable remote debugging.

On macOS:

bash
open "chrome://inspect/#remote-debugging" 2>/dev/null || echo "Please open chrome://inspect/#remote-debugging manually"

Then tell the user:

I've tried to open the remote debugging page in Chrome.

Please follow these steps:

Make sure Chrome or Edge is open

Visit: chrome://inspect/#remote-debugging (or edge://inspect/#remote-debugging)

Click "Allow remote debugging for this browser instance"

You should see a brief connection message appear

Let me know when done ✅

On Linux (non-WSL):

Please follow these steps:

Make sure Chrome or Edge is open

Visit: chrome://inspect/#remote-debugging

Click "Allow remote debugging for this browser instance"

Let me know when done ✅

On WSL:

Please follow these steps:

Open Edge on Windows

Visit: edge://inspect/#remote-debugging

Click "Allow remote debugging for this browser instance"

Let me know when done ✅

After user confirms, retry the connection once:

bash
browser(action="status")

If still failing:

❌ Still unable to connect to Chrome.

Please make sure:

Chrome/Edge is running

You clicked "Allow remote debugging" in chrome://inspect/#remote-debugging

No firewall is blocking localhost connections

Run /browser-setup doctor to diagnose the issue in detail.

Fetch the online troubleshooting guide for additional help:


web_fetch(url="https://www.openclacky.com/docs/browser-troubleshooting")

Stop here and suggest running doctor.

Case B: Other errors (MCP handshake timeout, daemon crash, etc.)

For any other error message, show it to the user and suggest:

❌ Browser connection failed:

This may be a temporary issue. Please try:

Restart your browser

Run /browser-setup again

If the problem persists, run /browser-setup doctor for detailed diagnostics.

Step 4 — Get and verify browser version

Now that connection is established, get the version:

bash
browser(action="act", kind="evaluate", js="navigator.userAgentData?.brands?.find(b => b.brand === 'Google Chrome' || b.brand === 'Microsoft Edge')?.version || navigator.userAgent.match(/Chrome\/(\d+)/)?.[1] || 'unknown'")

Parse the version number:

version >= 146 → Excellent, proceed
version 144-145 → Show warning but proceed:

⚠️ Your browser version is v${VERSION}. Version 146+ is recommended for best compatibility. Continuing anyway...
version < 144 or "unknown" → Stop:

❌ Browser version v${VERSION} is too old. Please upgrade Chrome or Edge to v146+.

Use the download link from the Region-Aware Download Links section above (pick China or Global based on the user's region).

After upgrading, run /browser-setup again.

Step 5 — Save configuration via API

Call the API to save the configuration:

bash
curl -s -X POST http://${CLACKY_SERVER_HOST}:${CLACKY_SERVER_PORT}/api/browser/configure \
  -H "Content-Type: application/json" \
  -d "{\"chrome_version\":\"${VERSION}\"}"

If this fails (HTTP error or empty response), show a warning:

⚠️ Failed to save configuration via API. You may need to run /browser-setup again after restarting Clacky.

Step 6 — Done

✅ Browser setup complete!

Chrome/Edge v${VERSION} is connected and ready to use.

You can now use browser automation features. Try asking me to:

"Open google.com in the browser"

"Take a screenshot"

"Fill out a form on this page"

`doctor`

Core Strategy: Diagnose don't fix. Check each component and report status.

This is a diagnostic tool, not a repair tool. It will check each component and tell you what's wrong, but won't automatically fix things.

Diagnostic Steps

Run all checks before showing results. Then show a summary report.

1. Check Config File

bash
test -f ~/.clacky/browser.yml && cat ~/.clacky/browser.yml

Parse the result:

File missing → ❌ Not configured
File exists, enabled: false → ⏸️ Disabled
File exists, enabled: true → ✅ Enabled

2. Check Node.js

bash
node --version 2>/dev/null

Not found → ❌ Node.js not installed
Version < 20 → ❌ Node.js too old (need 20+)
Version >= 20 → ✅ Node.js OK

3. Check chrome-devtools-mcp

bash
chrome-devtools-mcp --version 2>/dev/null

Not found → ❌ Not installed
Found → ✅ Installed (version: ...)

4. Check Clacky Server

bash
curl -s -f http://${CLACKY_SERVER_HOST}:${CLACKY_SERVER_PORT}/api/browser/status

Failed → ❌ Server not responding
Success → Parse JSON and show daemon_running status

5. Check Chrome Connection

Only run this if steps 1-4 are OK.

bash
browser(action="status")

Success → ✅ Connected. Also get the tab count from the result.
Failed → ❌ Not connected. Parse the error message to determine cause.

6. Check Chrome Version

Only run this if step 5 succeeded.

bash
browser(action="act", kind="evaluate", js="navigator.userAgent.match(/Chrome\/(\d+)/)?.[1] || 'unknown'")

version >= 146 → ✅ Excellent
version 144-145 → ⚠️ Acceptable but upgrade recommended
version < 144 or unknown → ❌ Too old

Report Format

Show results in a clean table:


Browser Doctor — Diagnostic Report
═══════════════════════════════════════════════════════════════

Configuration
  [✅] Config file found (~/.clacky/browser.yml)
  [✅] Browser tool enabled

Dependencies
  [✅] Node.js v22.1.0
  [✅] chrome-devtools-mcp installed (v1.2.3)

Connection
  [✅] Clacky server running
  [✅] MCP daemon running
  [✅] Chrome connected (3 tabs open)
  [✅] Chrome v146

═══════════════════════════════════════════════════════════════
✅ All systems operational!

If there are any ❌ or ⚠️ items, show them first in a Problems Found section, followed by specific Recommended Actions:


Browser Doctor — Diagnostic Report
═══════════════════════════════════════════════════════════════

⚠️ Problems Found
  [❌] Chrome not connected
       Error: Chrome/Edge is not running or remote debugging is not enabled
  [❌] Chrome version v142 is too old

───────────────────────────────────────────────────────────────

Configuration
  [✅] Config file found
  [✅] Browser tool enabled

Dependencies
  [✅] Node.js v22.1.0
  [✅] chrome-devtools-mcp installed

Connection
  [✅] Clacky server running
  [❌] Chrome not connected

═══════════════════════════════════════════════════════════════

🔧 Recommended Actions

1. Enable remote debugging:
   - Open Chrome and visit: chrome://inspect/#remote-debugging
   - Click "Allow remote debugging for this browser instance"

2. Upgrade your browser:
   - Chrome v142 is too old (need v146+)
   - Pick the download link for the user's region from the
     **Region-Aware Download Links** section at the top of this skill
     (China users → google.cn; others → google.com).

After fixing these issues, run `/browser-setup` again to verify.

Common Diagnostic Scenarios

Scenario 1: Config not found


[❌] Config file not found

🔧 Fix: Run `/browser-setup` to configure the browser tool.

Scenario 2: Chrome not running


[❌] Chrome not connected
     Error: Chrome/Edge is not running or remote debugging is not enabled

🔧 Fix:
  1. Open Chrome or Edge
  2. Visit: chrome://inspect/#remote-debugging
  3. Click "Allow remote debugging"

Scenario 3: MCP not installed


[❌] chrome-devtools-mcp not installed

🔧 Fix: Run `npm install -g chrome-devtools-mcp@latest`
      (or run `/browser-setup` to install automatically)

Scenario 4: Everything OK


✅ All systems operational!

The browser tool is ready to use.

Online Troubleshooting Guide

If any ❌ items are found, or the user reports a problem you cannot resolve with the above scenarios, fetch the latest troubleshooting guide:


web_fetch(url="https://www.openclacky.com/docs/browser-troubleshooting")

Use the content from that page to provide up-to-date diagnosis and resolution steps. This online document is maintained separately and may contain newer solutions not listed here.

Publisher	clacky-ai
Repository	`openclacky`
Skill name	`browser-setup`
Stars	1.2K
Forks	111
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Browser Setup

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Browser Setup Skill

Region-Aware Download Links

Command Parsing

`setup`

Step 1 — Ensure Node.js is installed

Step 2 — Ensure chrome-devtools-mcp is installed

Step 3 — Verify Chrome/Edge is running with remote debugging

Case A: "Chrome/Edge is not running or remote debugging is not enabled"

Case B: Other errors (MCP handshake timeout, daemon crash, etc.)

Step 4 — Get and verify browser version

Step 5 — Save configuration via API

Step 6 — Done

`doctor`

Diagnostic Steps

1. Check Config File

2. Check Node.js

3. Check chrome-devtools-mcp

4. Check Clacky Server

5. Check Chrome Connection

6. Check Chrome Version

Report Format

Common Diagnostic Scenarios

Online Troubleshooting Guide

Frequently asked questions

Set up your own AI workspace now

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Browser Setup Skill

Region-Aware Download Links

Command Parsing

setup

Step 1 — Ensure Node.js is installed

Step 2 — Ensure chrome-devtools-mcp is installed

Step 3 — Verify Chrome/Edge is running with remote debugging

Case A: "Chrome/Edge is not running or remote debugging is not enabled"

Case B: Other errors (MCP handshake timeout, daemon crash, etc.)

Step 4 — Get and verify browser version

Step 5 — Save configuration via API

Step 6 — Done

doctor

Diagnostic Steps

1. Check Config File

2. Check Node.js

3. Check chrome-devtools-mcp

4. Check Clacky Server

5. Check Chrome Connection

6. Check Chrome Version

Report Format

Common Diagnostic Scenarios

Online Troubleshooting Guide

Frequently asked questions

Related AI Skills

Set up your own AI workspace now

`setup`

`doctor`