← Back to Skills Marketplace
Self-Heal Watchdog
by
bptravel2017
· GitHub ↗
· v1.0.0
· MIT-0
303
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install self-heal-watchdog
Description
Automated self-healing system for OpenClaw gateway with model failover support. Three-layer protection: process watchdog (auto-restart on crash), config guar...
Usage Guidance
This skill largely does what it says — it will copy scripts into ~/.openclaw/watchdog, register a scheduler (launchd plist on macOS), back up and modify ~/.openclaw/openclaw.json, and call the 'openclaw' CLI to restart the gateway. Before installing: (1) review the scripts yourself (they are small and readable); (2) ensure you trust the openclaw CLI on your system; (3) back up ~/.openclaw/openclaw.json manually (setup.sh may fail if that file is missing); (4) verify you have python3, curl, and relevant system tools; (5) run in DRY_RUN=1 mode to observe actions without changes; and (6) be aware the installer will create a persistent scheduled job (uninstall instructions are provided). The main issue here is metadata mismatch (required binaries/env not declared) — that increases risk of surprise failures or unexpected behavior, so treat this as a privileged change and test it in a safe environment first.
Capability Analysis
Type: OpenClaw Skill
Name: self-heal-watchdog
Version: 1.0.0
The skill bundle implements a self-healing watchdog that requires high-risk capabilities, including modifying the primary 'openclaw.json' configuration file and establishing persistence via macOS 'launchd' (com.openclaw.watchdog.plist). While these actions are clearly aligned with the stated purpose of automated recovery and model failover, the scripts (specifically setup.sh and model-failover.sh) perform automated service restarts and configuration overwrites. No evidence of malicious intent, data exfiltration, or remote command execution was found, but the broad system-level management qualifies as suspicious under the provided criteria.
Capability Assessment
Purpose & Capability
The code performs exactly the advertised tasks: process monitoring, config backup/rollback, and model failover by editing ~/.openclaw/openclaw.json and restarting the gateway. Those capabilities belong to a self-heal watchdog. However, the skill metadata declares no required binaries or env vars while the scripts clearly assume tools (python3, curl, pgrep, launchctl/system utilities, and an 'openclaw' CLI) and access to the user's OpenClaw config — this mismatch is material and should have been declared.
Instruction Scope
SKILL.md instructs running setup.sh which copies scripts, registers a scheduler, and explains commands; the scripts themselves operate on local files and localhost health endpoints only. All runtime actions (backing up and editing openclaw.json, restarting gateway, registering a launchd job) are within the stated scope. There is no evidence the scripts exfiltrate data or contact external endpoints beyond localhost.
Install Mechanism
This is an instruction-only skill (no external download/install step). Installing runs setup.sh which writes files under ~/.openclaw/watchdog and registers a launchd agent. No remote code is fetched by the install process, lowering supply-chain risk — but the installer does create persistent scheduled execution on the host.
Credentials
requires.env and primary credential are listed as none, but the scripts use/assume several environment variables and binaries (OPENCLAW_HOME, GATEWAY_URL, HEALTH_ENDPOINT, DRY_RUN, plus python3, curl, pgrep, launchctl/systemd/cron, and the openclaw CLI). The skill does modify a local configuration file (~/.openclaw/openclaw.json) and writes logs/backups; while this is coherent with purpose, the metadata should have declared these requirements and that it will change your config. No secret/API exfiltration is apparent in the code.
Persistence & Privilege
The installer registers a persistent scheduled job (launchd plist on macOS, with alternatives noted for cron/systemd). always:false (not forced), but installing will create long-lived system scheduler entries and files under the user's home, and register a service that runs every 60s. This is expected for a watchdog but is a high-impact change that requires user consent.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install self-heal-watchdog - After installation, invoke the skill by name or use
/self-heal-watchdog - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release: Three-layer protection with model failover
Metadata
Frequently Asked Questions
What is Self-Heal Watchdog?
Automated self-healing system for OpenClaw gateway with model failover support. Three-layer protection: process watchdog (auto-restart on crash), config guar... It is an AI Agent Skill for Claude Code / OpenClaw, with 303 downloads so far.
How do I install Self-Heal Watchdog?
Run "/install self-heal-watchdog" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Self-Heal Watchdog free?
Yes, Self-Heal Watchdog is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Self-Heal Watchdog support?
Self-Heal Watchdog is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Self-Heal Watchdog?
It is built and maintained by bptravel2017 (@bptravel2017); the current version is v1.0.0.
More Skills