Pilot Watchdog
v1.0.0Security monitoring for suspicious network patterns in Pilot Protocol networks. Use this skill when: 1. You need real-time detection of suspicious connection...
⭐ 0· 26·0 current·0 all-time
byCalin Teodor@teoslayer
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill claims to provide real-time monitoring for Pilot Protocol networks and only requires the pilotctl binary, jq, and the pilot-protocol skill. Those dependencies and the pilotctl commands used in SKILL.md align with the stated purpose.
Instruction Scope
The instructions create and write configuration and state files under ~/.pilot/watchdog, run an infinite monitoring loop, and call pilotctl (including set-webhook). This is expected for a local watchdog but you should note the skill will create files in your home directory, maintain state, and configure a webhook (default example is http://localhost:8080/watchdog). No instructions attempt to read unrelated system files or exfiltrate data to external domains.
Install Mechanism
This is an instruction-only skill with no install spec or remote downloads. That minimizes installation risk because nothing is written to disk by the skill package itself beyond what the runtime instructions do.
Credentials
No environment variables or credentials are requested. The only access required is to the pilotctl CLI/daemon and to create local files under the user's home directory, which is proportionate to a monitoring tool.
Persistence & Privilege
The skill is not marked always:true and does not modify other skills or system-wide settings. It does write its own config/state under ~/.pilot/watchdog and expects a running pilot daemon, which is appropriate for its function. Model invocation is allowed (default) but that is normal and not by itself a concern.
Assessment
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.Like a lobster shell, security has layers — review code before you run it.
latestvk97af7ghzpwen2m3t420yzvnqx84g6ct
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Binspilotctl