Security audit
Security checks for vulnerabilities and agentic risk
Account changes require approval, but the CLI setup can introduce persistent changes to your agents that the skill does not explain.
Review the CLI installation separately before proceeding, including its automatic installation of additional agent skills. If you only want this connector, disable startup skill synchronization using the publisher's documented OO_SKILLS_SYNC_DISABLED setting before invoking the CLI: [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables). Use limited account permissions and retain the required approvals for changes. The complete bundled artifact was inspected, but downloaded installers and hosted connector behavior remain unverified.
The supplied code performs remote installer execution rather than any visible Roam SCIM operation. Although installation can be a supporting implementation detail, nothing in this chunk establishes that the Oomol installer supports the declared functionality. The remote script's contents and further effects are not available for assessment.
Piping an HTTPS download directly into bash executes mutable remote content without verifying its integrity or allowing inspection first. The vendor-hosted URL and conditional setup context support a legitimate intent, but compromise of the hosting or release infrastructure could lead to arbitrary code execution with the user's privileges.
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 fallback setup directs execution of downloaded shell or PowerShell code without an integrity check or explicit approval for installing software. Although this is a legitimate dependency setup step and only occurs when the CLI is absent, a compromised installer could execute arbitrary code with the invoking user's permissions; server-side API credential handling does not protect local files or credentials.
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