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...
Security Analysis
high confidenceThe skill's code and instructions are consistent with its stated purpose (attaching a Chrome relay extension on macOS); it performs intrusive but explained actions (killing Chrome, patching Chrome preferences, taking a debug screenshot) which are justified by the described workflow.
The name/description match the included script and instructions: the skill locates and clicks the OpenClaw Relay extension icon via the macOS accessibility tree so the browser(profile="chrome") relay can be attached. Required tools (Peekaboo) and the node Accessibility permission are explained and reasonably related to the task.
The instructions and script do several system-level things that are explicitly documented: kill Chrome (pkill -9), patch ~/Library/Application Support/Google/Chrome/Default/Preferences to suppress restore dialogs, open and maximize Chrome, inspect the accessibility tree, click the extension icon, and save a debug screenshot to ~/.openclaw/media. All of these are within the skill's stated goal, but they are intrusive operations that affect the user's Chrome state and could cause data loss if unsaved tabs/windows exist.
This is an instruction-only skill with a shell script; no install spec is run by the skill itself. The README suggests installing Peekaboo via a Homebrew tap (steipete/tap/peekaboo). Using a third-party Homebrew tap is an explicit user instruction and not executed automatically by the skill; users should audit that tap before installing, but the install suggestion is coherent with the documented dependency.
The skill requests no secrets or environment variables. It does require granting Accessibility permission to the node binary (to allow Peekaboo to send UI events), and it reads/writes the Chrome Preferences JSON and writes diagnostic screenshots to ~/.openclaw/media. Those accesses are proportionate to the task but touch sensitive browser state (Preferences) and user files, so users should be aware and back up Chrome state if needed.
The skill is not always-enabled and does not request persistent platform privileges. It does not modify other skills or system configurations beyond the documented per-user Chrome Preferences patch and writing to ~/.openclaw/media; those changes are self-contained and described in the SKILL.md.
Guidance
This skill appears to do exactly what it says, but it performs intrusive actions that you should accept knowingly: it will kill any running Chrome processes (pkill -9), modify your Chrome Default Preferences file to suppress restore prompts, and write debug screenshots to ~/.openclaw/media. Before using it: (1) back up your Chrome profile (~/Library/Application Support/Google/Chrome) if you have unsaved tabs or important state, (2) inspect the brew tap/package before installing Peekaboo, (3) confirm you are comfortable granting Accessibility permission to your node binary (required so Peekaboo can send clicks), (4) ensure the OpenClaw extension is loaded and pinned at ~/.openclaw/browser/chrome-extension as documented, and (5) run the script manually the first time so you can observe its behavior (it is not auto-installed). If any of these operations are unacceptable (killing Chrome or modifying preferences), do not install or run the skill.
Latest Release
v1.0.0
What it does: When OpenClaw needs to control your real Chrome browser, it requires the OpenClaw Browser Relay extension to be active on a tab. Without a reliable attach method, agents fall back to pixel-coordinate clicking and screenshot-based targeting — both of which break across screen sizes and are expensive in tokens. This skill solves that with a single script that: 1) Launches Chrome to a known safe page Uses Peekaboo (macOS accessibility API) to find the extension icon by its description — not coordinates 2) Clicks it to attach 3) Confirms the relay is live before returning The result is a consistent, reproducible attach sequence that works regardless of screen resolution, window size, or where the icon happens to be in the toolbar. Use this skill as the first step in any workflow that needs browser(profile="chrome").
Popular Skills
Published by @i-am-rad on ClawHub
