Security audit
Security checks for vulnerabilities and agentic risk
The booking queries fit the stated purpose, but missing-tool setup tells the agent to run unverified downloaded code without a separate approval step.
Review setup before enabling this skill. Install a verified CLI release yourself and require approval for further installation steps. Consider OOMOL's access to the connected account and its documented agent-skill synchronization. The bundled queries are reads, but the remote installers were unavailable for inspection; no malicious payload was established.
The supplied code performs only a remote installer invocation, not SimplyBook.me search or read operations. No connection between this installer and the declared functionality is established. The downloaded script's contents are not supplied, so its specific effects cannot be determined.
Piping a remotely fetched installer directly into Bash executes whatever the endpoint returns with the agent's local privileges, without a pinned version or independent integrity verification. Compromise of the distribution endpoint could therefore expose local files or credentials and modify the environment; HTTPS and conditional setup do not eliminate that supply-chain risk. The PowerShell installation example has the same execution pattern.
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 software by executing downloaded scripts without first obtaining approval for local system changes. Running only when the CLI is missing reduces exposure, but a request to read booking information does not itself authorize installing software or executing a remote installer.
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