Skylv System Health Watch
PassAudited by ClawScan on May 4, 2026.
Overview
This appears to be a purpose-aligned local health monitor; the main cautions are that it runs a Node.js helper, can run continuously, and stores local diagnostic data.
This skill looks reasonable for local health monitoring. Before installing or running it, make sure you trust the included `health_monitor.js`, run continuous watch mode only intentionally, and review any generated reports or `.health-*.json` files before sharing them. The supplied source display was truncated, so verify the complete file if available.
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.
Running the skill executes the included script locally and can create or overwrite its own health-monitor files.
The skill is operated by running a local JavaScript helper. This is central to the stated purpose, but it means local code executes with the user's normal permissions.
node health_monitor.js status ... node health_monitor.js check ... node health_monitor.js report json
Run it only from the reviewed skill directory, and avoid executing modified copies unless you have reviewed them.
Generated reports or local history files could reveal endpoint names, stack traces, or other diagnostic context if shared.
The monitor stores local health history/alert settings and tracks error stack/context data. This is appropriate for diagnostics, but such outputs may include operational details.
const HISTORY_FILE = '.health-history.json'; const ALERTS_FILE = '.health-alerts.json'; const MAX_HISTORY = 1000; ... stack: error.stack?.slice(0, 500), context
Keep generated `.health-*.json` files private, review reports before sharing them, and avoid passing secrets into error context.
If started, the monitor may continue consuming resources and updating local state until the process is stopped.
The skill includes a disclosed continuous monitoring mode. There is no evidence of hidden background persistence, but watch mode can keep running until stopped.
# Continuous monitoring node health_monitor.js watch 3000
Use watch mode only when you want live monitoring, choose a reasonable interval, and stop the process when finished.