Super Browser

Browser automation through the published `@pzeda/super-browser` package and its `super-browser` CLI against a real local Chrome session. Use when the task ne...

This skill appears to do what it claims, but installing and running a third-party npm CLI and connecting it to your real Chrome session can expose sensitive data. Before using it: (1) review the npm package page and source repository for @pzeda/super-browser and confirm the author and recent activity; (2) prefer `npx` or a local (non-global) install to avoid modifying global state; (3) run the package in an isolated environment (separate user/profile, VM, or container) if possible; (4) avoid pointing it at your primary Chrome profile — either launch Chrome with a dedicated profile or deny remote debugging access to profiles with sensitive logins; (5) restrict CDP to localhost and do not open port 9222 to the network; (6) inspect package install scripts and runtime behavior (or request checksums/signatures) if you must install globally. If you cannot audit the package, treat it as untrusted software and limit its access accordingly.

Type: OpenClaw Skill Name: pzeda-super-browser Version: 0.0.2 The skill provides extensive browser automation capabilities by wrapping the `@pzeda/super-browser` npm package, including the ability to reuse existing Chrome login sessions, take screenshots, and upload files. While these features are aligned with the stated purpose in SKILL.md, the broad access to the user's local browser environment, network traffic, and file system represents a significant security risk. The instructions to perform a global npm installation and the high-privilege nature of the browser control primitives warrant a suspicious classification despite the lack of explicit malicious intent.