SkillAgentSearch skills...

chrome-automation

网页开发工程师与运营专员在需要自动化现有 Chrome 浏览器时必用!通过 CDP 协议无缝接管当前浏览器,自动配置环境并实时可视化执行任务。完美保留登录状态,一键完成复杂网页自动化流程,让繁琐操作自动化。

Install / Use

npx skills add anbeime/skill --skill chrome-automation

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

93/100

Category

Automation

Supported Platforms

Universal

Our assessment of chrome-automation

chrome-automation scores 93/100 on our quality scale, 644th of 2,790 Automation skills we index (top 24%).

Its SKILL.md is 21 KB long, well organised into 131 sections with 31 code examples: a thorough specification that gives an agent plenty to work with.

With 7,172 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
20/20
Description
12/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so chrome-automation is actively maintained.
  • Our last check on 2026-10-26 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

Review

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands (2 minor notes below). An AI review judged it risky: The skill instructs the agent to run `curl ... https://sh.rustup.rs | sh -s -- -y`, piping a remote installer directly into a shell (lines ~199 and ~556).

  • noteInstalls by piping a downloaded script into a shellline 199
    curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y
  • noteInstalls by piping a downloaded script into a shellline 556
    # 1. Install Rust: curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y

AI review: risky

  • The skill instructs the agent to run `curl ... https://sh.rustup.rs | sh -s -- -y`, piping a remote installer directly into a shell (lines ~199 and ~556).
  • It repeatedly tells the agent to execute local auto-install and start-Chrome scripts without user confirmation, and to avoid fallback tools.
  • It uses `powershell -ExecutionPolicy Bypass` to run local scripts, weakening PowerShell's normal script execution safeguards.

AI review by kimi-k2.7-code on 2026-09-27. Automated pattern scan on 2026-09-27. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

chrome-automation compared with similar skills

All 4 of these similar skills score higher than chrome-automation; compare them before choosing.

SkillScoreStarsUpdatedFormat
chrome-automation (this skill)by anbeime937.2k53d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server

Frequently asked questions

How do I install chrome-automation?
Run npx skills add anbeime/skill --skill chrome-automation. The install tabs above show the steps for each supported agent.
Which AI agents does chrome-automation work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is chrome-automation safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands (2 minor notes below). An AI review judged it risky: The skill instructs the agent to run curl ... https://sh.rustup.rs | sh -s -- -y, piping a remote installer directly into a shell (lines ~199 and ~556). It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is chrome-automation still maintained?
The repository was last updated about 2 months ago, so chrome-automation is actively maintained.

name: chrome-automation description: 网页开发工程师与运营专员在需要自动化现有 Chrome 浏览器时必用!通过 CDP 协议无缝接管当前浏览器,自动配置环境并实时可视化执行任务。完美保留登录状态,一键完成复杂网页自动化流程,让繁琐操作自动化。 allowed-tools: Bash(*)

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:

# 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:

  • ❌ DO NOT fall back to using built-in browser tools (browser_use_desktop)
  • ✅ MUST run auto-install script before any browser automation
  • ✅ Only proceed with browser automation AFTER successful installation
  • ✅ Script handles all dependency checks automatically

Why agent-browser is required:

  • Provides real-time visual feedback in user's actual Chrome browser
  • Allows user to see and interact with automation in progress
  • Offers precise element selection and interaction capabilities
  • Built-in browser tools are NOT a substitute for this skill's functionality

Quick Start

First-time setup (automatic)

Run the auto-install script first:

# Mac
bash ~/.claude/skills/chrome-automation/scripts/auto-install-mac.sh

# Windows (PowerShell)
powershell -ExecutionPolicy Bypass -File "$HOME\.claude\skills\chrome-automation\scripts\auto-install-windows.ps1"

The script automatically handles:

  • Repository cloning
  • Dependency installation (pnpm, Playwright)
  • Rust toolchain setup
  • Native binary compilation

Connect and control Chrome

IMPORTANT: Use the start-chrome script to preserve login states across sessions

# Mac: Start Chrome with persistent profile (RECOMMENDED)
# This preserves your login states, cookies, and settings
bash ~/.claude/skills/chrome-automation/scripts/start-chrome-mac.sh

# Windows: Start Chrome with persistent profile (PowerShell)
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
AGENT_BROWSER_HOME=/Users/jyxc-dz-0100272/Documents/agent-browser \
./bin/agent-browser --cdp 9222 snapshot -i

