New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Browser Setup

by clacky-ai in clacky-ai/openclacky

Configure the browser tool for Clacky. An agent skill from clacky-ai/openclacky.

MITAuto-check: notesDevelopment

Install Browser Setup

skills CLI
$ npx skills add clacky-ai/openclacky --skill browser-setup -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install clacky-ai/openclacky browser-setup --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/clacky-ai/openclacky.git skills-src && mkdir -p .claude/skills && cp -r skills-src/lib/clacky/default_skills/browser-setup .claude/skills/browser-setup && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
browser-setup
GitHub stars
1.2k
Token cost
~3.1k tokens
SKILL.md length
1,097 words
Files
1
Skills in repo
20
Repo updated
First seen
Licence
MIT

At a glance

Configure the browser tool for Clacky. An agent skill from clacky-ai/openclacky.

  • Works in 6 steps: Ensure Node.js is installed → Ensure chrome-devtools-mcp is installed → Verify Chrome/Edge is running with… → …
  • : browser setup
  • SKILL.md covers Region-Aware Download Links, Command Parsing, setup and doctor
  • Calls curl, node and bash; reaches google.com and openclacky.com

What it does

Browser Setup is an agent skill from clacky-ai/openclacky. 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.

Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Debugging. It works with Linux, macOS, Node.js and Model Context Protocol. The repository describes itself as: The most Token-efficient open-source AI Agent. The licence is MIT.

When your agent uses it

  • : browser setup
  • Tasks that involve Debugging

Example prompts

  • “browser setup”
  • “setup browser”
  • “browser config”
  • “/browser-setup”

Requirements

  • Node.js
  • Pre-approved tools (allowed-tools): Bash, Read, Write, browser

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Ensure Node.js is installed
  2. Ensure chrome-devtools-mcp is installed
  3. Verify Chrome/Edge is running with remote debugging
  4. Get and verify browser version
  5. Save configuration via API
  6. Done

What it can do on your machine

Read from SKILL.md and the folder at commit 66b741e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Read
    • Write
    • browser

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • curl
    • node
    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • google.com
    • openclacky.com

    Also links to:

    • microsoft.com
    • google.cn
    • nodejs.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Browser Setup loads about 3.1k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 1,097 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~88
When it runs · the whole SKILL.md, loaded when a task matches
~3.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read, Write, browser

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from clacky-ai/openclacky at commit 66b741e, republished under its MIT licence (© clacky-ai). 1,097 words, ~3,065 tokens.

