How do I install the Pilot Receipt skill?

Run npx skillmds@latest add teoslayer/pilot-receipt 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 Receipt 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 Receipt?

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 Receipt free to use?

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

Who published Pilot Receipt?

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

Pilot Receipt by teoslayer — Agent Skill

Name: Pilot Receipt
Author: TeoSlayer

Pilot Receipt

Delivery and read receipts for messages over the Pilot Protocol network. Use this skill when: 1. You need confirmation that messages were delivered 2. You want to track when recipients read your messages 3. You need audit trails for message delivery Do NOT use this skill when: - You need anonymous messaging (use pilot-chat without receipts) - You're sending fire-and-forget messages (use pilot-broadcast) - Receipt tracking adds unnecessary overhead

TeoSlayer f90aa91 2 files · 3.0 KB Updated Sep 17, 2026

File contents

pilot-receipt

Delivery and read receipts for messages over the Pilot Protocol network. This skill enables tracking of message delivery status and read confirmation, providing visibility into whether recipients have received and opened your messages.

Commands

Send with Receipts

Send message with metadata to track delivery:

pilotctl --json send-message <hostname> --data "<message>"

Check Inbox

Check received messages (receipts in metadata):

pilotctl --json inbox

Clear inbox after reading:

pilotctl --json inbox --clear

Subscribe to Topic

Subscribe to receipt channel for notifications:

pilotctl --json subscribe <hostname> receipts

Publish Receipt

Publish read receipt confirmation:

pilotctl --json publish <hostname> receipts --data "{\"message_id\":\"123\",\"read_at\":\"$(date -u +%Y-%m-%dT%H:%M:%SZ)\"}"

Workflow Example

#!/bin/bash
# Send message and track delivery/read status

RECIPIENT="agent-b"
MESSAGE="Please confirm receipt of this critical update"
MESSAGE_ID=$(date +%s)

# Send message with ID
pilotctl --json send-message "$RECIPIENT" --data "{\"id\":\"$MESSAGE_ID\",\"text\":\"$MESSAGE\"}"

echo "Message sent: $MESSAGE_ID"
echo "Subscribing to receipt channel..."

# Subscribe to receipt channel
pilotctl --json subscribe "$RECIPIENT" receipts --count 1 | while read -r receipt; do
  RECEIVED_ID=$(echo "$receipt" | jq -r '.message_id')
  READ_AT=$(echo "$receipt" | jq -r '.read_at')

  if [ "$RECEIVED_ID" = "$MESSAGE_ID" ]; then
    echo "Message read at $READ_AT"
    break
  fi
done &

SUB_PID=$!

# Wait for receipt
sleep 60
if kill -0 $SUB_PID 2>/dev/null; then
  kill $SUB_PID
  echo "Warning: No read receipt received"
else
  echo "Receipt confirmed"
fi

Dependencies

Requires pilot-protocol, pilotctl, jq. Receipt mechanism uses pub/sub and message metadata.

---name: pilot-receiptdescription: Delivery and read receipts for messages over the Pilot Protocol network. Use this skill when: 1. You need confirmation that messages were delivered 2. You want to track when recipients read your messages 3. You need audit trails for message delivery Do NOT use this skill when: - You need anonymous messaging (use pilot-chat without receipts) - You're sending fire-and-forget messages (use pilot-broadcast) - Receipt tracking adds unnecessary overheadlicense: AGPL-3.0---# pilot-receiptDelivery and read receipts for messages over the Pilot Protocol network. This skill enables tracking of message delivery status and read confirmation, providing visibility into whether recipients have received and opened your messages.## Commands### Send with ReceiptsSend message with metadata to track delivery:```bashpilotctl --json send-message <hostname> --data "<message>"```### Check InboxCheck received messages (receipts in metadata):```bashpilotctl --json inbox```Clear inbox after reading:```bashpilotctl --json inbox --clear```### Subscribe to TopicSubscribe to receipt channel for notifications:```bashpilotctl --json subscribe <hostname> receipts```### Publish ReceiptPublish read receipt confirmation:```bashpilotctl --json publish <hostname> receipts --data "{\"message_id\":\"123\",\"read_at\":\"$(date -u +%Y-%m-%dT%H:%M:%SZ)\"}"```## Workflow Example```bash#!/bin/bash# Send message and track delivery/read statusRECIPIENT="agent-b"MESSAGE="Please confirm receipt of this critical update"MESSAGE_ID=$(date +%s)# Send message with IDpilotctl --json send-message "$RECIPIENT" --data "{\"id\":\"$MESSAGE_ID\",\"text\":\"$MESSAGE\"}"echo "Message sent: $MESSAGE_ID"echo "Subscribing to receipt channel..."# Subscribe to receipt channelpilotctl --json subscribe "$RECIPIENT" receipts --count 1 | while read -r receipt; do RECEIVED_ID=$(echo "$receipt" | jq -r '.message_id') READ_AT=$(echo "$receipt" | jq -r '.read_at') if [ "$RECEIVED_ID" = "$MESSAGE_ID" ]; then echo "Message read at $READ_AT" break fidone &SUB_PID=$!# Wait for receiptsleep 60if kill -0 $SUB_PID 2>/dev/null; then kill $SUB_PID echo "Warning: No read receipt received"else echo "Receipt confirmed"fi```## DependenciesRequires pilot-protocol, pilotctl, jq. Receipt mechanism uses pub/sub and message metadata.

Frequently asked questions