What the start-chrome script does:

  1. First run: Creates a dedicated automation profile at ~/Library/Application Support/Google/Chrome-Automation
  2. First run: Imports your existing Chrome configuration (login states, cookies, settings)
  3. Subsequent runs: Uses the existing automation profile - all your logins are preserved
  4. You only need to log in once - it will be remembered for future sessions

Core Workflow

CRITICAL: Always show browser state to user after each significant action using screenshots.

  1. Connect: Ensure Chrome running with remote debugging port 9222
  2. Navigate: Open pages using --cdp 9222 flag
  3. Snapshot: Get interactive elements with snapshot -i
  4. Interact: Use element refs (@e1, @e2, etc.)
  5. Screenshot: Capture state and show to user
  6. Report: Describe what's visible in browser

Standard operation pattern

# Set path variables
export AB_HOME=/Users/jyxc-dz-0100272/Documents/agent-browser
cd $AB_HOME

# Navigate
AGENT_BROWSER_HOME=$AB_HOME ./bin/agent-browser --cdp 9222 open https://example.com
sleep 2

# Get interactive elements
AGENT_BROWSER_HOME=$AB_HOME ./bin/agent-browser --cdp 9222 snapshot -i

# Screenshot to show user
AGENT_BROWSER_HOME=$AB_HOME ./bin/agent-browser --cdp 9222 screenshot /tmp/state.png

# Interact
AGENT_BROWSER_HOME=$AB_HOME ./bin/agent-browser --cdp 9222 fill @e1 "text"
AGENT_BROWSER_HOME=$AB_HOME ./bin/agent-browser --cdp 9222 press Enter

# Capture result
sleep 2
AGENT_BROWSER_HOME=$AB_HOME ./bin/agent-browser --cdp 9222 screenshot /tmp/result.png

Installation & Setup

Automatic Installation (RECOMMENDED)

Always use the auto-install script - it handles all dependencies automatically:

Mac Installation

# Run auto-install script
bash ~/.claude/skills/chrome-automation/scripts/auto-install-mac.sh

What it does:

  1. Checks if agent-browser binary exists and works
  2. Clones repository if missing
  3. Installs Node.js dependencies (pnpm)
  4. Installs Playwright Chromium
  5. Checks/installs Rust toolchain (cargo, rustup)
  6. Sets up stable Rust toolchain if needed
  7. Builds native binary with npm run build:native
  8. Verifies installation success

Requirements:

  • Node.js (will notify if missing)
  • Git (for cloning repository)
  • Internet connection

Windows Installation

# Run auto-install script (PowerShell)
powershell -ExecutionPolicy Bypass -File "$HOME\.claude\skills\chrome-automation\scripts\auto-install-windows.ps1"

What it does:

  1. Checks if agent-browser binary exists and works
  2. Clones repository if missing
  3. Installs Node.js dependencies (pnpm)
  4. Installs Playwright Chromium
  5. Downloads and installs Rust toolchain if needed
  6. Sets up stable Rust toolchain
  7. Builds native binary with npm run build:native
  8. Verifies installation success

