Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Chrome Extension Relay Helper - Mac
Attach the OpenClaw Browser Relay Chrome extension to a live tab so the browser tool (profile="chrome") works. Use this skill before any browser automation t...
skill openclawclawhub Free
Attach the OpenClaw Browser Relay Chrome extension to a live tab so the browser tool (profile="chrome") works. Use this skill before any browser automation t...
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, scripts/attach.sh
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
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.
Upgrade existing
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.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- i-am-rad
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
OpenClaw Chrome Relay Helper - Mac
Automates attaching the OpenClaw Browser Relay Chrome extension to a live tab on macOS. Once attached, the browser(profile="chrome") tool works โ you can navigate, snapshot, click, and scrape using your real Chrome session. macOS only. Requires Peekaboo (macOS UI automation CLI).
Quickstart
bash <skill-dir>/scripts/attach.sh Outputs one of: ALREADY_ATTACHED โ already connected, nothing to do ATTACHED โ freshly connected, ready to use FAILED: <reason> โ check ~/.openclaw/media/relay-attach-fail.png for a debug screenshot Then navigate and automate: browser(action="navigate", profile="chrome", targetUrl="https://example.com") browser(action="snapshot", profile="chrome", compact=True) # read page content Typical wall time: ~29s on a clean launch.
1. Peekaboo (macOS UI automation CLI)
brew install steipete/tap/peekaboo Peekaboo reads Chrome's accessibility tree to find the extension icon by description โ no pixel coordinates needed.
2. Accessibility permission for node
Go to System Settings โ Privacy & Security โ Accessibility and add your node binary. Without this, Peekaboo cannot send click events. Find your node path with: which node
3. openclaw.json browser profile
Add this to your ~/.openclaw/openclaw.json: "browser": { "profiles": { "chrome": { "cdpUrl": "http://127.0.0.1:18792", "driver": "extension", "color": "#FF5A36" } } } Restart the gateway after editing: openclaw gateway restart
4. Extension loaded and pinned in Chrome
The OpenClaw Browser Relay extension must be loaded as an unpacked extension in Chrome. It's included with OpenClaw at: ~/.openclaw/browser/chrome-extension Load it via chrome://extensions โ Developer mode ON โ Load unpacked. The extension must also be pinned to the toolbar. The script finds the icon via Chrome's accessibility tree, which only exposes toolbar-pinned extensions โ not icons hidden inside the Extensions panel. To pin: click the puzzle-piece icon โ click the pin icon next to "OpenClaw Browser Relay".
How it works
The script finds the extension icon using Chrome's accessibility tree โ not pixel coordinates. The icon's description changes based on state: Detached: "OpenClaw Browser Relay (click to attach/detach)" Attached: "OpenClaw Browser Relay: attached (click to detach)" Peekaboo scans for a pop-up button element whose description starts with "OpenClaw Browser Relay", determines state, and clicks to attach if needed. Retries up to 8ร (every 2s) to handle slow Chrome startup. Window maximize is required before scanning โ Chrome's toolbar icons are not visible in the accessibility tree on a small or default-sized window.
What the script does (step by step)
Fast path โ if Chrome is running and badge already shows "attached", exits immediately (~2s) Kill any running Chrome instance Patch ~/Library/Application Support/Google/Chrome/Default/Preferences to suppress the "Restore Pages?" dialog on relaunch Open Chrome to https://info.cern.ch/ โ the world's first website, a 428-byte static HTML file with zero anti-bot tech, JS, cookies, or Cloudflare Maximize the window via Peekaboo (required for toolbar visibility) Scan accessibility tree for the extension icon (retries up to 8ร, 2s apart) Click the icon to attach Verify state changed to "attached" before returning
Known pitfalls
ApproachWhy it doesn't workHardcoded pixel coordinatesBreaks at any screen size other than what they were measured onAppleScript keystroke with Ctrl+ShiftModifier keys are silently dropped โ only the bare key firesChrome extension keyboard shortcutThe extension manifest has no commands โ shortcuts don't trigger attachVision model to locate iconNot reliable enough for toolbar UI at any resolutionSkipping window maximizeToolbar icons don't appear in the accessibility tree on a small windowExtension not pinned to toolbarUnpinned extensions are hidden inside the Extensions panel โ not visible in the accessibility treeWrong profile name or port in configbrowser(profile="chrome") requires the profile named exactly chrome pointing to port 18792
Token efficiency tips
# โ Use snapshot for reading page content (~3k tokens) browser(action="snapshot", profile="chrome", compact=True) # โ Avoid screenshot + vision for UI element detection # โ Unreliable for toolbar/coordinate identification # โ 10โ50x more expensive than snapshot
Integration pattern
Any skill that needs Chrome relay should call this first: # 1. Attach bash <path-to-chrome-relay>/scripts/attach.sh # 2. Navigate browser(action="navigate", profile="chrome", targetUrl="https://target.com") # 3. Automate browser(action="snapshot", profile="chrome", compact=True) browser(action="act", profile="chrome", request={kind: "click", ref: "..."})
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs1 Scripts
- SKILL.md
- scripts/attach.sh