Security audit
Security checks for vulnerabilities and agentic risk
The Notion features are clearly described, but setup can execute changing remote software without asking for installation approval.
Review CLI setup separately before allowing it to run. Prefer a verified fixed release and check whether automatic installation of other agent skills is enabled. Limit the Notion connection to needed content and retain the required confirmations for changes. The supplied instructions show a setup-control concern, but no evidence of malicious intent; downloaded software and hosted behavior remain unverified.
The supplied command executes an Oomol installer rather than performing a Notion operation. Although installation can be a supporting implementation detail, the supplied content establishes no connection between this installer and the declared Notion functionality. The downloaded script is not provided, so its further behavior cannot be determined.
Piping a live installer directly into Bash executes remotely supplied code with the agent process's local privileges, without a pinned version or independent integrity verification. A compromised distribution endpoint could therefore compromise local files and accessible credentials; the legitimate vendor domain and conditional setup reduce suspicion of malicious intent but do not remove this supply-chain risk. The PowerShell installation example has the same underlying issue.
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 instructs the agent to install local software without first explaining the system changes or obtaining approval. Its missing-CLI condition limits exposure, but confirmation requirements elsewhere cover Notion mutations rather than local installation, leaving an authorization 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