Stable Browser
WarnAudited by ClawScan on May 10, 2026.
Overview
The skill is coherent and not clearly malicious, but it sets up a persistent CDP-controlled Chrome profile that can stay logged into accounts and enable broad browser/account actions.
Install only if you intentionally want OpenClaw to control a dedicated Chrome profile through CDP. Use a separate profile or low-risk accounts, avoid logging into sensitive services unless needed, require confirmation for posting or form submission, and remove the LaunchAgent/profile when you no longer want persistent browser control.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If used with logged-in sites, the agent could navigate, fill forms, or post content as the user unless the user sets separate limits.
The skill intentionally enables broad browser automation, including actions that can submit forms or publish content, without artifact-level boundaries or approval guidance for high-impact actions.
stable headless/headed browser control for web scraping, form filling, social media posting, or any browser automation task
Use this only for explicit browser tasks, require confirmation before posting/submitting/changing account data, and avoid giving the profile access to sensitive accounts unless necessary.
Any agent or local process able to use the configured CDP browser could act through the logged-in sessions while the browser is running.
The dedicated Chrome profile is meant to retain authenticated sessions for potentially high-value accounts, effectively delegating those account privileges to CDP browser automation.
Log into sites once, stays logged in ... First run: Log into any sites you need (Google, GitHub, X, LinkedIn, etc.)
Use a separate low-privilege browser profile or test accounts, log out of sensitive sites when done, and delete ~/.chrome-debug-profile if you no longer want those sessions available.
A CDP-controllable browser may remain available across logins, including with saved website sessions, unless the user removes the LaunchAgent or closes the setup.
The script creates a macOS LaunchAgent that starts the CDP-enabled Chrome at login and restarts it after crashes, extending the automation surface beyond the immediate setup task.
<key>RunAtLoad</key>\n <true/>\n <key>KeepAlive</key>\n <dict>\n <key>Crashed</key>\n <true/>
Disable or remove ~/Library/LaunchAgents/com.openclaw.chrome-cdp.plist when persistent browser automation is not needed, and document a cleanup step before installing.
Users have less external provenance to rely on before running a script that changes local browser and OpenClaw configuration.
The skill includes a setup script that users are instructed to run, but the registry information provides no source/homepage provenance and no install spec declaring the setup behavior.
Source: unknown; Homepage: none; No install spec — this is an instruction-only skill; Code file presence: scripts/setup-cdp.sh
Inspect the included script before running it, verify it matches the reviewed contents, and prefer skills with clear source provenance for environment-modifying setup.