Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
ClawGuard
v1.1.0System-level watchdog for OpenClaw gateway restarts and sub-agent task PIDs. Monitors registered PIDs and optional log/directory freshness. Auto-reverts conf...
⭐ 0· 402·1 current·1 all-time
by@camopel
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill is a local watchdog that watches PIDs, log/dir mtimes, and gateway restarts. The files and install script operate entirely in the user's home (~/.openclaw and ~/.local/bin) and interact with the system service manager (systemd user unit or launchd) and the 'openclaw' CLI for notifications — all of which align with the described purpose.
Instruction Scope
The SKILL.md and code limit activity to explicitly registered tasks and gateway restart watches. The daemon reads/writes ~/.openclaw/openclaw.json (backups), reads journalctl / launchctl output, and includes small snippets of status/journal in notification messages. That behavior is coherent with 'why the gateway failed' diagnostics, but it means systemd/journal output and parts of the local openclaw config may be sent out via the configured OpenClaw notification targets — review whether those notifications might leak sensitive information to external channels.
Install Mechanism
No remote downloads or package registry installs; install.sh copies local files into the user's home, creates a CLI wrapper in ~/.local/bin, and registers a per-user systemd or launchd agent. This is low-risk compared to fetching/executing remote archives.
Credentials
The skill requires only Python3 to run and uses the user's OpenClaw config file and workspace. It does not request external credentials or unusual environment variables. Notifications are sent via the local 'openclaw' CLI, so sensitive channel configuration depends on the existing OpenClaw setup (not the skill).
Persistence & Privilege
The installer configures and enables a user-level persistent service (systemd user or launchd) that restarts automatically. always:false in the skill metadata. This is expected for a watchdog, but installing gives the skill a persistent background presence in the user's session until the user removes/stop the service.
Assessment
Before installing: 1) Review and confirm you trust the author — this will install a persistent user service and a CLI under your home directory. 2) Understand it will copy/restore your ~/.openclaw/openclaw.json from backups and will run systemctl/launchctl to restart the gateway — that's the intended behavior but is powerful, so ensure backups are what you expect. 3) Notifications include snippets of status/journal output and will be sent through your configured OpenClaw channels — verify that those channels are appropriate to receive potential debug output. 4) The installer requires python3 in PATH; it embeds your current PATH into the service environment. If you have concerns about the exact python binary used, inspect/modify install.sh before running. 5) If you need tighter control, consider installing but not enabling ExecStartPre in the gateway service, or run the daemon manually first to observe behavior. If you want more assurance, review the three script files locally (they are small and self-contained) before running the installer.Like a lobster shell, security has layers — review code before you run it.
latestvk9702m7cj903btfg4hqjsdaycd825b02
License
MIT-0
Free to use, modify, and redistribute. No attribution required.