Security audit
Security checks for vulnerabilities and agentic risk
The Storyblok reading workflow is coherent, but its fallback setup executes unverified internet installers without requiring user approval.
Review and explicitly approve CLI installation separately before allowing the agent to perform setup. Prefer a reviewed, version-pinned installation with integrity verification. Connect only the intended Storyblok account with appropriate read permissions, and understand that OOMOL mediates access. The external installer and CLI were not bundled for inspection.
The supplied command performs remote script execution, not Storyblok searching or reading. Nothing in the code establishes that installing the Oomol CLI is a supporting requirement for Storyblok access. The downloaded script's contents are not supplied, so its further behavior cannot be assessed.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Available actions
- `get_space` — Retrieve metadata for the Storyblok space associated with the access token.
- `get_story` — Retrieve one Storyblok story by full slug, numeric ID, or UUID.
- `list_datasource_entries` — List Storyblok datasource entries, optionally filtered by datasource and dimension.
- `list_datasources` — List Storyblok datasources with pagination.
Piping a live HTTPS response directly into Bash executes remote code without independently verifying its integrity or reviewing its contents; the PowerShell alternative has the same weakness. Compromise of the installer distribution infrastructure could therefore lead to arbitrary code execution with the agent's local permissions. The apparent vendor-domain alignment and conditional setup make malicious intent less likely, but do not remove the supply-chain 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
When the CLI is missing, the skill directs the agent to execute an installer without first obtaining approval for local software installation. A request to read Storyblok data does not necessarily authorize local system changes, and the downloaded script could modify files or execute other commands with the agent's permissions. Restricting setup to a missing-command error reduces exposure but does not establish 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