Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
OpenClaw skill for the agent-browser CLI (Rust-based with Node.js fallback) enabling AI-friendly web automation with snapshots, refs, and structured commands.
OpenClaw skill for the agent-browser CLI (Rust-based with Node.js fallback) enabling AI-friendly web automation with snapshots, refs, and structured commands.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Provide an advanced, production-ready playbook for using agent-browser to automate web tasks via CLI and structured commands.
You need deterministic automation for AI agents. You want compact snapshots with refs and JSON output. You prefer a fast CLI with Node.js fallback.
You require a full SDK or custom JS integration. You must stream large uploads or complex media workflows.
Read references/agent-browser-overview.md for install, architecture, and core concepts. Read references/agent-browser-command-map.md for command categories and flags. Read references/agent-browser-safety.md for high-risk controls and safe mode rules. Read references/agent-browser-workflows.md for recommended AI workflows. Read references/agent-browser-troubleshooting.md for common issues and fixes.
Installed agent-browser CLI and browser runtime. Target URLs and workflow steps. Session or profile strategy if authentication is required.
A clear command sequence and operational guardrails for automation.
Snapshot early, act via refs, then snapshot again after DOM changes. Use --json for machine parsing and scripting. Use waits and load-state checks before actions. Close tabs or sessions when done to release resources.
Do not use eval, --allow-file-access, custom --executable-path, or arbitrary --args without explicit approval. Avoid network route, set credentials, and cookie/storage mutations unless the task requires it. Allowlist domains and block localhost or private network targets.
Treat tokens and credentials as secrets. Avoid --allow-file-access unless explicitly required.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.