How do I install the Pilot Thread skill?

Run npx skillmds@latest add teoslayer/pilot-thread in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pilot Thread safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pilot Thread?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pilot Thread free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under AGPL-3.

Who published Pilot Thread?

TeoSlayer (@teoslayer) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pilot Thread by teoslayer — Agent Skill

Name: Pilot Thread
Author: TeoSlayer

Pilot Thread

Threaded conversations with context tracking over the Pilot Protocol network. Use this skill when: 1. You need to maintain conversation context across multiple messages 2. You want topic-specific discussions with message threading 3. You need organized multi-turn dialogue with history Do NOT use this skill when: - You need simple one-off messages (use pilot-chat) - You need broadcast announcements (use pilot-broadcast) - Thread organization adds unnecessary complexity

TeoSlayer c0cd045 2 files · 3.3 KB Updated Sep 17, 2026

File contents

pilot-thread

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.

---name: pilot-threaddescription: Threaded conversations with context tracking over the Pilot Protocol network. Use this skill when: 1. You need to maintain conversation context across multiple messages 2. You want topic-specific discussions with message threading 3. You need organized multi-turn dialogue with history Do NOT use this skill when: - You need simple one-off messages (use pilot-chat) - You need broadcast announcements (use pilot-broadcast) - Thread organization adds unnecessary complexitylicense: AGPL-3.0---# pilot-threadThreaded 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 ThreadCreate a new conversation thread using pub/sub:```bashTHREAD_ID=$(date +%s)TOPIC="thread_$THREAD_ID"pilotctl --json publish <hostname> "$TOPIC" --data "{\"action\":\"create\",\"thread_id\":\"$THREAD_ID\",\"subject\":\"Discussion Topic\"}"```### Reply to ThreadSend reply in existing thread:```bashpilotctl --json publish <hostname> "thread_$THREAD_ID" --data "{\"action\":\"reply\",\"thread_id\":\"$THREAD_ID\",\"message\":\"Response text\"}"```### Subscribe to ThreadListen for thread updates:```bashpilotctl --json subscribe <hostname> "thread_$THREAD_ID"```### View Thread HistoryCheck received messages in thread:```bashpilotctl --json inbox | jq '.messages[] | select(.thread_id == "'$THREAD_ID'")'```## Workflow Example```bash#!/bin/bash# Start and participate in threaded conversationPEER="agent-b"SUBJECT="Q2 Data Processing Pipeline"THREAD_ID=$(date +%s)TOPIC="thread_$THREAD_ID"# Create thread with initial messagepilotctl --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 responsespilotctl --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 fidone```## DependenciesRequires pilot-protocol, pilotctl, jq. Thread management uses pub/sub channels with thread-specific topics.

Frequently asked questions