pilot-receipt

Deliver delivery and read receipts for Pilot Protocol messages.

7|3|Updated Apr 8, 2026

Search Tags:#communication #delivery #audit-trail #receipt #read-receipt #pilot-protocol

Ready to run

npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-receipt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pilot-receipt
Source: https://github.com/TeoSlayer/pilot-skills/tree/main/skills/pilot-receipt
Command: npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-receipt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delivers verifiable visibility into Pilot Protocol messages by providing delivery confirmations and read receipts, helping teams audit communications and ensure messages reach their intended recipients.

Core Features & Use Cases

Delivery confirmation: Know when a message has been delivered to a recipient.
Read status tracking: Receive updates when a recipient reads a message.
Audit trails: Maintain an auditable history of message delivery and read events across agents.
Use Case: In a team workflow, rely on receipts to confirm critical updates were received and opened by the intended recipients.

Quick Start

Install the Pilot Protocol daemon and then install the pilot-receipt skill to begin tracking message receipts.

Frequently Asked Questions about pilot-receipt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I track message delivery and read receipts over the Pilot Protocol?▼

Message delivery and read receipts over the Pilot Protocol are tracked by capturing delivery confirmations and read status updates. This provides verifiable visibility into whether recipients received and opened communications.

How do I maintain an audit trail for message delivery and read events?▼

Audit trails for message delivery and read events are maintained by logging delivery confirmations and read status updates across agents. This creates an auditable history verifying critical updates reached intended recipients.

Do I need pilotctl running to track read receipts and delivery status?▼

Yes, pilotctl running is required to track read receipts and delivery status. The pilot-protocol stack is also required, with jq needed for optional metadata processing during receipt tracking.

What's the best way to verify message reach and compliance with read acknowledgments?▼

Verifying message reach and read acknowledgment compliance is best achieved by generating delivery confirmations and read receipts. This ensures communications reach intended recipients and tracks when messages are opened.

Can I use jq for metadata processing when tracking Pilot Protocol receipts?▼

Yes, jq can be used for optional metadata processing when tracking Pilot Protocol receipts. It processes receipt metadata alongside the required pilotctl daemon and pilot-protocol stack for delivery and read tracking.

Why am I not getting read confirmations for my Pilot Protocol messages?▼

Missing read confirmations for Pilot Protocol messages may occur if pilotctl is not running or the pilot-protocol stack is improperly configured. Ensure the daemon operates correctly to capture read status updates.