DC gateway-health-monitor
Monitor and auto-fix OpenClaw gateway stability issues. Diagnoses launchd throttling, plugin restart loops, hung shutdowns, and macOS power management interference. Use when the gateway keeps disconnecting, restarting, or staying down for long periods. Triggers on "gateway down", "gateway keeps restarting", "disconnected", "gateway unstable", "launchd throttling", "gateway won't start".
As a process C 54/100 · Has gaps — weak spots: steps, result and completion, inputs and preconditions
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 7
-
high Dangerous commands
cmd-persistencescripts/install-patcher.sh:42Persistence mechanism (cron / launchd / scheduled task / autorun registry)launchctl bootstrap "gui/$(id -u)" "$PATCHER_PLIST"
-
high Dangerous commands
cmd-persistenceSKILL.md:58Persistence mechanism (cron / launchd / scheduled task / autorun registry)launchctl bootstrap gui/$(id -u) ~/Library/LaunchAgents/ai.openclaw.gateway.plist
Medium and low: 5
-
medium Dangerous commands
cmd-persistencescripts/diagnose.sh:7Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)PLIST="$HOME/Library/LaunchAgents/ai.openclaw.gateway.plist"
code literal -
medium Dangerous commands
cmd-persistencescripts/install-patcher.sh:7Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)PLIST_TO_WATCH="$HOME/Library/LaunchAgents/ai.openclaw.gateway.plist"
code literal -
medium Dangerous commands
cmd-persistencescripts/install-patcher.sh:8Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)PATCHER_PLIST="$HOME/Library/LaunchAgents/ai.openclaw.plist-patcher.plist"
code literal -
medium Dangerous commands
cmd-persistencescripts/patch-plist.sh:6Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)PLIST="$HOME/Library/LaunchAgents/ai.openclaw.gateway.plist"
code literal -
medium Dangerous commands
cmd-persistenceSKILL.md:45Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)**Fix**: Add these keys to the launchd plist (`~/Library/LaunchAgents/ai.openclaw.gateway.plist`):
quoted
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 54/100
- 0Steps. Prose only: no discrete steps
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 5 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 970 tokens
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 389: enough signal without eating the budget
- +4Structure: 13 headings
- +4Has examples (9 code blocks)
- +3All 4 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.