Security audit
Security checks for vulnerabilities and agentic risk
If a required tool is missing, the skill tells your agent to execute downloaded installation code without asking first.
Review setup before use. Preinstall a verified CLI release and prevent the agent from automatically running remote installers. Check whether bundled skill synchronization will change other agent configurations. Connect only the Kontent.ai environment and read permissions you need, and understand that access runs through OOMOL. The listed data operations fit the purpose; the Review verdict concerns setup control and persistent side effects, with no evidence establishing malicious intent.
The supplied command executes an external installation script and contains no Kontent.ai search or read operations. Nothing supplied establishes that this installer supports the declared purpose, and remote script execution introduces behavior outside the stated data-access function. The script's downstream actions cannot be determined from this chunk.
The command streams a mutable remote script directly into Bash without a pinned version or independent integrity verification; the PowerShell alternative has the same underlying risk. Compromise of the distribution endpoint could execute arbitrary code with the agent's local permissions, exposing accessible files and credentials. HTTPS and the legitimate dependency context reduce suspicion of malicious intent but do not eliminate this supply-chain risk.
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
When the CLI is missing, the skill directs the agent to install it without first obtaining approval for local software installation and third-party code execution. This crosses the boundary of a request to read Kontent.ai data, although the explicit missing-command condition limits when the behavior is triggered.
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