From harness
Use this skill whenever the user asks to visit a URL, click elements, fill out forms, scrape content, automate a website, log into a service, take a screenshot of a page, or perform any browser-driven workflow. Also use when the user needs UI testing, visual regression checks, or web data extraction. Do NOT load for: sharing or embedding URLs in code, reading local screenshot image files, or non-browser file operations. Automates browser interactions — navigate pages, fill forms, take screenshots, extract web data, and test web apps.
npx claudepluginhub tim-hub/powerball-harness --plugin harnessThis skill is limited to using the following tools:
A skill for browser automation. Uses the agent-browser CLI to perform UI debugging, verification, and automated operations.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
A skill for browser automation. Uses the agent-browser CLI to perform UI debugging, verification, and automated operations.
This skill is automatically triggered by the following phrases:
| Feature | Details |
|---|---|
| Browser Automation | See references/browser-automation.md |
| AI Snapshot Workflow | See references/ai-snapshot-workflow.md |
# Check installation
which agent-browser
# If not installed
npm install -g agent-browser
agent-browser install
| Request Type | Corresponding Action |
|---|---|
| Open a URL | agent-browser open <url> |
| Click an element | Snapshot → agent-browser click @ref |
| Fill a form | Snapshot → agent-browser fill @ref "text" |
| Check state | agent-browser snapshot -i -c |
| Screenshot | agent-browser screenshot <path> |
| Debug | agent-browser --headed open <url> |
For most operations, first take a snapshot and then interact using element references:
# 1. Open the page
agent-browser open https://example.com
# 2. Take a snapshot (AI-friendly, interactive elements only)
agent-browser snapshot -i -c
# Example output:
# - link "Home" [ref=e1]
# - button "Login" [ref=e2]
# - input "Email" [ref=e3]
# - input "Password" [ref=e4]
# - button "Submit" [ref=e5]
# 3. Interact using element references
agent-browser click @e2 # Click the Login button
agent-browser fill @e3 "user@example.com"
agent-browser fill @e4 "password123"
agent-browser click @e5 # Submit
# Check current state with a snapshot
agent-browser snapshot -i -c
# Or check the URL
agent-browser get url
# Take a screenshot
agent-browser screenshot result.png
| Command | Description |
|---|---|
open <url> | Open a URL |
snapshot -i -c | AI-friendly snapshot |
click @e1 | Click an element |
fill @e1 "text" | Fill a form field |
type @e1 "text" | Type text |
press Enter | Press a key |
screenshot [path] | Take a screenshot |
close | Close the browser |
| Command | Description |
|---|---|
back | Go back |
forward | Go forward |
reload | Reload |
| Command | Description |
|---|---|
get text @e1 | Get text |
get html @e1 | Get HTML |
get url | Current URL |
get title | Page title |
| Command | Description |
|---|---|
wait @e1 | Wait for an element |
wait 1000 | Wait 1 second |
| Command | Description |
|---|---|
--headed | Show the browser |
console | Console logs |
errors | Page errors |
highlight @e1 | Highlight an element |
Manage multiple tabs/sessions in parallel:
# Specify a session
agent-browser --session admin open https://admin.example.com
agent-browser --session user open https://example.com
# List sessions
agent-browser session list
# Operate within a specific session
agent-browser --session admin snapshot -i -c
| Tool | Recommendation | Use Case |
|---|---|---|
| agent-browser | ★★★ | First choice. Powerful AI-friendly snapshots |
| chrome-devtools MCP | ★★☆ | When Chrome is already open |
| playwright MCP | ★★☆ | Complex E2E testing |
Principle: Try agent-browser first; use MCP tools only if it does not work.
--headed option to display the browserclose