Security audit
Security checks for vulnerabilities and agentic risk
The research functions fit their purpose, but fallback setup executes unverified remote code without requiring separate user approval.
Review setup before enabling this skill. Install a verified CLI release yourself, check its automatic skill-sync settings, and require approval for additional installation. Searches use your OOMOL-connected account and may consume credit. The remote installers and hosted service implementation were not verified; the concern is uncontrolled setup, not evidence of malicious intent.
The supplied command performs remote software installation, not Web of Science searching or reading. Although dependency installation can be a supporting implementation detail, the supplied chunk establishes no connection between this installer and the declared functionality. The remote script's contents are unavailable, so its further actions cannot be determined.
Piping an HTTPS response directly into Bash executes mutable remote content without checking a pinned version, signature, or trusted digest. If the installation endpoint or its delivery infrastructure is compromised, the script could execute arbitrary commands with the agent process's permissions; the legitimate dependency-installation context does not eliminate this 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
The missing-CLI fallback directs installation through downloaded shell or PowerShell scripts without requiring informed approval for executing external code and changing the local environment. Its conditional placement reduces exposure, and the declared Bash tool restriction may prevent execution in a strictly enforcing host, but a data-search request should not implicitly authorize software 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