browser-setup

Configure and validate Clacky browser integration for remote debugging.

1.2k|100|Updated Dec 30, 2025

Search Tags:#automation #setup #diagnostics #chrome #browser #edge #remote-debugging

Ready to run

npx skills add https://github.com/clacky-ai/openclacky --skill browser-setup

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browser-setup
Source: https://github.com/clacky-ai/openclacky/tree/main/lib/clacky/default_skills/browser-setup
Command: npx skills add https://github.com/clacky-ai/openclacky --skill browser-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configuring and verifying browser automation for Clacky can be complex and error-prone. This Skill guides users through the setup, ensures dependencies are installed, and saves the configuration to ~/.clacky/browser.yml so browser automation can be used reliably.

Core Features & Use Cases

Step-by-step setup flow that validates Node.js, chrome-devtools-mcp, and remote debugging readiness.
Automatic configuration saving via the Clacky API and a doctor diagnostic to troubleshoot issues.
Cross-platform support for macOS, Linux, and WSL environments and compatibility with Chrome or Edge.

Quick Start

Run /browser-setup to configure and verify your Chrome/Edge browser integration.

Frequently Asked Questions about browser-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I set up remote debugging for Chrome or Edge to enable browser automation?▼

To enable browser automation, you can run the setup workflow to configure remote debugging for Chrome or Edge, which validates dependencies and saves your settings to ~/.clacky/browser.yml.

What is needed to configure the Clacky browser integration on WSL or macOS?▼

Configuring the Clacky browser integration on WSL, macOS, or Linux requires validating Node.js and chrome-devtools-mcp dependencies to ensure your environment is ready for remote debugging.

Why does my browser setup fail dependency checks before saving the configuration?▼

Browser setup fails dependency checks when Node.js or chrome-devtools-mcp are missing, but you can use the built-in doctor diagnostic to troubleshoot and verify your remote debugging readiness.

Can I use Edge instead of Chrome for remote debugging setup in Linux environments?▼

Yes, you can use Edge instead of Chrome for remote debugging setup across Linux, macOS, and WSL environments, with the setup workflow automatically verifying compatibility and saving the configuration.

How do I troubleshoot browser automation issues when remote debugging is not working?▼

You can troubleshoot browser automation issues by running the doctor diagnostic tool, which identifies remote debugging failures and verifies that all required dependencies are correctly installed.

Where does the browser configuration get saved after completing the setup process?▼

After completing the setup process, the browser configuration is saved automatically to ~/.clacky/browser.yml via the API, ensuring your verified Chrome or Edge settings persist for reliable automation.