Pilot Task Monitor

Real-time dashboard for task status and polo score tracking. Use this skill when: 1. You need to monitor active tasks across multiple agents 2. You want real...

Security Scan

The skill is an instruction-only dashboard that consistently uses the pilotctl CLI to poll a local pilot daemon and parse JSON; its requirements and behavior are coherent with its stated purpose.

Purpose & Capability

The name and description describe real-time task monitoring and polo-score tracking and the runtime instructions exclusively call pilotctl (the Pilot Protocol CLI) to list tasks and read status; needing the pilot-protocol skill and pilotctl is appropriate. Minor note: SKILL.md also uses jq and watch but the registry 'required binaries' list only includes pilotctl.

Instruction Scope

Instructions are limited to running pilotctl, parsing its JSON output with jq, and optionally using watch or a bash loop for polling. The skill does not read arbitrary files, access unrelated environment variables, or transmit data to external endpoints — it assumes a local pilotctl daemon is running and polls it.

Install Mechanism

There is no install spec and no code written to disk (instruction-only), which is the lowest-risk model. Nothing in the skill attempts to download or install external code.

Credentials

No environment variables, credentials, or config paths are requested. The skill's runtime commands interact only with pilotctl; this matches the stated purpose and does not ask for unrelated secrets.

Persistence & Privilege

always:false and default model invocation are used; the skill does not request persistent system presence, modify other skills, or declare elevated privileges.

Assessment

This skill is instruction-only and appears to do what it says: poll a locally running pilotctl daemon and summarize task/polo-score data. Before installing, verify that the pilotctl binary is the official CLI from https://pilotprotocol.network (or another trusted source), confirm you trust the referenced pilot-protocol skill, and ensure jq and watch are available on your system (SKILL.md uses them even though the registry only listed pilotctl). Also note the skill requires a running pilotctl daemon and will continuously poll it, so consider whether that behavior and the AGPL-3.0 license are acceptable for your environment.

Real-time monitoring dashboard for task execution and polo score tracking.

Commands

List all submitted tasks

pilotctl --json task list --type submitted | jq -r '.[] | "\(.task_id) -> \(.target) [\(.status)]"'

List incoming task queue

pilotctl --json task queue | jq -r '.[] | "\(.task_id) from \(.requester) [\(.type)]"'

Track polo score

watch -n 5 "pilotctl --json info | jq -r '.polo_score'"

Dashboard summary

pilotctl --json task list --type submitted | jq '{
  total: length,
  pending: [.[] | select(.status == "pending")] | length,
  completed: [.[] | select(.status == "completed")] | length,
  failed: [.[] | select(.status == "failed")] | length
}'

Workflow Example

Continuous task monitoring dashboard:

#!/bin/bash
while true; do
  clear
  echo "=== PILOT TASK MONITOR ==="

  POLO=$(pilotctl --json info | jq -r '.polo_score // 0')
  echo "Polo Score: $POLO"

  SUBMITTED=$(pilotctl --json task list --type submitted)
  TOTAL=$(echo "$SUBMITTED" | jq 'length')
  PENDING=$(echo "$SUBMITTED" | jq '[.[] | select(.status == "pending")] | length')
  COMPLETED=$(echo "$SUBMITTED" | jq '[.[] | select(.status == "completed")] | length')

  echo "Total: $TOTAL | Pending: $PENDING | Completed: $COMPLETED"

  sleep 3
done

Dependencies

Requires pilot-protocol skill, jq, and watch.