Security audit
Security checks for vulnerabilities and agentic risk
The skill reads HackerRank data as advertised, but its setup instructions can run unverified downloaded code without separate approval.
Review the setup before enabling this skill. Preinstall a verified CLI release, require separate approval for installation, and consider disabling its managed skill synchronization. Connecting HackerRank entrusts OOMOL with access to recruiting data. The concern is insufficiently controlled setup; the inspected artifact does not establish malicious intent. Remote installer contents and server-side behavior remain unverified.
The supplied command performs remote script execution and appears intended to install software, not search or read HackerRank Work data. Nothing in the supplied chunk establishes that this installation is a supporting implementation detail of the declared functionality. The downloaded script's contents and any additional effects are not provided.
The command pipes a mutable remote script directly into Bash without verifying an expected artifact or reviewing its contents; the PowerShell alternative has the same execution pattern. Compromise of the distribution endpoint or release pipeline could execute arbitrary code with the invoking user's privileges, exposing accessible files and credentials. The conditional setup context reduces exposure frequency but does not remove 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 fallback directs installation after a missing-command error without explaining that downloaded code will execute or requiring user approval for local system changes. Although installation supports the documented connector workflow, a request to read HackerRank data does not necessarily authorize installing software; the declared Bash tool restriction may limit execution but does not make the instructions safe.
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