← Back to Skills Marketplace
teoslayer

Pilot Watchdog

by Calin Teodor · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
138
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install pilot-watchdog
Description
Security monitoring for suspicious network patterns in Pilot Protocol networks. Use this skill when: 1. You need real-time detection of suspicious connection...
README (SKILL.md)

Pilot Watchdog

Real-time security monitoring for Pilot Protocol with anomaly detection, automated alerting, and threat response.

Commands

Initialize Watchdog

mkdir -p ~/.pilot/watchdog/{alerts,state}
cat > ~/.pilot/watchdog/config.json \x3C\x3CEOF
{
  "enabled": true,
  "check_interval_seconds": 30,
  "rules": {
    "connection_rate_limit": 10,
    "failed_handshake_threshold": 3,
    "polo_score_drop_threshold": 30
  }
}
EOF

Monitor Connection Rate

# Detect abnormal connection rate
CURRENT=$(pilotctl --json connections 2>/dev/null | jq -r '.[].remote_hostname' | sort | uniq -c)

echo "$CURRENT" | while read -r COUNT AGENT; do
  if [ "$COUNT" -gt 10 ]; then
    echo "ALERT: $AGENT has $COUNT connections"
  fi
done

Monitor Polo Score Changes

# Detect sudden polo score drops
STATE_FILE=~/.pilot/watchdog/state/polo_scores.json
THRESHOLD=30

CURRENT=$(pilotctl --json peers | jq '[.[] | {hostname, polo_score}]')

if [ -f "$STATE_FILE" ]; then
  echo "$CURRENT" | jq -r '.[] | "\(.hostname) \(.polo_score)"' | \
  while read -r HOSTNAME CURRENT_SCORE; do
    PREVIOUS_SCORE=$(jq -r --arg h "$HOSTNAME" '.[] | select(.hostname == $h) | .polo_score' "$STATE_FILE")

    if [ "$PREVIOUS_SCORE" != "null" ]; then
      CHANGE=$((CURRENT_SCORE - PREVIOUS_SCORE))
      if [ $CHANGE -lt 0 ] && [ ${CHANGE#-} -ge $THRESHOLD ]; then
        echo "ALERT: $HOSTNAME polo score dropped by ${CHANGE#-} points"
      fi
    fi
  done
fi

echo "$CURRENT" > "$STATE_FILE"

Set Webhook for Events

# Configure daemon webhook
pilotctl --json set-webhook "http://localhost:8080/watchdog"

Workflow Example

Continuous security monitoring with automated responses:

#!/bin/bash
WATCHDOG_DIR=~/.pilot/watchdog
INTERVAL=30

mkdir -p "$WATCHDOG_DIR"/{alerts,state}

# Alert function
alert() {
  echo "$(date -u +%Y-%m-%dT%H:%M:%SZ) [$1] $2" | tee -a "$WATCHDOG_DIR/alerts/alerts.log"
}

# Monitor loop
while true; do
  # Check connection rate
  pilotctl --json connections | jq -r '.[].remote_hostname' | sort | uniq -c | \
    awk '$1 > 10 {print $2}' | while read agent; do
      alert "CONNECTION_RATE" "$agent exceeded connection limit"
    done

  # Check failed handshakes
  PENDING=$(pilotctl --json pending | jq length)
  if [ "$PENDING" -gt 5 ]; then
    alert "HANDSHAKE" "High number of pending handshakes: $PENDING"
  fi

  sleep $INTERVAL
done

Dependencies

Requires pilot-protocol skill, pilotctl binary, jq, and running daemon.

Usage Guidance
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.
Capability Analysis
Type: OpenClaw Skill Name: pilot-watchdog Version: 1.0.0 The pilot-watchdog skill provides legitimate security monitoring utilities for the Pilot Protocol, including connection rate limiting and peer score tracking. The provided Bash scripts in SKILL.md use standard tools like jq and awk safely (e.g., using --arg in jq to prevent injection) and perform local logging and monitoring tasks consistent with the stated purpose. No evidence of data exfiltration, malicious execution, or harmful prompt injection was found.
Capability Assessment
Purpose & 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.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install pilot-watchdog
  3. After installation, invoke the skill by name or use /pilot-watchdog
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release
Metadata
Slug pilot-watchdog
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Pilot Watchdog?

Security monitoring for suspicious network patterns in Pilot Protocol networks. Use this skill when: 1. You need real-time detection of suspicious connection... It is an AI Agent Skill for Claude Code / OpenClaw, with 138 downloads so far.

How do I install Pilot Watchdog?

Run "/install pilot-watchdog" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Pilot Watchdog free?

Yes, Pilot Watchdog is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Pilot Watchdog support?

Pilot Watchdog is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Pilot Watchdog?

It is built and maintained by Calin Teodor (@teoslayer); the current version is v1.0.0.

💬 Comments