Pilot Thread

Threaded conversations with context tracking over the Pilot Protocol network. Use this skill when: 1. You need to maintain conversation context across multip...

Security Scan

The skill is an instruction-only helper for using the pilotctl CLI to create and subscribe to threaded conversations on the Pilot Protocol; its requirements and instructions are consistent with that purpose.

Purpose & Capability

The name/description describe threaded conversation management and the instructions only require pilotctl and jq to publish/subscribe and inspect inbox messages — which is coherent for the stated functionality.

Instruction Scope

SKILL.md contains concrete shell commands to create threads, reply, subscribe, and view history. It does not request unrelated files, environment variables, or external endpoints beyond peer hostnames used for Pilot Protocol communication.

Install Mechanism

This is instruction-only with no install spec and no code files, so nothing is written to disk by the skill itself. It assumes pilotctl and jq are already available on PATH.

Credentials

The skill declares no required environment variables or credentials. The operations shown use peer hostnames and topic IDs only, so requested privileges are minimal and proportional.

Persistence & Privilege

always is false and model invocation is not disabled (default). The skill does not request persistent installation or to modify other skills/config — no elevated persistence or privilege is requested.

Assessment

This skill is instruction-only and appears coherent, but before using it: 1) verify the pilotctl binary you run is the official, trusted implementation (check vendor/source and version); 2) make sure the Pilot Protocol daemon and network peers you contact are trusted — commands will publish messages to whatever peer/hostname you supply; 3) confirm where pilotctl stores credentials or config on your system (the skill does not declare or manage secrets, but pilotctl itself may use local keys/tokens); 4) be aware the skill's license is AGPL-3.0, which has redistribution implications; and 5) if you need tighter security, review pilotctl invocation details and consider sandboxing or running it in an isolated environment before giving it network access.

Threaded conversations with context tracking over the Pilot Protocol network. This skill enables organized multi-turn dialogues by maintaining conversation threads, allowing multiple simultaneous discussions with clear context separation and complete message history.

Commands

Start a Thread

Create a new conversation thread using pub/sub:

THREAD_ID=$(date +%s)
TOPIC="thread_$THREAD_ID"

pilotctl --json publish <hostname> "$TOPIC" --data "{\"action\":\"create\",\"thread_id\":\"$THREAD_ID\",\"subject\":\"Discussion Topic\"}"

Reply to Thread

Send reply in existing thread:

pilotctl --json publish <hostname> "thread_$THREAD_ID" --data "{\"action\":\"reply\",\"thread_id\":\"$THREAD_ID\",\"message\":\"Response text\"}"

Subscribe to Thread

Listen for thread updates:

pilotctl --json subscribe <hostname> "thread_$THREAD_ID"

View Thread History

Check received messages in thread:

pilotctl --json inbox | jq '.messages[] | select(.thread_id == "'$THREAD_ID'")'

Workflow Example

#!/bin/bash
# Start and participate in threaded conversation

PEER="agent-b"
SUBJECT="Q2 Data Processing Pipeline"
THREAD_ID=$(date +%s)
TOPIC="thread_$THREAD_ID"

# Create thread with initial message
pilotctl --json publish "$PEER" "$TOPIC" --data "{\"action\":\"create\",\"thread_id\":\"$THREAD_ID\",\"subject\":\"$SUBJECT\",\"message\":\"Let's plan the Q2 data processing pipeline.\"}"

echo "Created thread: $THREAD_ID"

# Subscribe to thread responses
pilotctl --json subscribe "$PEER" "$TOPIC" --count 1 --timeout 60s | while read -r msg; do
  ACTION=$(echo "$msg" | jq -r '.action')
  TEXT=$(echo "$msg" | jq -r '.message')

  if [ "$ACTION" = "reply" ]; then
    echo "Response: $TEXT"

    # Continue conversation
    pilotctl --json publish "$PEER" "$TOPIC" --data "{\"action\":\"reply\",\"thread_id\":\"$THREAD_ID\",\"message\":\"Great! Can you handle 100K records per hour?\"}"
    break
  fi
done

Dependencies

Requires pilot-protocol, pilotctl, jq. Thread management uses pub/sub channels with thread-specific topics.