Security audit
Security checks for vulnerabilities and agentic risk
The Knack workflow has clear data-change safeguards, but its setup can execute unverified remote code without an installation approval step.
Review setup before enabling this skill. Install the CLI through a separately reviewed process and check whether you want its bundled-skill synchronization. Connect only the needed Knack account and retain approval for every write or deletion. The remote installer payload was unavailable for verification; no malicious intent was established.
The supplied code installs software from Oomol, with no demonstrated connection to Knack functionality. This is an undeclared capability involving an inconsistent external resource, rather than an established supporting implementation detail. The remote script's contents and any further actions are not available for assessment.
Piping a remotely fetched installer directly into Bash executes mutable network-delivered code with the agent's local privileges, without a review or integrity-verification step. HTTPS protects transport but does not prevent a compromised distribution endpoint from serving malicious code; the missing-CLI condition limits exposure but not the potential impact, and the PowerShell example has the same weakness.
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 by executing third-party scripts without first obtaining explicit approval for local system changes. Although this happens only when the CLI is missing, authorization to operate on Knack data does not necessarily authorize installing software on the host.
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