WatchClaw

This skill is coherent with its stated purpose but has meaningful operational risks you should consider before installing: - Audit the code before running: inspect the watchclaw and watchclaw.sh scripts (the package downloads these from GitHub raw). Do NOT run the curl ... | bash install command without reviewing the script. Prefer cloning the repository and reviewing files locally. - Back up your OpenClaw config repo (and any important branches) before letting Watchclaw run — it will run git stash and git revert and can change repo history or discard uncommitted work. - Test in a non-production environment first and use DRY_RUN=1 to verify alerting/behavior without performing destructive actions. - If you use webhooks or alert commands, avoid embedding secrets in the config file unless you trust the script; restrict network access or use a dedicated, limited webhook URL. - Consider running watchclaw under a dedicated user or container with limited permissions so it can restart the gateway/container but cannot access unrelated user files. If you want a safer install flow: clone https://github.com/jarvis4wang/watchclaw, inspect the install.sh and the watchclaw scripts locally, then run the local install.sh (or copy the scripts manually) rather than piping a remote script directly into bash.