The ATR Browser skill empowers Claude with comprehensive browser control and automation capabilities. By leveraging a dedicated browser server mode, it enables the agent to navigate URLs, interact with complex web elements, perform data scraping, and capture visual snapshots, bridging the gap between AI reasoning and real-time web interaction.

When should I use atr-browser?

atr-browser is useful in the following scenarios: • Automated Web Testing: Perform end-to-end QA testing by simulating user actions like clicking, typing, and navigating to verify website functionality. • Dynamic Data Extraction: Scrape content from modern, JavaScript-heavy websites that require interaction or session management to reveal data. • Visual Monitoring and Auditing: Capture full-page or element-specific screenshots to monitor UI changes, verify layouts, or document web states. • Workflow Automation: Streamline repetitive browser-based tasks such as filling out multi-step forms, downloading reports, or navigating through authenticated portals. • SEO and Competitor Analysis: Programmatically inspect page metadata, HTML structure, and console logs to analyze site performance and competitive positioning.

name	atr-browser
description	Control browser, automate browser interactions, navigate to URLs, click on webpages, fill forms, take screenshots, inspect webpages, web scraping with browser, test websites manually, or interact with web pages programmatically using ATR browser server mode.
allowed-tools	Bash(atr browser:*)

ATR Browser Automation Skill

This skill provides browser automation capabilities through ATR's browser server mode. The browser server runs as a daemon process and accepts CLI commands for browser control.

Architecture

Claude Code --> atr CLI (client) --> ATR Server + Browser

The browser runs in visible (non-headless) mode by default for debugging and verification.

Getting Started

Step 1: Check Browser Status and Start if Needed

Before any browser operations, verify the browser server is running:

atr browser status

If the server is not running, start it:

atr browser start

The server stores state at ~/.atr/browser.state which allows subsequent commands to discover the endpoint automatically.

Step 2: Navigate and Interact

Once running, use navigation and interaction commands to control the browser.

Command Categories

Lifecycle Commands

Command	Description
`atr browser start [--port PORT]`	Start browser daemon (default port: 9333)
`atr browser stop`	Stop browser daemon
`atr browser status`	Check if browser is running

Command	Description
`atr browser navigate <url>`	Navigate to URL
`atr browser back`	Go back in history
`atr browser forward`	Go forward in history
`atr browser reload`	Reload current page

Page Management Commands

Command	Description
`atr browser new-page [url]`	Open new tab
`atr browser list-pages`	List all tabs
`atr browser select-page <index>`	Switch to tab (0-based)
`atr browser close-page <index>`	Close tab

Interaction Commands

Command	Description
`atr browser click <target> [--double]`	Click element (use --double for double-click)
`atr browser fill <target> <value>`	Type into input field
`atr browser hover <target>`	Hover over element
`atr browser press-key <key>`	Press keyboard key (e.g., Enter, Tab, Control+A)
`atr browser drag <from> <to>`	Drag element

Inspection Commands

Command	Description
`atr browser snapshot [--verbose]`	Get page elements with UIDs
`atr browser screenshot --file [--full]`	Capture screenshot (saves to /tmp/)
`atr browser html`	Get page HTML
`atr browser url`	Get current URL
`atr browser title`	Get page title
`atr browser eval <script>`	Execute JavaScript

Screenshot Note: Use --file to save screenshots to /tmp/ with a timestamped filename (e.g., /tmp/atr-screenshot-20240105-103045.png). No need to specify a file path. Add --full for full-page screenshots. Without --file, returns base64-encoded image data.

Debugging Commands

Command	Description
`atr browser console [--limit N]`	Get console messages (default: 50)
`atr browser network [--limit N]`	Get network requests (default: 50)
`atr browser errors`	Get failed requests

Workflow Pattern

Follow this workflow for browser automation tasks:

Ensure Server Running

atr browser status || atr browser start

Navigate to Target

atr browser navigate https://example.com

Inspect Page Elements
```
atr browser snapshot
```
This returns elements with unique IDs (UIDs) like e0, e1, etc.
Interact with Elements Target elements by:
- Text content: "Sign In"
- UID from snapshot: e5
- CSS selector: .submit-button

Verify Results

atr browser url
atr browser title
atr browser screenshot --file

Cleanup When Done
```
atr browser stop
```

Using JSON Output

Add --json flag for structured output when parsing is needed:

atr browser snapshot --json
atr browser list-pages --json
atr browser network --json

Element Targeting

The <target> parameter in click, fill, hover, and drag commands accepts:

Element UID: e0, e5 (from snapshot output)
Visible text: "Sign In", "Submit Form"
aria-label: Elements with matching aria-label attribute
data-testid: Elements with matching data-testid attribute
CSS selector: #login-button, .nav-link

Best practice: Use atr browser snapshot first to see available elements and their UIDs.

Keyboard Keys

For press-key command:

Named keys: Enter, Tab, Escape, Backspace
Modifiers: Control+a, Shift+Tab, Alt+Enter
Arrow keys: ArrowUp, ArrowDown, ArrowLeft, ArrowRight

Troubleshooting

Browser won't start:

atr browser status
rm ~/.atr/browser.state  # If stale state
atr browser start

Port already in use:

atr browser start --port 9334

Element not found:

atr browser snapshot --verbose --json

Additional Resources

For complete command reference with all flags, see references/commands-reference.md.

atr-browser

When & Why to Use This Skill

Use Cases