Security audit
Security checks for vulnerabilities and agentic risk
The Teamtailor reads are appropriately scoped, but setup can execute downloaded code and introduce other agent skills without explaining or seeking approval for those changes.
Review and approve CLI installation separately before allowing setup to proceed. Verify the installer and chosen release, and decide whether to permit its additional agent skills. Vendor documentation provides OO_SKILLS_SYNC_DISABLED=1 to disable startup skill synchronization. Connect Teamtailor with only the permissions needed and understand that OOMOL mediates these requests. Exact installer behavior could not be verified; no malicious payload was identified in the supplied skill.
The supplied command runs an external installation script, while the description declares Teamtailor data access. Nothing in the supplied code establishes that this installer supports the declared functionality. The remote script's contents and resulting system changes cannot be determined from this chunk.
The command pipes a remotely fetched script directly into bash without version pinning or integrity verification; the PowerShell alternative uses the same fetch-and-execute pattern. Compromise of the distribution endpoint could therefore execute attacker-controlled code with the user's privileges, although the vendor-related domain and missing-CLI prerequisite provide no evidence of malicious intent.
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 setup instructs the agent to execute downloaded shell or PowerShell code without first explaining the system changes or obtaining explicit installation approval. Triggering installation only when the CLI is missing reduces exposure, but a read-oriented Teamtailor request can still lead to arbitrary code execution with the invoking user's privileges.
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