Security audit
Security checks for vulnerabilities and agentic risk
The ExhibitDay workflow is appropriately scoped, but its setup can execute unverified downloaded code without a separate approval step.
Review and install a verified CLI release yourself before enabling automatic setup, including its behavior for installing other agent skills. OOMOL intermediates ExhibitDay requests and manages the connected credential. Keep the required confirmations for changes and deletions. The remote installers and hosted connector implementation were not verified.
The supplied command performs remote installer execution, not ExhibitDay data management. Nothing in the supplied chunk establishes that this installer is a supporting dependency for ExhibitDay, so its behavior is materially outside the declared purpose. The downloaded script's contents and downstream effects are not visible and cannot be determined from this chunk.
The command pipes a remotely fetched, unpinned script directly into Bash without verifying its integrity or reviewing it; the PowerShell alternative has the same weakness. If the distribution endpoint or delivery infrastructure is compromised, attacker-controlled code could run with the invoking user's permissions, potentially exposing local secrets or modifying files; HTTPS and the conditional setup trigger do not eliminate that risk.
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 without requiring approval or explaining that installation executes code and can change the local environment. Limiting this to a missing CLI reduces exposure, but the skill's confirmation requirements for ExhibitDay writes do not explicitly cover local installation.
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
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## Resources
- ExhibitDay homepage: https://www.exhibitday.com
- API documentation: https://api.exhibitday.com/