SOLO.ro cli

Monitor and interact with SOLO.ro accounting platform via CLI or TUI (summary, revenues, expenses, queue, e-factura, company). Use when a user asks to check their accounting data, view invoices, expenses, or e-factura documents, or translate a task into safe solo-cli commands.

This skill appears to honestly document how to use a third-party solo-cli tool, but take precautions before installing or providing credentials: 1) Verify the solo-cli binary provenance — prefer an official project page or GitHub releases and check checksums; be cautious about third-party Homebrew taps. 2) Avoid storing plaintext passwords in config.json if possible — use OS credential stores, environment-managed secrets, or an API token if the service supports it. 3) Ensure config and cookies files are created with restrictive filesystem permissions (chmod 600). 4) Test using the demo mode first and inspect network calls (or run in a sandbox) before supplying real credentials. 5) If you must use your real account, consider creating a limited/test account with minimal data. If you want a stronger assurance that this is safe, ask the publisher for a signed release URL, checksum, and source repository to review the actual executable's behavior.

Type: OpenClaw Skill Name: solo-cli Version: 1.1.0 The skill instructs the agent to install `solo-cli` from a third-party Homebrew tap (`rursache/tap`) via `brew install rursache/tap/solo-cli` in `SKILL.md`. This introduces a significant supply chain risk, as the integrity and behavior of the `solo-cli` binary from this untrusted source cannot be guaranteed. While the skill's instructions themselves do not explicitly command malicious actions, the act of installing software from an arbitrary third-party tap is a high-risk operation. Additionally, the tool handles sensitive user credentials and session cookies locally, which, combined with the supply chain risk, makes the overall behavior suspicious.