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.
Security Analysis
high confidenceThe skill's documentation describes a CLI browser tool that needs local code, Chrome, and API keys, but the package is instruction-only and omits the claimed source files and declared environment requirements — this mismatch and the use of persistent browser profiles/download folders warrants caution.
The declared purpose (browser automation via a CLI) is coherent with the instructions (commands like browser navigate/act/extract). However the registry metadata claims no required env or binaries, while the docs repeatedly require Chrome, an Anthropic model API key (ANTHROPIC_API_KEY) and optionally Browserbase keys (BROWSERBASE_API_KEY, BROWSERBASE_PROJECT_ID). The package omits the code files (no src/, no package.json) that the docs reference (e.g. src/cli.ts), so the claimed capability cannot be fulfilled by the files present.
SKILL.md and REFERENCE.md instruct the agent to run npm install and npm link, inspect .env for API keys, launch Chrome with a persistent profile (.chrome-profile/) and write downloads/screenshots into ./agent/... — these steps read and persist user data (profile, cookies, downloads) and could access sensitive data beyond a minimal browsing task. The skill also states selection between 'Browserbase' remote mode and local Chrome happens automatically (no user prompting), which implies the agent will check local configuration files and environment without explicit consent.
There is no formal install spec in the registry, but the runtime instructions tell the agent to run 'npm install' and 'npm link' if setupComplete is false. Since this skill bundle does not include the referenced source or package.json, those commands would either fail or pull/execute code from the current directory/environment — a risky implicit install path. Instruction-driven installs (npm install) are higher risk when package sources and checksums are not included or verifiable.
The registry declares no required env vars, but setup.json and REFERENCE.md require ANTHROPIC_API_KEY and SKILL.md mentions optional Browserbase keys (BROWSERBASE_API_KEY, BROWSERBASE_PROJECT_ID). That inconsistency is problematic: the skill will attempt to read secrets that are not declared to the platform. Additionally, the use of a persistent Chrome profile means site cookies and sessions could be reused or inspected, which is sensitive and exceeds the minimal needs for ephemeral browsing tasks.
The skill is not marked 'always:true' and does not request special platform privileges. However it instructs creation/use of persistent artifacts (.chrome-profile, ./agent/downloads, ./agent/browser_screenshots) which persist across runs and can store cookies, session tokens, and downloaded files. Autonomous invocation is allowed (platform default); combined with file-system persistence this increases blast radius if the skill behaves unexpectedly.
Guidance
Do not install or run this skill yet. The package lacks the code and package metadata the docs reference (no src/, no package.json), and the registry metadata does not declare the API keys and Chrome dependency that the instructions require — this mismatch could cause accidental npm installs or reading of local .env/.chrome-profile data. Ask the author for a complete release (source files or a verified install artifact and package.json), and insist they update the registry to declare required env vars (ANTHROPIC_API_KEY, optional Browserbase keys) and any binaries. Before running, review the actual code, prefer running in an isolated VM/container, avoid pointing it at your real Chrome profile, and never expose API keys or secrets until you verify the source. If you must test, use a disposable profile and do not run npm install in a sensitive directory.
Latest Release
v1.0.0
- Initial release of the browser automation skill as a CLI tool. - Automatically selects between local Chrome or remote Browserbase environments based on available configuration—no user prompts needed. - Supports natural language commands to navigate, extract data, interact with web pages, take screenshots, fill forms, and more. - Includes guidance for setup, command usage, and troubleshooting. - Documentation covers differences between local and remote modes, best practices, and example workflows.
More by @peytoncasper
Published by @peytoncasper on ClawHub
