Browser Stagehand

Automate web browser interactions using natural language via CLI commands. Use when the user asks to browse websites, navigate web pages, extract data from w...

This skill appears to implement the advertised browser automation CLI, but the registry metadata omits important runtime requirements and behaviors. Before installing or running it, consider the following: (1) the docs expect an ANTHROPIC_API_KEY (and optionally Browserbase API keys) stored in .env or exported — do not place unrelated secrets there; (2) the tool uses a persistent Chrome profile (.chrome-profile) and will preserve cookies/sessions — use a dedicated profile or run in a disposable environment if you don't want session data retained; (3) downloads go to ./agent/downloads and screenshots to ./agent/browser_screenshots — review those directories and clean them after use; (4) the setup requires running `npm install`/`npm link` which installs external packages — inspect package.json and dependency sources before installing; (5) the skill auto-selects remote vs local mode without prompting, which could cause it to use remote services if API keys are present; (6) ask the publisher to update registry metadata to list required env vars (ANTHROPIC_API_KEY, optional BROWSERBASE_API_KEY/BROWSERBASE_PROJECT_ID), required binaries (Chrome), and to provide a source repository so you can inspect code. If you cannot verify these details, run the tool in an isolated container or VM and avoid sharing production credentials.

Type: OpenClaw Skill Name: openclaw-browser-stagehand Version: 1.0.0 The skill provides extensive browser automation capabilities using the Stagehand library, including full network access (with explicit mention of localhost/internal networks), persistent session storage via '.chrome-profile/', and automatic file downloads to the local filesystem. While these features are documented in REFERENCE.md and EXAMPLES.md as necessary for the tool's stated purpose, they represent high-risk behaviors—specifically the ability to interact with internal services and perform 'stealth' operations (e.g., launching the browser off-screen at -9999,-9999). Per the analysis criteria, these risky capabilities warrant a suspicious classification despite the lack of clear evidence of malicious intent.