Provides on-demand 10-second automatic rollback protection when modifying openclaw.json to ensure Gateway stability.

This skill is small and coherent, but inspect and run it carefully: 1) Ensure you trust the openclaw CLI on your PATH — the script calls it with status and restart commands. 2) Check ownership/permissions of ~/.openclaw and ~/.openclaw/backups: if those dirs are writable or symlinked by an untrusted user, cp/ls operations could be abused (symlink/TOCTOU). 3) Logs are written to /tmp/openclaw-watchdog.log which is world-writeable by default on some systems; consider changing the log path or securing /tmp to avoid information disclosure or symlink attacks. 4) Backups and failed-config copies may contain sensitive credentials — secure backup storage and access. 5) Run the script manually in a safe environment first to confirm behavior; you may want to add stricter checks (atomic file replacement, secure temporary files, explicit permission checks) before using it in production.

Type: OpenClaw Skill Name: config-guard Version: 0.1.0 The skill bundle provides a 'Claw Seatbelt' feature designed to automatically roll back OpenClaw Gateway configurations to a previous backup if the Gateway becomes unresponsive. The `SKILL.md` instructions are clear and directly align with this stated purpose, showing no signs of prompt injection attempts to subvert the agent. The `bin/watchdog.sh` script implements the rollback logic using standard shell commands (`ls`, `cp`, `grep`) and the legitimate `openclaw` CLI tool to manage configurations and restart the Gateway. There is no evidence of data exfiltration, unauthorized network activity, persistence mechanisms, or obfuscation. The script operates within the expected scope of a configuration management utility, making its intent benign.