Download SKILL.mdSave it as .claude/skills/browser-setup/SKILL.md (or your agent's skills folder).
name
browser-setup
description
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.
allowed-tools
Bash, Read, Write, browser
name_zh
浏览器配置
description_zh
配置 Chrome 或 Edge 浏览器工具并检测连接，支持 macOS、Linux 和 WSL。
argument-hint
setup | doctor

Browser Setup Skill

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

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:

RegionChromeEdge
Chinahttps://www.google.cn/chrome/https://www.microsoft.com/zh-cn/edge
Globalhttps://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 saysSubcommand
browser setup, 配置浏览器, setup browsersetup
browser doctordoctor

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:

  1. Make sure Chrome or Edge is open
  2. Visit: chrome://inspect/#remote-debugging (or edge://inspect/#remote-debugging)
  3. Click "Allow remote debugging for this browser instance"
  4. You should see a brief connection message appear

Let me know when done ✅

On Linux (non-WSL):

Please follow these steps:

  1. Make sure Chrome or Edge is open
  2. Visit: chrome://inspect/#remote-debugging
  3. Click "Allow remote debugging for this browser instance"

Let me know when done ✅

On WSL:

Please follow these steps:

  1. Open Edge on Windows
  2. Visit: edge://inspect/#remote-debugging
  3. 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: <error message>

This may be a temporary issue. Please try:

  1. Restart your browser
  2. Run /browser-setup again

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

Show full SKILL.md (440 more words)Show less
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.

© clacky-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in lib/clacky/default_skills/browser-setup of clacky-ai/openclacky.

Open the folder on GitHubat commit 66b741e

Compare with similar skills

Browser Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Browser Setup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Browser Setup this skillclacky-ai/openclacky1.2k—~3.1kAutomated safety check: NotesMIT
Gearcoleco Debuggingdrhelius/Gearcoleco141—~3.5kAutomated safety check: PassGPL-3.0
Dotnet Debuggingnovotnyllc/dotnet-artisan233—~2.1kAutomated safety check: PassMIT
Extension Puppeteer Debuggingmengxi-ream/read-frog10k—~2kAutomated safety check: NotesGPL-3.0
Antigravity CLI StatuslineAndyAWD/antigravity-cli-statusline100—~2.2kAutomated safety check: PassMIT
OpenLogi Device DiagnosisAprilNEA/OpenLogi23k—~1.6kAutomated safety check: PassApache-2.0

Similar skills

  • Gearcoleco Debugging

    drhelius/Gearcoleco

    Debug and trace ColecoVision and Super Game Module games using the Gearcoleco emulator MCP server.

    141 GitHub stars~3.5k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Dotnet Debugging

    novotnyllc/dotnet-artisan

    Debugs Windows and Linux/macOS applications (native, .NET/CLR, mixed-mode) with WinDbg MCP (crash dumps, !analyze, !syncblk, !dlk, !runaway, !dumpheap, !gcroot, BSOD), dotnet-dump, lldb with SOS…

    233 GitHub stars~2.1k tokensUpdated today
    DevelopmentAuto-check passed

  • Extension Puppeteer Debugging

    mengxi-ream/read-frog

    Debug the built Read Frog extension in real Chrome. An agent skill from mengxi-ream/read-frog.

    10k GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check: notes

  • Antigravity CLI Statusline

    AndyAWD/antigravity-cli-statusline

    本技能用於設定 Antigravity 命令列介面（CLI）（agy）的狀態列（Statusline / Footer）顯示指標、顯示順序與多語系介面（繁體中文 zh-tw / English us / 日本語 jp），並自動部署跨平台 Node.js 掛鉤（Hook）腳本（statusline-quota.mjs、fetch-local-quota.mjs）至…

    100 GitHub stars~2.2k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • OpenLogi Device Diagnosis

    AprilNEA/OpenLogi

    Finds the first failing layer when an OpenLogi Logitech device is missing or misbehaving across enumeration, open, probe, IPC and UI.

    23k GitHub stars~1.6k tokensUpdated 4 days ago
    DevelopmentAuto-check passed

  • Tapd Iteration Init

    TencentBlueKing/bk-bcs

    迭代执行流水线启动器。分三个阶段执行：信息检查（验证 git 环境、获取迭代信息、 解析迭代分支）→ 恢复检测（已有状态文件时判定恢复策略）→ 新流程初始化（创建分支、 迭代目录和 iteration-state.json）。

    840 GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed

More from clacky-ai/openclacky

All 20 skills in this repo

  • Skill Add

    clacky-ai/openclacky

    Install skills from a zip URL or local zip file path. An agent skill from clacky-ai/openclacky.

    1.2k GitHub stars~560 tokensUpdated today
    Auto-check passed

  • Media Gen

    clacky-ai/openclacky

    Generate or edit images, videos, or audio in the current task.

    1.2k GitHub stars~7.3k tokensUpdated today
    Auto-check passed

  • Cron Task Creator

    clacky-ai/openclacky

    Create, manage, and run scheduled automated tasks (cron jobs) in Clacky.

    1.2k GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Deploy

    clacky-ai/openclacky

    Deploy Rails applications to Railway. An agent skill from clacky-ai/openclacky.

    1.2k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • MCP Manager

    clacky-ai/openclacky

    Manage MCP (Model Context Protocol) servers for openclacky: add, list, probe, remove, reconfigure.

    1.2k GitHub stars~3k tokensUpdated today
    Auto-check passed

  • New

    clacky-ai/openclacky

    Create a new project to start development quickly. An agent skill from clacky-ai/openclacky.

    1.2k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Browser Setup

What does Browser Setup do?

Configure the browser tool for Clacky. An agent skill from clacky-ai/openclacky. Browser Setup is an agent skill from clacky-ai/openclacky. Configure the browser tool for Clacky.

When should I use Browser Setup?

Browser Setup fits situations like: : browser setup; tasks that involve Debugging.

How do I install Browser Setup in Claude Code?

Run `npx skills add clacky-ai/openclacky --skill browser-setup -a claude-code`. Or copy the skill folder (lib/clacky/default_skills/browser-setup in clacky-ai/openclacky) into .claude/skills/browser-setup in your project. Claude Code loads it when a task matches its description.

How do I install Browser Setup in Codex?

Run `npx skills add clacky-ai/openclacky --skill browser-setup -a codex`. Or copy the skill folder (lib/clacky/default_skills/browser-setup in clacky-ai/openclacky) into .agents/skills/browser-setup in your project. Codex loads it when a task matches its description.

Can I use Browser Setup in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add clacky-ai/openclacky --skill browser-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/browser-setup, .gemini/skills/browser-setup, .github/skills/browser-setup and .opencode/skills/browser-setup in your project.

What does Browser Setup need to run?

Going by SKILL.md and its folder, Browser Setup needs the command-line tools its instructions call (curl, node and bash). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Bash, Read, Write, browser.

Does Browser Setup access the network?

SKILL.md names 5 domains. In commands or code: google.com and openclacky.com; the agent is likely to contact these when it follows the instructions. As links in the text: microsoft.com, google.cn and nodejs.org. This is read from the text; nothing was executed.

Is Browser Setup safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Browser Setup use?

Browser Setup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Browser Setup use?

About 3.1k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Browser Setup?

Skills that share tags, products or a category with Browser Setup: Gearcoleco Debugging (drhelius/Gearcoleco, 141 stars), Dotnet Debugging (novotnyllc/dotnet-artisan, 233 stars), Extension Puppeteer Debugging (mengxi-ream/read-frog, 10k stars) and Antigravity CLI Statusline (AndyAWD/antigravity-cli-statusline, 100 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Browser Setup?

clacky-ai (a GitHub organization) maintains it in clacky-ai/openclacky, which has 1,204 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 8, 2026.

Source: clacky-ai/openclacky on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.