Neo — Web App API Discovery

Browse websites, read web pages, interact with web apps, call website APIs, and automate web tasks. Use Neo when: user asks to check a website, read a web pa...

The skill appears to do what it says (turn a browser into an AI-callable API) but it will access very sensitive local data: Chrome profiles, cookies, active sessions, and full network captures. Before installing or running it: 1) inspect the npm package source (repository, maintainers, recent releases) to ensure trustworthiness; 2) prefer installing and running in a disposable or sandboxed environment (separate user account, VM, or container) rather than on a machine with important logins; 3) avoid using it while logged into sensitive accounts you don't want accessible; 4) treat exported cookies/captures as credentials — store/delete them securely; 5) run 'neo doctor' and review prompts before allowing it to launch Chrome; and 6) if you need a lower-privilege alternative, use read-only scraping tools that do not reuse your real browser session. Because this evaluation is based solely on the instruction file and registry metadata (the npm package itself was not inspected), confidence is medium — inspect the package source to raise confidence.

Type: OpenClaw Skill Name: neo-browser Version: 2.1.0 The 'neo-browser' skill (version 2.1.0) provides an interface for the '@4ier/neo' CLI, which grants an AI agent extensive control over the user's browser via CDP. Key high-risk capabilities include exporting full browser cookies (`neo cookies export`), capturing raw network traffic (`neo capture`), and managing Chrome profiles. While these features are functionally aligned with the stated goal of web automation and API discovery, the inclusion of explicit commands to extract session data and execute arbitrary JavaScript (`neo eval`) creates a significant surface for credential theft and session hijacking. No direct evidence of malicious exfiltration was found in the instructions, but the toolset is inherently high-risk.