Security audit
Security checks for vulnerabilities and agentic risk
The Weaviate reads fit the stated purpose, but setup executes unverified remote installers and the required CLI has broader effects on installed agent skills.
Review and install a specific CLI release yourself before enabling this skill, and connect only the Weaviate account you intend to expose through OOMOL. Consider disabling automatic skill synchronization with OO_SKILLS_SYNC_DISABLED=1, as documented in the CLI reference. The remote installer and binary remain unverified; the artifacts do not establish malicious intent.
The supplied command executes an installer from a non-Weaviate resource, with no visible connection to searching or reading Weaviate data. This is a materially different operation, not an established supporting implementation detail. The downloaded script's contents and any further effects are not shown.
The supplied chunk performs only a login operation and contains no Weaviate search or read behavior. Authentication could be a supporting implementation detail if tied to Weaviate, but the supplied content establishes no such connection. As provided, its sole behavior is materially different from the declared purpose.
The setup command downloads a mutable remote script and immediately executes it without version pinning, independent integrity verification, or an explicit approval step; the PowerShell alternative has the same weakness. Compromise of the installation endpoint or its release infrastructure could execute arbitrary code with the agent process's permissions, potentially exposing local credentials or modifying files. The missing-CLI prerequisite reduces how often this path is reached but does not make it safe.
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
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