Security audit
Security checks for vulnerabilities and agentic risk
The ArcGIS functions fit the stated purpose, but missing-software recovery tells the agent to run unverified online installers without a clear approval step.
Review and install the CLI separately before enabling the skill, and require approval for installation changes. ArcGIS requests use your OOMOL-connected account and may incur charges. The complete bundled skill was inspected; remote installers, CLI code, and hosted services were not verified. The concern is the uncontrolled setup path, not evidence of malicious intent.
The supplied code executes a remote installer and contains no ArcGIS Online search or data-reading operations. Nothing in the supplied content establishes that this installation is a supporting requirement for the declared functionality. The downloaded script's contents and effects cannot be determined from this command alone.
Piping a remotely fetched script directly into Bash executes mutable network content without a pinned version or independent integrity verification. Compromise of the distribution endpoint or release pipeline could yield arbitrary code execution under the invoking account; the PowerShell example has the same weakness. HTTPS and conditional execution reduce some exposure but do not establish script integrity.
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 the agent to install software after a missing-command error without first obtaining approval for local system changes. Although conditional and relevant to the task, installation executes code with the invoking user's privileges and goes beyond an ArcGIS read request; the declared tool restriction may limit execution but does not make these 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