phonebase

Control Android cloud phones via the `pb` CLI. Make sure to use this skill whenever the user mentions logging into apps, installing apps, browsing on a phone...

This skill appears coherent with its stated goal, but keep these practical points in mind before using it: 1) pb and the cloud-phone service can access and display sensitive data (screenshots, app UIs, files). Do not ask the agent to operate on highly sensitive accounts or private data without explicit user consent. 2) The SKILL.md asks you to authenticate yourself via pb login in your browser — never paste credentials into the chat or skill. 3) Because the skill recommends using pb instead of desktop tools, ensure that using a third-party cloud phone is appropriate for the task (some sites treat logins from cloud phones differently or flag them). 4) Verify the pb CLI you install is the official package (check package source, maintainers, and homepage) before running npm install -g. 5) If you need the agent to perform particularly sensitive actions (banking, password resets, access to private files), prefer to run pb commands yourself or review each command the agent proposes before execution. If you want more assurance, ask for the pb CLI project homepage or documentation so you can audit the client/service before use.

Type: OpenClaw Skill Name: phonebase Version: 1.0.0 The phonebase skill bundle provides an interface for controlling Android cloud phones via the `pb` CLI, including high-risk capabilities such as raw shell execution (`pb shell`), file synchronization (`pb push`/`pb pull`), and application management (`pb install`). While these features are aligned with the stated purpose of mobile automation and the `SKILL.md` file includes explicit security guidance for the agent (e.g., warning against prompt injection from remote screen content and advising against constructing shell commands from untrusted input), the broad access to device internals and local filesystem interaction meets the threshold for a suspicious classification.