Security audit
Security checks for vulnerabilities and agentic risk
The conversion workflow is coherent, but its automatic setup executes an unverified remote installer and under-discloses broader changes the CLI can make.
Review and install the CLI separately before enabling this skill, including its automatic agent-skill synchronization settings. The remote installers and hosted connector implementation were not verified. Use a PDF you intend to process through OOMOL and ConvertAPI, and consider service charges. The review found no artifact-backed evidence of malicious intent.
The supplied command executes a remote installer from a different service without demonstrating any ConvertAPI functionality. This is a materially different action from the declared searching and reading purpose. The installer contents are not supplied, so its subsequent behavior cannot be determined.
The supplied code only initiates a CLI login; it does not perform any identifiable ConvertAPI operation. Authentication could be a supporting implementation detail, but nothing in this chunk establishes that oo authenticates to ConvertAPI or supports the declared functionality.
Piping a live HTTPS response directly into bash executes installer content without a pinned version or independently verified integrity. A compromised distribution endpoint or altered installer could execute arbitrary code with the invoking user's privileges; HTTPS alone does not protect against compromise of the publisher's infrastructure.
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 conversion action creates a derived document and temporary download URLs, but the blanket rule classifies untagged actions as reads that are safe to execute directly. Conversion can also consume service credits and involve third-party document processing, so this classification can bypass the skill's own confirmation requirement for consequential operations.
When the CLI is missing, the setup instructions direct execution of downloaded shell or PowerShell code without explicitly obtaining approval for software installation. If followed, this can modify the local environment and execute code with the invoking account's privileges; the conditional setup trigger limits exposure but does not establish 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