Security audit
Security checks for vulnerabilities and agentic risk
Fairing reads match the stated purpose, but setup can execute unverified remote installers without a clear user approval step.
Review the setup before enabling this skill. Install a verified CLI release yourself and review its automatic skill-synchronization settings. Use a Fairing connection limited to the data needed. The exact installer changes remain unverified; no artifact evidence establishes malicious intent.
The supplied command performs remote script execution, not the declared Fairing data operations. No code establishes that this installer is a necessary supporting dependency for Fairing, so its installation behavior is materially outside the stated purpose. The downloaded script's contents and any further effects are not available for assessment.
Piping an HTTPS download directly into Bash executes mutable remote content with the invoking user's privileges without an inspection or integrity-verification step. If the installer endpoint or its delivery infrastructure is compromised, this can expose local files and credentials or allow persistent system changes; HTTPS alone does not protect against a compromised publisher.
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 setup instructions direct the agent to execute a remote installer without explicitly obtaining approval for local software installation. This expands a Fairing read request into local-system changes and code execution; the missing-CLI condition limits exposure but does not provide user consent.
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