browser

What This Skill Does

The Browser skill acts as a powerful interface for automating complex web interactions using the Stagehand CLI engine coupled with Claude's reasoning capabilities. It abstracts the complexity of headless browser automation, allowing users to issue natural language commands instead of writing boilerplate code. Whether you need to navigate to a site, interact with DOM elements, or perform complex data extraction, this skill handles the heavy lifting. It intelligently toggles between local Chrome instances for rapid development and remote Browserbase environments for production-grade scraping, stealth, and proxy support.

Installation

To add the browser skill to your agent, run the install command in your project terminal: clawhub install openclaw/skills/skills/peytoncasper/agent-browser-stagehand. Once the installation is complete, verify the setup status by inspecting the setup.json file in the skill directory. If the setup is not marked as complete, navigate to the skill directory and run npm install followed by npm link to register the global browser command. If you intend to use the remote Browserbase features, ensure your environment variables (BROWSERBASE_API_KEY and BROWSERBASE_PROJECT_ID) are correctly configured in your .env file.

Use Cases

This skill is designed for scenarios requiring programmatic web interaction. Common use cases include: automated web testing to ensure UI components are functional; data scraping where unstructured web content needs to be converted into structured JSON formats; automated form filling for repetitive administrative tasks; and monitoring web applications for specific changes or status updates. It is particularly effective for workflows that require bypassing basic anti-bot protections via Browserbase.

Example Prompts

1. "Open the browser, navigate to the login page for my dashboard, and enter my credentials."
2. "Go to the documentation site and extract all the h2 tags into a structured JSON list."
3. "Browse to the news website and take a screenshot of the main header to verify it loaded correctly."

Tips & Limitations

For the best results, always prioritize navigation commands before attempting interactions. If an action fails, use the browser observe command to see the current state of the DOM; this is invaluable for debugging element selectors. Remember that local execution is faster but lacks the advanced stealth features of remote environments. Always close your browser sessions to prevent resource leakage, especially when running multiple tasks in a sequence.