Astrill Watchdog

ReviewAudited by ClawScan on May 1, 2026.

Overview

This appears to be a straightforward Astrill VPN watchdog, but it installs a persistent user-level service that can automatically restart the VPN.

Before installing, make sure you want a background service that starts on login, pings periodically, writes local VPN diagnostic logs, and can kill/relaunch Astrill automatically. Review setup.sh and the config block, then disable the systemd user service if you stop using it.

Findings (3)

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.

Low

#ASI02: Tool Misuse and Exploitation

What this means

If the watchdog misdetects a failure, it may restart Astrill and briefly disrupt VPN or network connectivity.

Why it was flagged

The script can automatically kill and relaunch the Astrill process when its health checks fail. This is central to the skill's purpose, but it gives the watchdog direct control over the VPN client.

Skill content

pkill -u "$ASTRILL_USER" -f '/usr/local/Astrill/astrill' ... env "${DESKTOP_ENV[@]}" setsid "$ASTRILL_BIN" /autostart

Recommendation

Install only if you want automatic Astrill restarts; review the CHECK_INTERVAL, RECONNECT_WAIT, and PING_HOST settings before enabling it.

Medium

#ASI10: Rogue Agents

What this means

The watchdog will keep monitoring and may restart Astrill automatically after login until the service is stopped or disabled.

Why it was flagged

Setup enables and starts a user-level systemd service so the watchdog continues running after installation and on future logins. This persistence is disclosed and purpose-aligned.

Skill content

systemctl --user enable astrill-watchdog.service ... systemctl --user restart astrill-watchdog.service

Recommendation

Use the documented stop command when needed, and disable the user service if you no longer want it to run on login.

Info

#ASI04: Agentic Supply Chain Vulnerabilities

What this means

The registry may not warn non-Ubuntu users or users missing required tools before they try setup.

Why it was flagged

The registry metadata does not declare the Ubuntu/systemd/tooling requirements even though the skill artifacts do. This is an under-declaration issue rather than hidden behavior.

Skill content

OS restriction: none ... Required binaries (all must exist): none ... No install spec — this is an instruction-only skill.

Recommendation

Confirm you are on Ubuntu with Astrill installed and review setup.sh before running it.