← Back to Skills Marketplace
Openclaw Browser Automation 1.0.1
by
q262045312-ui
· GitHub ↗
· v1.0.0
· MIT-0
169
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install openclaw-browser-automation-1-0-1
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 w...
Usage Guidance
This package appears to do what it says (automate browsers), but the published metadata omits several important requirements and privacy-impacting behaviors. Before installing or running it: (1) Inspect the package's package.json and dependency list (npm install will fetch unknown code). (2) Be prepared to provide an ANTHROPIC_API_KEY and optionally Browserbase keys; only provide keys you trust the code/provider to use. (3) Understand the tool will create a persistent Chrome profile (.chrome-profile) and save downloads/screenshots under ./agent/, which can store cookies, sessions, and downloaded files — delete these when finished if they contain sensitive data. (4) Running npm link will add a global 'browser' command that executes project code; only do this for code from a trusted source. (5) Note that launching Chrome with remote-debugging on port 9222 exposes a CDP endpoint — ensure it's bound to localhost and not accessible remotely. (6) Because the skill has no provenance/homepage and the registry metadata conflicts with its own docs, treat it as untrusted until the author clarifies the discrepancies or provides the actual package code for review.
Capability Analysis
Type: OpenClaw Skill
Name: openclaw-browser-automation-1-0-1
Version: 1.0.0
The skill bundle provides powerful browser automation capabilities with high-risk features, including persistent session management via a local Chrome profile (.chrome-profile/) and automatic redirection to remote environments (Browserbase) without user prompting. It exhibits suspicious indicators such as launching the browser off-screen for stealth and referencing a non-existent AI model (Claude Haiku 4.5) in REFERENCE.md, alongside a future-dated timestamp in _meta.json. While these capabilities are plausibly needed for the stated purpose, the lack of file type restrictions on downloads and the handling of sensitive API keys warrant a cautious classification.
Capability Assessment
Purpose & Capability
The stated purpose—automating browser interactions—is consistent with the commands and examples in the docs. However the registry metadata claims no required env vars or binaries while the SKILL.md and setup.json clearly expect Chrome, npm/npm link, and API keys (ANTHROPIC_API_KEY and optional BROWSERBASE_API_KEY/BROWSERBASE_PROJECT_ID). This mismatch is an inconsistency the author should justify.
Instruction Scope
Runtime instructions instruct the agent/operator to run npm install and npm link, launch Chrome with remote-debugging on port 9222 and use a persistent profile directory (.chrome-profile), and to save downloads/screenshots under ./agent/. Those actions persist session cookies, downloads, and other browser state to disk and automatically choose remote vs local mode based on API keys found in a .env file (with no user prompt). The docs also say the tool uses an AI model (Claude Haiku) for element selection. The instructions therefore access local filesystem state and secrets (.env), persist sensitive data, and enable a remote control interface (CDP) — all of which are broader than the registry metadata indicates.
Install Mechanism
There is no install spec in the registry (instruction-only), but the included setup.json and SKILL.md instruct users to run npm install and npm link. Running those commands will fetch and build whatever dependencies are declared in package.json (which is not included in the package contents provided), so the actual code/run-time dependencies are unknown. This creates risk because arbitrary code could be installed/executed when following setup instructions.
Credentials
The skill metadata declared no required environment variables, yet SKILL.md/setup.json reference ANTHROPIC_API_KEY (required per setup.json) and optional Browserbase keys (BROWSERBASE_API_KEY and BROWSERBASE_PROJECT_ID). Those keys are plausible needs (model API for AI-driven element selection, remote browser provider), but the registry should have declared them. Also the tool uses and preserves a local Chrome profile directory and download directory, which means it will read/write potentially sensitive local data (cookies, session tokens, downloaded files).
Persistence & Privilege
The skill does not force-enable itself (always:false), but its workflow explicitly creates and reuses persistent state: .chrome-profile (session cookies), ./agent/downloads (downloaded files), and ./agent/browser_screenshots (images). It also launches Chrome with remote debugging on port 9222 (CDP) which, if accessible, could be used by other local processes to control the browser. These behaviors have privacy and persistence implications and should be made explicit to users.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install openclaw-browser-automation-1-0-1 - After installation, invoke the skill by name or use
/openclaw-browser-automation-1-0-1 - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of openclaw-browser: automate web browser interactions via CLI using natural language commands.
- Supports both local Chrome and remote Browserbase environments, with automatic mode selection based on configuration.
- Provides commands to navigate, act, extract data, observe elements, take screenshots, and close the browser.
- No user prompts required for environment selection; determined by existing API keys or local setup.
- Includes best practices, troubleshooting tips, and links to detailed documentation.
Metadata
Frequently Asked Questions
What is Openclaw Browser Automation 1.0.1?
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... It is an AI Agent Skill for Claude Code / OpenClaw, with 169 downloads so far.
How do I install Openclaw Browser Automation 1.0.1?
Run "/install openclaw-browser-automation-1-0-1" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Openclaw Browser Automation 1.0.1 free?
Yes, Openclaw Browser Automation 1.0.1 is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Openclaw Browser Automation 1.0.1 support?
Openclaw Browser Automation 1.0.1 is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Openclaw Browser Automation 1.0.1?
It is built and maintained by q262045312-ui (@q262045312-ui); the current version is v1.0.0.
More Skills