Security audit
Security checks for vulnerabilities and agentic risk
The VTEX read workflow is coherent, but its automatic setup can execute changing remote code without a clear user checkpoint.
Review and install a verified CLI release yourself before enabling this skill, and require approval for later installation changes. Review or disable the CLI's automatic skill synchronization. Confirm the intended OOMOL account and VTEX connection, since OOMOL handles the integration. The listed VTEX operations are reads; the Review verdict concerns installation authority and undisclosed persistent effects. Remote installer behavior remains unverified.
The supplied command installs software by executing externally retrieved code; it does not search or read VTEX data. Nothing in the supplied chunk establishes this installation as a supporting implementation detail for VTEX access. The downloaded script's contents and further effects are not shown.
The command streams a mutable remote script directly into Bash without a pinned version or independent integrity verification; the PowerShell alternative uses the same download-and-execute pattern. A compromised distribution endpoint or malicious installer update could execute arbitrary code with the agent's local privileges, despite the otherwise read-only VTEX workflow.
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 software without explicitly obtaining approval for local system changes. Authorization to read VTEX data does not necessarily authorize running an installer, which can modify files and execute code with the invoking user's privileges; the missing-CLI prerequisite limits exposure but does not remove this consent gap.
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