chrome-automation
Connect to and control Google Chrome browser using agent-browser with CDP (Chrome DevTools Protocol). Use when the user wants to automate their existing Chrome browser, see browser actions in real-time, or needs to control the Chrome instance they're already using. Handles installation, setup, connecting via remote debugging, and all browser automation tasks with live visual feedback.
npx skills add anbeime/skill --skill chrome-automation --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Chrome Browser Automation with Real-time Control Control the user's Google Chrome browser using agent-browser connected via Chrome DevTools Protocol (CDP). All actions are visible in real-time in the user's browser window. ## ⚠️ CRITICAL: Automatic Installation & Dependency Check **BEFORE using this skill, ALWAYS run the auto-installation check:** This skill automatically checks and installs all required dependencies without user confirmation. The installation process verifies: - agent-browser repository and binary - Node.js and pnpm - Playwright Chromium - Rust toolchain (cargo) - Native binary compilation **Auto-installation workflow:** ```bash # Mac: Run auto-install script bash ~/.claude/skills/chrome-automation/scripts/auto-install-mac.sh # Windows: Run auto-install script (PowerShell) powershell -ExecutionPolicy Bypass -File "$HOME\.claude\skills\chrome-automation\scripts\auto-install-windows.ps1" ``` **The script will:** 1. Check if agent-browser binary exists and works 2. Install missing dependencies automatically (pnpm, Rust, etc.) 3. Clone repository if not present 4. Build native binary with proper Rust toolchain 5. Verify installation success **Critical rules:** - ❌ D
- ⚠️ CRITICAL: Automatic Installation & Dependency Check
- Quick Start
- First-time setup (automatic)
- Connect and control Chrome
- Core Workflow
- Standard operation pattern
- Installation & Setup
- Automatic Installation (RECOMMENDED)
- Manual Installation (Advanced Users Only)
- Verify Installation
- Troubleshooting Installation
- Chrome Connection
- Method 1: Start Chrome with persistent profile (Recommended)
- Method 2: Connect to existing Chrome
bash ~/.claude/skills/chrome-automation/scripts/auto-install-mac.sh powershell -ExecutionPolicy Bypass -File "$HOME\.claude\skills\chrome-automation\scripts\auto-install-windows.ps1" Mac Windows (PowerShell) This preserves your login states, cookies, and settings bash ~/.claude/skills/chrome-automation/scripts/start-chrome-mac.sh powershell -ExecutionPolicy Bypass -File "$HOME\.claude\skills\chrome-automation\scripts\start-chrome-windows.ps1" Use agent-browser with --cdp flag cd /Users/jyxc-dz-0100272/Documents/agent-browser Set path variables
What does the chrome-automation skill do?
Connect to and control Google Chrome browser using agent-browser with CDP (Chrome DevTools Protocol). Use when the user wants to automate their existing Chrome browser, see browser actions in real-time, or needs to control the Chrome instance they're already using. Handles installation, setup, connecting via remote debugging, and all browser automation tasks with live visual feedback.
How do I install it?
Run `npx skills add anbeime/skill --skill chrome-automation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From anbeime/skill, a repository with 4,714 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
