Security audit
Security checks for vulnerabilities and agentic risk
The SmartSuite workflow has clear approval rules, but its setup instructions can execute downloaded software without a separate installation approval.
Review the CLI installation before enabling this skill. Prefer installing a verified release yourself and require approval for subsequent installation changes. OOMOL mediates access to your connected SmartSuite account, and its CLI may also install other agent skills. The bundled SmartSuite instructions require approval for record changes and deletions; external installer behavior remains unverified.
The supplied command performs remote installer execution rather than SmartSuite data operations. Nothing in the chunk establishes this installer as a supporting dependency for the declared purpose. The downloaded script is not supplied, so its subsequent actions and safety cannot be determined.
Piping an HTTPS response directly into bash executes whatever the remote endpoint serves, without a pinned version, signature check, or opportunity for review. Compromise of the installer endpoint or its publishing pipeline could lead to local code execution, exposing files and credentials accessible to the agent; HTTPS alone does not protect against a compromised publisher.
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 setup instructions direct the agent to execute remote installer code without requiring informed approval or integrity verification. Although this is a legitimate prerequisite and runs only when the CLI is missing, it can turn a routine SmartSuite request into local software installation with the agent process's permissions.
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