Openclaw Gateway Guardian

OpenClaw Gateway Guardian - Automatic monitoring, protection, and restart of OpenClaw Gateway service. Prevents gateway from stopping, crashing, or disappear...

This package is not clearly dishonest or malicious, but it has multiple inconsistencies you should resolve before installing: - Confirm the presence and trustworthiness of the `openclaw` CLI on the host; the guardian calls `openclaw gateway restart` but the skill metadata does not declare that binary as required. - The README/SKILL.md mention commands (init, health) and notification features that the included script does not implement — expect limited functionality (start/stop/status/logs) as shipped. - The docs encourage creating scheduled tasks (even under SYSTEM); avoid running unfamiliar scripts as SYSTEM. If you need autostart, prefer running under a dedicated low-privilege service account and review the install script (there are references to an install_powerShell script that is not present in the package manifest). - Inspect the script yourself (it is small): it writes files under ~/.openclaw_guardian, creates PID/state files, and uses subprocess to restart the gateway. Run it in a safe test environment first to confirm behavior. - If you plan to rely on notifications, verify whether those features are implemented or implement them yourself; do not paste secrets into configs unless you understand where they will be used. If the author can (a) declare the `openclaw` binary requirement, (b) update/remove docs so commands match the actual script (or ship an updated script implementing init/health/notifications), and (c) avoid recommending SYSTEM-level scheduled tasks or clearly explain why elevated privileges are required, the package would be much more coherent and easier to trust.

Type: OpenClaw Skill Name: openclaw-gateway-guardian Version: 1.0.3 The bundle is a utility designed to monitor and automatically restart the OpenClaw Gateway service. The primary logic in `scripts/gateway_guardian.py` performs health checks via TCP port monitoring and uses hardcoded subprocess calls to restart the service if it fails. While the documentation (README.md, SKILL.md) claims to support notifications that are not yet implemented in the provided Python script, and includes highly specific local environment paths (e.g., in STATUS.md), there is no evidence of malicious intent, data exfiltration, or prompt injection.