Skills/ClawHub/self-heal-watchdog

self-heal-watchdog@1.0.0

VERIFIED· install only

Publisher claims: "Automated self-healing system for OpenClaw gateway with model failover support. Three-layer protection: process watchdog (auto-restart on crash), config guar..." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry ClawHubPublisher bptravel2017 · publishing for 244 daysInstalls 1,223Last detonated 33 min ago
$clawhub install self-heal-watchdog
WatchReport an issue

Coverage

Install scripts ran; no agent task scenario for this bundle.
Tested
install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; install scripts ran; no agent task scenario for this bundle) on 2026-11-16 and scored it 84/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios
t+CategoryObserved action
0.0sprocessinstall script run in the sandbox
0.1sfilesystemread ~/.openclaw/watchdog/ · ~/.openclaw/openclaw.json · ~/.openclaw/openclaw.json.bak outside project
0.1sfilesystemwrote ~/.openclaw/watchdog/watchdog-state.json
0.1sprocessexec /usr/bin/dirname
0.1sprocessexec /usr/bin/mkdir
0.1sprocessexec /usr/bin/cp
0.1sprocessexec /usr/bin/chmod
0.1sprocessexec /usr/bin/cat
0.1sprocessexited 1: cp: cannot stat '/tmp/ks-detonate-Pcrxsa/setup/home/.openclaw/openclaw.json': No such file or directory
0.1sprocessscript backend runs setup only
0.1sprocessscript backend runs setup only
0.2sprocesssecond launch, clock +45 days, CI unset
0.2sfilesystemread ~/.openclaw/watchdog/ · ~/.openclaw/openclaw.json.bak outside project
0.2sprocessexec /usr/bin/dirname
0.2sprocessexec /usr/bin/mkdir
0.2sprocessexec /usr/bin/cp
0.2sprocessexec /usr/bin/chmod
0.2sprocessexited 1: cp: cannot stat '/tmp/ks-detonate-Pcrxsa/later/home/.openclaw/openclaw.json': No such file or directory

Static findings

MEDIUM
File permission modification commandscripts/setup.sh:55 · File permission modification command — agent changes file ownership/permissionschmod +x "$WATCHDOG_DIR"/*.shFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05

No other findings across 980 lines in 9 files.

Cost to the agent

Instructions loaded
≈430 tok
1 file · 9 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.