Security audit
Security checks for vulnerabilities and agentic risk
If its required CLI is missing, this skill directs your agent to execute a downloaded installer without first asking for approval.
Review and install the CLI yourself before use, and require approval for setup changes. Review its automatic skill synchronization settings. Connecting Documenso also entrusts OOMOL with account credentials and access to requested data. The concerns warrant review, but the artifact does not establish malicious intent.
The supplied command performs remote installer execution, not Documenso data retrieval. No connection between this installation and the declared Documenso functionality is shown, so it cannot be established as a supporting implementation detail. The downloaded script's contents and further effects are not available for assessment.
Piping a remotely fetched script directly into Bash executes its contents without a review step, version pinning, or independent integrity verification. If the installer endpoint or publishing pipeline is compromised, the script can execute arbitrary code with the invoking user's permissions; HTTPS does not protect against a compromised publisher. The missing-CLI condition limits exposure but does not remove this supply-chain risk, and the PowerShell alternative has the same 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 directs the agent to install software after a missing-command error without first explaining system changes or obtaining installation approval. Although conditional and relevant to the workflow, installing software exceeds the expected scope of searching and reading Documenso data.
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