Our review
Automates web browser interactions via natural-language CLI commands, with automatic fallback between local and remote browser environments.
Strengths
- Natural language interface reduces need for scripting
- Automatic environment selection between local and remote (Browserbase) without user prompting
- Supports navigation, actions, data extraction, screenshots, and element observation
Limitations
- Requires initial setup (npm install) and optionally Chrome or Browserbase API keys
- May struggle with complex interactions or dynamic content
- Performance depends on environment (remote is slower)
When you need to quickly interact with web pages, extract data, or test web applications without writing browser automation code.
When you need high-performance scraping at scale or complex multi-step workflows with extensive conditional logic.
Security analysis
SafeThe skill only runs standard npm install/link and browser automation commands. No destructive actions, no exfiltration beyond intended usage, no encoded payloads. Using Browserbase API keys from .env is part of normal operation.
No concerns found
Examples
Navigate to https://example.com and take a screenshotGo to https://example.com/login, fill in the username field with 'user' and password field with 'pass', then click the submit buttonSearch Google for 'climate change' and extract the titles and URLs of the first 10 resultsname: 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:
- If Browserbase API keys exist (BROWSERBASE_API_KEY and BROWSERBASE_PROJECT_ID in .env file): Uses remote Browserbase environment
- If no Browserbase API keys: Falls back to local Chrome browser
- No user prompting: The selection happens automatically based on available configuration
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 <url> # Go to URL
browser act "<action>" # Natural language action
browser extract "<instruction>" ['{}'] # Extract data (optional schema)
browser observe "<query>" # 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
- Always navigate first before interacting
- View screenshots after each command to verify
- Be specific in action descriptions
- Close browser when done
Troubleshooting
- Chrome not found: Install Chrome or use Browserbase mode
- Action fails: Use
browser observeto discover available elements - Browserbase fails: Verify API key and project ID are set
For detailed examples, see EXAMPLES.md. For API reference, see REFERENCE.md.
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.