← Back to Skills Marketplace
111
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install opencli-browser
Description
Use when an agent needs to drive a real Chrome window via opencli — inspect a page, fill forms, click through logged-in flows, or extract data ad-hoc. Covers...
Usage Guidance
Before installing or enabling this skill: 1) Confirm you have the opencli CLI and the required Chrome extension/debug-port configuration — the skill's metadata does not declare these but the runtime docs require them. 2) Treat this skill as powerful: it can read page DOM and network traffic (including session tokens or private form data). Avoid running it while logged into sensitive accounts; prefer a dedicated browser profile or test account. 3) Ask the skill author to update the manifest to declare required binaries/env vars and to document how sensitive data is handled. 4) If you must use it, restrict the agent's ability to invoke the skill autonomously or require user confirmation for each run.
Capability Analysis
Type: OpenClaw Skill
Name: opencli-browser
Version: 1.0.0
The skill bundle provides comprehensive documentation and instructions for an AI agent to use the 'opencli' tool for browser automation. It covers element selection, form interaction, network traffic inspection, and session management with a focus on reliability and token efficiency. There are no indicators of malicious intent, data exfiltration, or prompt injection attacks; the content is entirely aligned with its stated purpose of enabling agentic browser control.
Capability Assessment
Purpose & Capability
The SKILL.md repeatedly instructs the agent to run the opencli CLI and to interact with a running Chrome + extension (e.g., 'opencli doctor', 'opencli browser ...', references to Chrome debug port), but the registry metadata declares no required binaries, no install steps, and no required config paths. A legitimate opencli-based browser driver should at minimum declare opencli (and/or Chrome/Chromium) as a runtime dependency and document any required extension or debug-port config; the absence of those declarations is an incoherence.
Instruction Scope
The instructions themselves stay within the stated purpose (driving a live browser). They explicitly encourage inspecting page state, capturing network requests, running JS eval (read-only), and verifying writes. Those actions necessarily let the agent read page DOM, form contents, and network payloads (potentially including session identifiers or personal data). That is expected for a browser-driving skill, but it means the agent will have access to sensitive user data; the SKILL.md does not provide any additional constraints or warnings about that beyond usage best-practices.
Install Mechanism
This is an instruction-only skill with no install spec or code files. That minimizes disk-write risk. However, because it relies on an external CLI (opencli) and browser/extension setup, the manifest should have declared those runtime requirements.
Credentials
The SKILL.md references environment variables (OPENCLI_WINDOW_FOCUSED, OPENCLI_LIVE) and external browser state, but the declared requires.env is empty. More importantly, the skill's runtime actions (DOM reads, network capture) can expose highly sensitive data — cookies, auth tokens, page content — yet no explicit requirements/consent or warnings are declared in the metadata. The absence of declared binaries/envs and lack of an explicit statement about sensitive data handling is disproportionate to the manifest.
Persistence & Privilege
always:false and default autonomous invocation settings are used (user-invocable, agent may call autonomously). This is the platform default and not itself a problem. Note: because the skill lets the agent control a browser and capture network/page state, autonomous invocation increases risk; exercise caution if you allow the agent to call this skill without manual approval.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install opencli-browser - After installation, invoke the skill by name or use
/opencli-browser - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
opencli-browser 1.0.0 – Initial release
- Enables structured control of a live Chrome window via opencli for agents.
- Provides selector-first target contract, compound form field support, and resilient element references.
- Handles stale reference recovery, structured error reporting, and network/API capture.
- Outputs machine-readable envelopes describing confidence and match quality for every action.
- Includes safety and robustness rules for agents: always inspect first, chain context-aware actions, and verify critical writes.
- Not intended for adapter development—use opencli-adapter-author for that workflow.
Metadata
Frequently Asked Questions
What is opencli-browser?
Use when an agent needs to drive a real Chrome window via opencli — inspect a page, fill forms, click through logged-in flows, or extract data ad-hoc. Covers... It is an AI Agent Skill for Claude Code / OpenClaw, with 111 downloads so far.
How do I install opencli-browser?
Run "/install opencli-browser" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is opencli-browser free?
Yes, opencli-browser is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does opencli-browser support?
opencli-browser is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created opencli-browser?
It is built and maintained by chang (@liberalchang); the current version is v1.0.0.
More Skills