Pilot Priority Queue

Priority-based message delivery with urgency levels over the Pilot Protocol network. Use this skill when: 1. You need urgent message handling with priority l...

Security Scan

The skill's declared purpose (priority message handling over the Pilot Protocol) matches its instructions and requirements; it's an instruction-only skill that delegates to the pilotctl CLI and uses jq for filtering.

Purpose & Capability

Name/description describe priority-based message handling and the SKILL.md only requires the pilotctl CLI and the pilot-protocol skill, which are coherent with that purpose. Examples show sending and receiving messages and triaging by prefix; nothing requests unrelated services or credentials.

Instruction Scope

Instructions are narrowly scoped to running pilotctl and processing its JSON output via jq and Bash. Two minor issues: (1) examples rely on jq for filtering but jq is not declared in the required binaries list; absence of jq only limits convenience but may confuse users. (2) The workflow suggests using 'pilotctl --json inbox --clear' which is destructive (clears the inbox); callers should be aware this deletes messages and only run it after processing or in non-production/testing environments.

Install Mechanism

No install spec or downloads — instruction-only skill. Nothing is written to disk by the skill bundle itself, so install risk is low. The real risk surface is the external pilotctl binary, whose provenance should be verified by the user.

Credentials

The skill requires no environment variables or credentials. That is proportionate to the stated purpose. It does require the pilotctl binary and a running pilot daemon, which are expected for a CLI-based protocol skill.

Persistence & Privilege

The skill is not always-enabled and does not request persistent system-wide privileges or modify other skills. Autonomous invocation is allowed by platform default but not exceptional here.

Assessment

This skill is internally consistent but depends entirely on the pilotctl CLI and a running Pilot Protocol daemon. Before using: (1) Verify pilotctl is an official/trusted binary (check vendor homepage, download signature, or inspect binary), (2) install jq if you want to use the provided filtering examples, (3) test commands in a safe environment because 'pilotctl --json inbox --clear' will delete messages, and (4) ensure you have the companion pilot-protocol skill and a running daemon. Also note the skill is AGPL-3.0 licensed — review license implications for your use. If you need stronger assurance, request the upstream pilotctl source or release URL and review its behavior (network access, credential handling) before granting it to production systems.

Priority-based message delivery with urgency levels over the Pilot Protocol network. This skill enables structured message prioritization, ensuring urgent communications are processed first while maintaining ordered delivery for messages of equal priority.

Commands

Send messages with priority prefix

# Send critical message with [CRITICAL] prefix
pilotctl --json send-message <hostname> --data "[CRITICAL] System alert"

# Send high priority with [HIGH] prefix
pilotctl --json send-message <hostname> --data "[HIGH] Urgent task"

# Send normal message
pilotctl --json send-message <hostname> --data "Regular update"

# Send low priority with [LOW] prefix
pilotctl --json send-message <hostname> --data "[LOW] FYI: Log summary"

Receive and filter by priority

# View all inbox
pilotctl --json inbox

# Filter critical messages using jq
pilotctl --json inbox | jq '.items[]? | select(.content | startswith("[CRITICAL]"))'

# Filter high priority
pilotctl --json inbox | jq '.items[]? | select(.content | startswith("[HIGH]"))'

Manual queue management

# Clear inbox after processing
pilotctl --json inbox --clear

Workflow Example

Process messages by priority with automatic triage:

#!/bin/bash
# Process priority inbox using prefix tags

INBOX=$(pilotctl --json inbox)

# Extract and count by priority prefix
CRITICAL_COUNT=$(echo "$INBOX" | jq '[.items[]? | select(.content | startswith("[CRITICAL]"))] | length')
HIGH_COUNT=$(echo "$INBOX" | jq '[.items[]? | select(.content | startswith("[HIGH]"))] | length')
NORMAL_COUNT=$(echo "$INBOX" | jq '[.items[]? | select(.content | (startswith("[CRITICAL]") or startswith("[HIGH]") or startswith("[LOW]")) | not)] | length')
LOW_COUNT=$(echo "$INBOX" | jq '[.items[]? | select(.content | startswith("[LOW]"))] | length')

echo "Critical: $CRITICAL_COUNT, High: $HIGH_COUNT, Normal: $NORMAL_COUNT, Low: $LOW_COUNT"

# Process critical first
if [ "$CRITICAL_COUNT" -gt 0 ]; then
  echo "CRITICAL MESSAGES:"
  echo "$INBOX" | jq -r '.items[]? | select(.content | startswith("[CRITICAL]")) |
    "[\(.timestamp // "N/A")] \(.content)"'
fi

# Process high priority
if [ "$HIGH_COUNT" -gt 0 ]; then
  echo "HIGH PRIORITY:"
  echo "$INBOX" | jq -r '.items[]? | select(.content | startswith("[HIGH]")) |
    "[\(.timestamp // "N/A")] \(.content)"'
fi

Dependencies

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