Pilot Watchdog
Security checks across static analysis, malware telemetry, and agentic risk
Overview
The skill's requirements and instructions are consistent with a local Pilot Protocol monitoring tool: it relies on pilotctl/jq and creates local config/state under ~/.pilot/watchdog for continuous monitoring and alerting.
This skill appears coherent for local Pilot Protocol monitoring, but review a few practical points before installing: - Inspect the commands in SKILL.md and confirm you are comfortable with them creating and writing to ~/.pilot/watchdog (config, state, alerts.log). - The example webhook is set to http://localhost:8080/watchdog; if you change it to an external URL, ensure that endpoint is trusted and that sending peer/alert data externally is acceptable for your environment. - pilotctl is the operational surface to the Pilot daemon — verify pilotctl is the official binary from a trusted source and that the pilot daemon runs with appropriate privileges. - Run the monitoring loop under a controlled service manager (systemd) or supervision, and ensure proper file permissions on ~/.pilot/watchdog to limit access to logs/state. - The skill uses AGPL-3.0; confirm license terms meet your policy requirements. If you need stricter guarantees, ask the skill author for an explicit option to run in a one-shot audit mode (no persistent config or daemon loop) and for documentation of what pilotctl commands will disclose about peers/connections.
SkillSpector
SkillSpector findings are pending for this release.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.