agentsclimarketplace

Agent browser

Skill maxwell2732/claudecode-research-harness-workflow/skills/agent-browser

Browser automation through the repo agent-browser CLI. Explicit helper for navigation, forms, screenshots, scraping, and web-app checks. Prefer Browser Use or Playwright when available. Do NOT load for: sharing URLs, embedding links, or editing screenshot files.From its SKILL.md

Install
npx -y skills add maxwell2732/claudecode-research-harness-workflow --skill agent-browser

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

4.8 KB, as published. Nobody here has run it

Agent Browser Skill

A skill for browser automation. Uses the agent-browser CLI to perform UI debugging, verification, and automated interaction.


Trigger Phrases

This skill is automatically invoked by the following phrases:

  • "Open this page", "Check the URL"
  • "Click on", "Type into", "Fill the form"
  • "Take a screenshot"
  • "Check the UI", "Test the screen"
  • "open this page", "click on", "fill the form", "screenshot"

Features

FeatureDetails
Browser AutomationSee references/browser-automation.md
AI Snapshot WorkflowSee references/ai-snapshot-workflow.md

Execution Steps

Step 0: Verify agent-browser

# Check installation
which agent-browser

# If not installed
npm install -g agent-browser
agent-browser install

Step 1: Classify the User's Request

Request TypeAction
Open a URLagent-browser open <url>
Click an elementSnapshot → agent-browser click @ref
Fill a formSnapshot → agent-browser fill @ref "text"
Check stateagent-browser snapshot -i -c
Take screenshotagent-browser screenshot <path>
Debugagent-browser --headed open <url>

Step 2: AI Snapshot Workflow (Recommended)

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-optimized, interactive elements only)
agent-browser snapshot -i -c

# Sample output:
# - link "Home" [ref=e1]
# - button "Login" [ref=e2]
# - input "Email" [ref=e3]
# - input "Password" [ref=e4]
# - button "Submit" [ref=e5]

# 3. Interact via element references
agent-browser click @e2           # Click Login button
agent-browser fill @e3 "[email protected]"
agent-browser fill @e4 "password123"
agent-browser click @e5           # Submit

Step 3: Verify the Result

# Check current state via snapshot
agent-browser snapshot -i -c

# Or check the URL
agent-browser get url

# Take a screenshot
agent-browser screenshot result.png

Quick Reference

Basic Operations

CommandDescription
open <url>Open a URL
snapshot -i -cAI-optimized snapshot
click @e1Click an element
fill @e1 "text"Fill a form
type @e1 "text"Type text
press EnterPress a key
screenshot [path]Take a screenshot
closeClose the browser

Navigation

CommandDescription
backGo back
forwardGo forward
reloadReload

Retrieving Information

CommandDescription
get text @e1Get text
get html @e1Get HTML
get urlCurrent URL
get titlePage title

Waiting

CommandDescription
wait @e1Wait for element
wait 1000Wait 1 second

Debugging

CommandDescription
--headedShow browser
consoleConsole logs
errorsPage errors
highlight @e1Highlight element

Session Management

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 in a specific session
agent-browser --session admin snapshot -i -c

Choosing Between agent-browser and MCP Browser Tools

ToolRecommendationUse Case
agent-browser★★★First choice. Powerful AI-optimized 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 doesn't work.


Notes

  • agent-browser runs in headless mode by default
  • Use --headed to show the browser
  • Sessions persist until explicitly closed
  • Use sessions for sites requiring authentication

Keep looking

Skills are one crate of 626,194. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.