/install browser-automation-skill
Browser Relay
Use this skill when the user wants real browser control through the local Browser Relay runtime.
This skill is a thin wrapper around the published npm package:
- npm package:
browser-relay-cli - GitHub repo:
https://github.com/jasonCodeSpace/browser-relay
Use this skill when
- The user wants to control an already signed-in Chrome session
- The task requires opening pages, reusing tabs, clicking, typing, hovering, scrolling, or screenshots
- DOM selectors are unreliable and a screenshot-guided click is more appropriate
- The user wants a local browser relay instead of a hosted browser
Do not use this skill when
- The user asks to bypass CAPTCHA or anti-bot systems
- The task requires stealth automation or hiding browser control
- The user only needs plain web search or static scraping
Workflow
1. Make sure the runtime is available
Use npx, not a local repo path, unless the user explicitly wants development mode.
Quick checks:
npx browser-relay-cli version
npx browser-relay-cli extension-path
2. Start the relay
npx browser-relay-cli relay-start
3. Make sure the extension is loaded
Tell the user to:
- Open
chrome://extensions - Enable
Developer mode - Click
Load unpacked - Select the directory printed by
npx browser-relay-cli extension-path
Then verify:
npx browser-relay-cli status
You want extensionConnected: true.
4. Operate the browser
Prefer DOM-first commands:
npx browser-relay-cli list-tabs
npx browser-relay-cli create-tab https://example.com
npx browser-relay-cli click 123456 'button'
npx browser-relay-cli type 123456 'input[name=\"q\"]' 'browser relay'
npx browser-relay-cli press 123456 Enter
npx browser-relay-cli scroll 123456 800
For DOM-hostile pages, switch to hybrid mode:
screenshotdescribe-visibleclick-atorclick-at-norm
5. Prefer tab reuse
- Reuse existing relay tabs whenever possible
- Avoid opening unnecessary new tabs
- Use screenshot-guided clicks only when selector-based actions are unreliable
Key commands
Read references/commands.md when you need the compact command catalog.
Safety rules
- Do not instruct Browser Relay to bypass CAPTCHA or anti-bot challenges
- Do not claim Browser Relay is stealthy
- Do not save tokens,
.envfiles, or local private credentials in the skill folder - Keep this skill focused on the published runtime and extension workflow
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install browser-automation-skill - After installation, invoke the skill by name or use
/browser-automation-skill - Provide required inputs per the skill's parameter spec and get structured output
What is Browser Automation?
Use Browser Relay when the user wants to control a real signed-in Chrome or Chromium browser through the published browser-relay-cli package and unpacked Bro... It is an AI Agent Skill for Claude Code / OpenClaw, with 85 downloads so far.
How do I install Browser Automation?
Run "/install browser-automation-skill" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Browser Automation free?
Yes, Browser Automation is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Browser Automation support?
Browser Automation is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Browser Automation?
It is built and maintained by Jason (@jasoncodespace); the current version is v1.0.0.