Security audit
Security checks for vulnerabilities and agentic risk
The Workiom workflow is coherent, but its automatic setup executes downloaded code without separate approval or clearly explaining broader local changes.
Install and verify a fixed CLI release separately before using this skill, and review or disable its automatic agent-skill synchronization. Connect only the Workiom access you need through OOMOL and retain the required approval for writes. The remote installers and downstream binaries were not verified; the artifacts do not establish malicious intent.
The supplied code performs remote software installation rather than the declared Workiom data operations. No visible code establishes that this installer is a supporting dependency for Workiom functionality. The fetched script's contents and further effects cannot be determined from this chunk.
Piping an HTTPS download directly into bash executes mutable remote content with the agent process's local privileges, without a pinned version or independent integrity verification. Compromise of the distribution endpoint or release pipeline could expose local credentials and files or enable persistent modification; 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 fallback directs the agent to install software by executing downloaded shell or PowerShell code without explicitly obtaining approval for local system changes. Restricting setup to a missing-CLI error reduces exposure, but a Workiom data request does not necessarily authorize installing software or executing remote code.
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