Browser Automation
by @peytoncasper
Automate web browser interactions using natural language via CLI commands. Use when the user asks to browse websites, navigate web pages, extract data from websites, take screenshots, fill forms, click buttons, or interact with web applications.
clawhub install browser-automationπ About This Skill
name: browser description: Automate web browser interactions using natural language via CLI commands. Use when the user asks to browse websites, navigate web pages, extract data from websites, take screenshots, fill forms, click buttons, or interact with web applications. allowed-tools: Bash
Browser Automation
Automate browser interactions using Stagehand CLI with Claude.
First: Environment Selection (Local vs Remote)
The skill automatically selects between local and remote browser environments:
Setup (First Time Only)
Check setup.json in this directory. If setupComplete: false:
npm install # Install dependencies
npm link # Create global 'browser' command
Commands
All commands work identically in both modes:
browser navigate # Go to URL
browser act "" # Natural language action
browser extract "" ['{}'] # Extract data (optional schema)
browser observe "" # Discover elements
browser screenshot # Take screenshot
browser close # Close browser
Quick Example
browser navigate https://example.com
browser act "click the Sign In button"
browser extract "get the page title"
browser close
Mode Comparison
| Feature | Local | Browserbase | |---------|-------|-------------| | Speed | Faster | Slightly slower | | Setup | Chrome required | API key required | | Stealth mode | No | Yes | | Proxy/CAPTCHA | No | Yes | | Best for | Development | Production/scraping |
Best Practices
1. Always navigate first before interacting 2. View screenshots after each command to verify 3. Be specific in action descriptions 4. Close browser when done
Troubleshooting
browser observe to discover available elementsFor detailed examples, see EXAMPLES.md. For API reference, see REFERENCE.md.
π Tips & Best Practices
1. Always navigate first before interacting 2. View screenshots after each command to verify 3. Be specific in action descriptions 4. Close browser when done