Requirements:

  • Node.js (will notify if missing - download from https://nodejs.org/)
  • Git (for cloning repository)
  • Internet connection

Manual Installation (Advanced Users Only)

If you prefer manual installation or need to troubleshoot:

Mac Manual Steps

# 1. Clone repository
cd ~/Documents
git clone https://github.com/vercel-labs/agent-browser.git
cd agent-browser

# 2. Install Node dependencies
pnpm install
npx playwright install chromium

# 3. Install Rust (if not installed)
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y
export PATH="$HOME/.cargo/bin:$PATH"
rustup default stable

# 4. Build native binary
npm run build:native

Windows Manual Steps

# 1. Clone repository
Set-Location "$HOME\Documents"
git clone https://github.com/vercel-labs/agent-browser.git
Set-Location agent-browser

# 2. Install Node dependencies
pnpm install
npx playwright install chromium

# 3. Install Rust (if not installed)
# Download from: https://win.rustup.rs/x86_64
# Or use the auto-install script

# 4. Build native binary
npm run build:native

Verify Installation

After installation (automatic or manual), verify it works:

# Mac
cd ~/Documents/agent-browser
AGENT_BROWSER_HOME=~/Documents/agent-browser ./bin/agent-browser --version

# Windows (PowerShell)
Set-Location "$HOME\Documents\agent-browser"
$env:AGENT_BROWSER_HOME = "$HOME\Documents\agent-browser"
.\bin\agent-browser.cmd --version

Troubleshooting Installation

"No binary found for darwin-arm64" or "No binary found for win32-x64":

  • Rust is not installed or not in PATH
  • Run the auto-install script, it will handle Rust installation
  • Or manually install Rust and run npm run build:native

"cargo: command not found":

  • Rust toolchain not in PATH
  • Mac: export PATH="$HOME/.cargo/bin:$PATH"
  • Windows: $env:PATH = "$HOME\.cargo\bin;$env:PATH"
  • Then run rustup default stable and npm run build:native

"rustup could not choose a version":

  • Default toolchain not set
  • Run: rustup default stable
  • Then rebuild: npm run build:native

Common Rust Installation Issues

Issue 1: Permission denied when installing Rust (Mac)

When running the Rust installer, you may encounter:

error: could not amend shell profile: '/Users/username/.bash_profile': 
could not write rcfile file: Permission denied (os error 13)

Solution: This error is usually harmless - Rust binaries are still installed successfully to ~/.cargo/bin/. The error only affects automatic PATH configuration in shell profiles.

Fix steps:

# Mac: Set default toolchain manually
/Users/username/.cargo/bin/rustup default stable

# This will download and install:
# - cargo, clippy, rust-docs, rust-std, rustc, rustfmt

Issue 2: Rust installed but cargo not found (Mac)

After Rust installation, running cargo fails with "command not found".

Root cause:

  • Rust binaries are in ~/.cargo/bin/ but not in current shell's PATH
  • Default toolchain not configured

Solution:

# Use full path to set default toolchain
~/.cargo/bin/rustup default stable

# Then build with full path
cd ~/Documents/agent-browser/cli
~/.cargo/bin/cargo build --release

# Or add to PATH for current session
export PATH="$HOME/.cargo/bin:$PATH"
cargo build --release

Issue 3: Rust installation permission errors (Windows)

On Windows, Rust installer may fail with access denied errors.

Solution:

# Run PowerShell as Administrator, then:
# Download and run Rust installer
Invoke-WebRequest -Uri "https://win.rustup.rs/x86_64" -OutFile "$env:TEMP\rustup-init.exe"
& "$env:TEMP\rustup-init.exe" -y

# Set default toolchain
& "$env:USERPROFILE\.cargo\bin\rustup.exe" default stable

# Add to PATH for current session
$env:PATH = "$env:USERPROFILE\.cargo\bin;$env:PATH"

Issue 4: Build fails even after Rust installation

Symptoms:

  • npm run build:native fails
  • "cargo: command not found" in build output

Solution:

# Mac: Build with explicit cargo path
cd ~/Documents/agent-browser/cli
~/.cargo/bin/cargo build --release

# Then copy binary manually
cd ~/Documents/agent-browser
node scripts/copy-native.js

# Windows: Build with explicit cargo path
Set-Location "$HOME\Documents\agent-browser\cli"
& "$env:USERPROFILE\.cargo\bin\cargo.exe" build --release

# Then copy binary manually
Set-Location "$HOME\Documents\agent-browser"
node scripts/copy-native.js

Key Takeaway: Even if Rust installation shows permission errors, the binaries are usually installed successfully. The main issue is:

  1. Default toolchain not configured → Run rustup default stable with full path
  2. PATH not updated → Use full paths to cargo/rustup, or manually add ~/.cargo/bin to PATH

For detailed troubleshooting, see:

  • references/setup-mac.md
  • references/setup-windows.md
  • references/troubleshooting.md

Chrome Connection

Method 1: Start Chrome with persistent profile (Recommended)

Use the start-chrome script to preserve login states across sessions:

# Mac: Start Chrome with persistent profile
bash ~/.claude/skills/chrome-automation/scripts/start-chrome-mac.sh

# Windows (PowerShell):
powershell -ExecutionPolicy Bypass -File "$HOME\.claude\skills\chrome-automation\scripts\start-chrome-windows.ps1"

First time setup (automatic):

  • Creates dedicated profile at ~/Library/Application Support/Google/Chrome-Automation (Mac)
  • Or %USERPROFILE%\AppData\Local\Google\Chrome-Automation (Windows)
  • Imports your existing Chrome configuration (login states, cookies, bookmarks)
  • Excludes large cache files to save space

Subsequent runs:

  • Uses the existing automation profile
  • All your logins are preserved
  • No need to log in again
# Verify connection after starting Chrome
cd /Users/jyxc-dz-0100272/Documents/agent-browser
AGENT_BROWSER_HOME=/Users/jyxc-dz-0100272/Documents/agent-browser \
./bin/agent-browser --cdp 9222 get url

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars7.2k
CategoryAutomation
Updated1mo ago
Forks666

Languages

Python

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium
chrome-automation — Universal Skill: Install & Safety Check | SkillAgent