Security audit
Security checks for vulnerabilities and agentic risk
The weather features fit their purpose, but setup can execute changing remote code and introduce other agent skills without clearly explaining those effects.
Review and install a verified CLI release yourself before use, rather than allowing automatic remote-script execution. Consider setting OO_SKILLS_SYNC_DISABLED=1 to prevent startup writes to other agents' skill directories, as documented in the [CLI reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables). OOMOL mediates your weather requests and connected credentials. The remote installer and hosted connector implementation were not inspected.
The supplied command executes a remote installer unrelated to the declared AccuWeather functionality. Nothing in the chunk accesses AccuWeather or retrieves weather data, and no connection is established that would justify this installation as a supporting implementation detail. The downloaded script's further behavior is not visible.
The supplied chunk performs only a login operation, not AccuWeather searching or reading. Authentication could be a supporting implementation detail, but the provided code establishes no connection between this login and the declared AccuWeather functionality.
The installation command pipes a remotely retrieved, unpinned script directly into Bash without verifying its integrity or reviewing its contents; the PowerShell alternative has the same weakness. Compromise of the distribution endpoint or script could execute arbitrary code with the invoking user's privileges, exposing local files and credentials. The missing-CLI prerequisite reduces exposure frequency but does not constrain what the downloaded code can do.
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
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