Soil Rich Ops

Manage Soil Rich by John — website updates, blog/social content, ISDA compliance, orders, FFA programs. Notion-powered.

This skill appears to do what it says (manage website, Notion content, compliance data), but the SKILL.md expects access to local repos, an iCloud Documents folder, and external APIs (Notion, Netlify) while the registry declares no required credentials or paths. Before installing, ask the author to: (1) explicitly list required environment variables (e.g., NOTION_TOKEN, NETLIFY_AUTH_TOKEN, repo SSH key) and any config paths, (2) explain why the iCloud Documents path is needed and restrict file access to only the necessary files, (3) confirm which commands will be run and whether deployments require explicit user approval (ensure deploys cannot happen without explicit consent), and (4) provide the 'site-deployer' skill’s identity and behavior (since deploys are delegated). If you cannot get clear answers, avoid granting the skill access to your website repo, iCloud folders, or API tokens. Consider running it in a sandbox or giving it read-only test data/credentials first.

Type: OpenClaw Skill Name: soilrich-ops Version: 1.0.0 The skill is classified as suspicious due to the potential for shell injection vulnerabilities. The `soil site update` command takes user-controlled `[page]` and `[content]` arguments, which are then used to modify files in `~/soilrich-website/` and commit changes via `git`. If these inputs are not rigorously sanitized by the agent before being passed to shell commands, an attacker could inject arbitrary commands. While the skill's stated purpose is benign, this vulnerability, combined with the broad `git` and `npm` command permissions, presents a significant risk of unauthorized code execution within the agent's environment.