traffic-monitor

PassAudited by ClawScan on May 1, 2026.

Overview

This is a coherent traffic-reporting skill; the main things to notice are its dependence on local vnstat/systemctl commands and its small persistent heartbeat state file.

This skill appears safe for its stated purpose if you want server traffic reports. Verify vnstat is installed and watching the correct interface, be cautious with the documented systemctl restart command, and know that heartbeat mode writes a small local state file to control repeated alerts.

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.

What this means

The skill may fail or produce no monthly report unless vnstat is already installed, configured, and collecting data on the server.

Why it was flagged

The registry metadata does not declare dependencies or installation steps even though the skill documentation and code rely on vnstat being available.

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

Before installing or invoking it, confirm vnstat is installed, trusted, and monitoring the intended interface.

What this means

Restarting vnstat could affect traffic data collection or require elevated privileges on the server.

Why it was flagged

The documentation includes a service restart command. It is relevant to traffic monitoring, but it is an administrative action and should not be run casually.

Skill content
# 重启 vnstat
systemctl restart vnstat
Recommendation

Treat the systemctl commands as manual maintenance steps and run them only with user approval and appropriate server access.

What this means

The saved state can influence whether future heartbeat runs emit an alert, though it does not contain credentials or detailed traffic logs.

Why it was flagged

Heartbeat mode persists the last reported threshold and percentage in a local OpenClaw memory file so future runs decide whether to print another alert.

Skill content
STATE_FILE = "/root/.openclaw/workspace/memory/traffic-state.json"
Recommendation

If alerts seem missing or repeated, inspect or clear this state file and ensure only trusted users can modify the OpenClaw memory directory.