Security audit
Security checks for vulnerabilities and agentic risk
The chat features are clearly scoped, but setup instructs the agent to run unverified downloaded software without separate approval.
Review this skill's automatic setup before use. Install the CLI separately from a verified release and review the Rocket.Chat access granted to OOMOL. Keep the required confirmations for posting, editing, and deleting messages. External installer and connector implementations were not verified; the concern is installation control, with no artifact-backed evidence of malicious intent.
The supplied chunk performs remote installer execution, not Rocket.Chat operations. Nothing in the chunk establishes that this installation is a supporting dependency for the declared functionality. The downloaded script's contents are not supplied, so its additional behavior cannot be determined.
Piping a remotely fetched, unpinned installer directly into Bash executes its contents without prior verification; the PowerShell alternative has the same weakness. A compromised distribution endpoint could execute arbitrary code with the invoking account's permissions, including accessing local files and credentials; HTTPS does not protect against compromise of the publisher or hosting infrastructure.
oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):
curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux
The missing-CLI fallback directs installation without first explaining local system changes or requesting installation-specific approval. This expands a Rocket.Chat task into local software execution; the conditional trigger reduces exposure but does not establish user consent for those effects.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
- **`OOMOL_INSUFFICIENT_CREDIT`** — OOMOL billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.
- **HTTP 402 without `OOMOL_INSUFFICIENT_CREDIT`** — the third-party account itself has no active plan or credit. Report the provider error message as is; do not ask the user to recharge OOMOL.
## Resources