Ralph Loop (Agent Mode)

This skill appears to do what it says — it teaches an OpenClaw agent how to launch and monitor interactive coding CLIs using exec + process — but there are several things to consider before installing or running it: 1. Metadata mismatch: The package/README explicitly require CLIs like opencode/codex/claude/goose, but the registry metadata you were shown said 'none' for required binaries. Confirm which CLIs are actually required and present on the host before use. 2. Review auto-approval flags: The SKILL.md references risky flags (e.g. --yolo, --dangerously-skip-permissions, --full-auto). Avoid enabling those unless you run the skill in a fully isolated sandbox and understand the consequences. 3. Sandbox and least privilege: Run initial tests in an isolated environment (container/VM) with limited network and credentials. Prefer sandboxed execution (docker/e2b/fly) as the README recommends. 4. Inspect generated prompts and files: The agent will create and cat PROMPT.md and other files into CLI commands. Prompt injection or crafted prompts could cause the coding CLI to run unintended actions. Review PROMPT.md, AGENTS.md, and command strings before allowing execution. 5. Monitor runtime and logs: Use the platform's process/exec monitoring controls and be prepared to kill sessions if behavior is unexpected. Do not give the agent access to sensitive cloud credentials or wide git permissions when testing. 6. What would change this assessment: If there were an install script that downloaded code from an untrusted host, or the skill requested unrelated credentials (AWS/GCP tokens) in its declared requirements, or the registry metadata intentionally omitted required exec/process permissions — the verdict would be higher-severity suspicious or worse. Providing explicit, consistent required-tools metadata and removing or clearly warning about permission-bypassing flags would increase my confidence to 'benign'.