Gateway Watchdog
PassAudited by ClawScan on May 1, 2026.
Overview
Gateway Watchdog is a coherent local log-monitoring skill; it reads OpenClaw logs and can be set up for recurring checks, but the reviewed artifacts show no credential use, network calls, or destructive actions.
This skill appears safe for its stated purpose. Before using it, be comfortable with it reading OpenClaw/Gateway logs and writing local state under ~/.local/state/gateway-watchdog. Enable the optional heartbeat or cron integration only if you want recurring monitoring and notifications.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Reports may include snippets from local Gateway/OpenClaw logs, so sensitive error messages could be shown to the user or included in notifications.
The script reads local OpenClaw/systemd logs to detect errors, and later reports matching top error lines. This is expected for a log monitor, but logs may contain sensitive operational details.
journalctl "$scope" -u "$candidate" --since "${WINDOW}min ago" --no-pager ...; find "$log_dir" -maxdepth 1 -name "*.log" ... | xargs -0 catUse it only for logs you are comfortable monitoring, and review reports before forwarding or sharing them outside the intended user channel.
If enabled, the watchdog can continue running on a schedule and notify the user when error thresholds are exceeded.
The skill documents an optional recurring cron setup and heartbeat integration. This creates ongoing monitoring if the user chooses to enable it, but it is clearly disclosed and aligned with the skill purpose.
openclaw cron add --name "gateway-watchdog" --schedule "*/30 * * * *" --task "Run gateway-watchdog.sh verbose. If errors detected, notify user with the report."
Only add the heartbeat or cron entry if recurring monitoring is desired, and remove that schedule if you no longer want automated checks.