Gateway Watchdog Lite

PassAudited by ClawScan on May 10, 2026.

Overview

This skill appears to do what it says—install a background watchdog that restarts the local OpenClaw gateway and can send Telegram alerts—but users should understand that it persists and can automatically restart or kill gateway-related processes.

This skill is reasonable if you want an always-on local watchdog for the OpenClaw gateway. Before installing, confirm the workspace path and gateway port, decide whether Telegram alerts are desired, and remember that the service will keep running and may restart or kill gateway processes until you disable or uninstall it.

Findings (4)

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.

Note

ASI10: Rogue Agents

What this means

The watchdog will continue running in the background and may act without further prompts after installation.

Why it was flagged

The skill intentionally installs a persistent background service. This is disclosed and purpose-aligned for a watchdog, but persistence is important for users to notice.

Skill content

Installs a launchd service (macOS) or systemd service (Linux / VPS) that probes the gateway every 2 minutes and auto-recovers it on failure.

Recommendation

Install only if you want continuous background monitoring, and use the documented uninstall commands if you no longer want it running.

Note

ASI02: Tool Misuse and Exploitation

What this means

If configured incorrectly, the watchdog could repeatedly restart or terminate gateway-related processes every cooldown interval.

Why it was flagged

The recovery logic can automatically restart the OpenClaw gateway service or kill matching gateway processes when the health check fails. This is purpose-aligned, but a wrong port or misdetected failure could disrupt local OpenClaw processes.

Skill content

systemctl --user restart openclaw-gateway 2>/dev/null
    else
        pkill -f "openclaw.*gateway" 2>/dev/null || true

Recommendation

Confirm OC_PORT and WORKSPACE_PATH before enabling the service, monitor the logs after installation, and disable the service if it restarts the gateway unexpectedly.

Note

ASI03: Identity and Privilege Abuse

What this means

If Telegram alerts are enabled, the service can send gateway recovery/failure messages through the user's configured gog/Telegram setup.

Why it was flagged

Optional Telegram alerts use the local gog CLI to send messages to the configured Telegram ID. This appears limited to status alerts and does not show credential theft or unrelated account access.

Skill content

"$GOG_BIN" telegram send --to "$TELEGRAM_ID" --text "$MSG" 2>/dev/null || true

Recommendation

Set TELEGRAM_ID to an empty string if you do not want alerts, and verify your gog Telegram configuration before enabling notifications.

Note

ASI04: Agentic Supply Chain Vulnerabilities

What this means

Users have to rely on the included scripts and documentation rather than a pinned source or managed install specification.

Why it was flagged

The runnable scripts are included, but the registry-level provenance and install metadata are limited. This is not evidence of malicious behavior, but it reduces assurance compared with a clearly sourced and declarative install.

Skill content

Source: unknown
Homepage: none
Install specifications: No install spec — this is an instruction-only skill.

Recommendation

Review the included scripts before running them and prefer installing from a publisher/source you trust.