← Back to Skills Marketplace
Remote Browser Service
by
Vasilii Vazhesov
· GitHub ↗
· v1.0.1
· MIT-0
361
Downloads
0
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install remote-browser-service
Description
Control a remote Chrome browser in Kubernetes via HTTP API. Use for web automation, scraping, form filling, navigation, and page inspection. Exposes accessib...
Usage Guidance
This skill's behavior is coherent for a remote browser API, but exercise caution before installing: the package has no source URL or homepage and the documented service (rb.all-completed.com) is external and unverified. The skill will send Authorization tokens and page content (including anything the agent types) to that host—avoid supplying real credentials or PII. Ask the provider for a homepage, privacy/security docs, and a service SLA. If you must test, use an ephemeral or low-privilege token and non-sensitive test data, and consider disabling autonomous invocation while evaluating. If you cannot verify the service owner, do not provide production credentials.
Capability Analysis
Type: OpenClaw Skill
Name: remote-browser-service
Version: 1.0.1
The skill bundle provides instructions for an AI agent to interact with a remote Chrome browser service hosted at rb.all-completed.com. While the functionality is clearly aligned with the stated purpose of web automation and scraping, the capability to remotely control a browser and the requirement for a secret API key (AC_API_KEY) are high-risk behaviors. The use of an unfamiliar third-party domain and a future-dated publishedAt timestamp (2026) in _meta.json are notable, though no explicit evidence of malicious intent or data exfiltration was found in SKILL.md.
Capability Assessment
Purpose & Capability
The described functionality (remote Chrome control, snapshots, actions) aligns with the HTTP endpoints documented in SKILL.md and the single declared credential (AC_API_KEY). However the registry metadata shown in the UI contains a parsing artifact ('Required env vars: [object Object]'), the package has no homepage or source URL, and the owner is unknown — making provenance unverifiable.
Instruction Scope
The runtime instructions explicitly tell the agent to create sessions and send Authorization tokens and page content to https://rb.all-completed.com. The doc also suggests using access_token in the query string (less secure). The SKILL.md references an environment variable (RBS_BASE_URL) and other behaviors (WebSocket/CDP) that are not declared in metadata. While these network actions are expected for a remote browser service, they mean the agent will transmit navigated page content and any values typed by the agent to a third-party endpoint — this is a privacy/security concern and the SKILL.md does not constrain what is safe to send.
Install Mechanism
Instruction-only skill with no install spec and no code files — nothing will be written or executed locally as part of an installer. This minimizes on-disk risk.
Credentials
Only AC_API_KEY is declared (optional, secret), which is proportionate for an API-backed service. But the SKILL.md refers to RBS_BASE_URL (not declared) and shows ways to supply tokens (Authorization header or ?access_token=) that could expose secrets. The registry metadata parsing issue ('[object Object]') makes it unclear if other env vars are expected. Given the endpoint is from an unknown/unverified source, providing any sensitive API key or session token could be risky.
Persistence & Privilege
always:false and no install means the skill does not request permanent inclusion. disable-model-invocation is false (agent can invoke autonomously) — normal for skills, but combined with the ability to send tokens and page contents to an external host, autonomous invocation increases blast radius. No evidence the skill modifies other skills or system settings.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install remote-browser-service - After installation, invoke the skill by name or use
/remote-browser-service - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
Document VNC interface, framebuffer screenshots, and VNC actions; expand DOM action matrix (tap, hover, select); clarify fill behavior and Chrome vs VNC screenshot strategy; add index and tips for VNC vs DOM.
v1.0.0
Initial release: Remotely control a Chrome browser in Kubernetes via an HTTP API, optimized for web automation and AI agents.
- Provides endpoints for session management, navigation, accessibility snapshots, text extraction, screenshots, and DOM element actions.
- Supports both HTTP and WebSocket (DevTools CDP) workflows.
- Exposes efficient strategies for reading page content, interacting with elements, and verifying visually (via screenshots).
- Ref-based and selector-based element actions supported.
- Includes detailed API usage examples, authentication options, and tips for efficient usage.
- Idle sessions auto-close; stored sessions persist and can be resumed.
Metadata
Frequently Asked Questions
What is Remote Browser Service?
Control a remote Chrome browser in Kubernetes via HTTP API. Use for web automation, scraping, form filling, navigation, and page inspection. Exposes accessib... It is an AI Agent Skill for Claude Code / OpenClaw, with 361 downloads so far.
How do I install Remote Browser Service?
Run "/install remote-browser-service" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Remote Browser Service free?
Yes, Remote Browser Service is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Remote Browser Service support?
Remote Browser Service is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Remote Browser Service?
It is built and maintained by Vasilii Vazhesov (@vasyaod); the current version is v1.0.1.
More Skills