How do I install the Pilot Relay skill?

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

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

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

Who published Pilot Relay?

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

Pilot Relay by teoslayer — Agent Skill

Name: Pilot Relay
Author: TeoSlayer

Pilot Relay

Store-and-forward messaging for offline peers over the Pilot Protocol network. Use this skill when: 1. You need to send messages to agents that may be offline 2. You want guaranteed eventual delivery 3. You need asynchronous communication patterns Do NOT use this skill when: - You need real-time chat (use pilot-chat with online peers) - You need streaming data (use pilot-connect) - You need immediate confirmation (use pilot-chat with receipts)

TeoSlayer cf3ea7f 2 files · 3.1 KB Updated Sep 17, 2026

File contents

pilot-relay

Store-and-forward messaging for offline peers. Enables guaranteed message delivery to agents that may be temporarily offline, with automatic delivery when they come back online.

Essential Commands

Send message (auto-relayed if peer offline)

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

Check daemon status

pilotctl --json daemon status

Retrieve messages from inbox

pilotctl --json inbox

Clear inbox after processing

pilotctl --json inbox --clear

Workflow Example

Agent A sends to Agent B (message auto-relayed if B is offline):

#!/bin/bash
# Agent A (sender)

# Try to find Agent B
pilotctl --json find agent-b

# Send message (auto-queued for relay if offline)
pilotctl --json send-message agent-b --data "Important: Database migration tonight"

# Check daemon status
pilotctl --json daemon status

Agent B comes online and retrieves messages:

#!/bin/bash
# Agent B (receiver)

# Start daemon (auto-retrieves relayed messages)
pilotctl --json daemon start

# Check inbox for messages
INBOX=$(pilotctl --json inbox)
echo "$INBOX" | jq -r '.items[]? | "[\(.timestamp)] \(.content)"'

# Send acknowledgment reply
pilotctl --json send-message agent-a --data "Acknowledged: Will monitor migration"

# Clear inbox
pilotctl --json inbox --clear

Relay Behavior

Automatic queuing

Messages are automatically queued when:

Recipient peer is offline
Direct connection fails after retries
Peer is behind symmetric NAT without relay support

Delivery guarantees

At-least-once delivery
Ordered per-sender
7-day retention
Automatic retry

Relay nodes

Registered rendezvous servers act as relay points
Messages are encrypted end-to-end (relay cannot read content)
Relay nodes store messages temporarily until delivery

Dependencies

Requires pilot-protocol skill, pilotctl binary, running daemon, registry connection, and trust relationship between sender/recipient.

---name: pilot-relaydescription: Store-and-forward messaging for offline peers over the Pilot Protocol network. Use this skill when: 1. You need to send messages to agents that may be offline 2. You want guaranteed eventual delivery 3. You need asynchronous communication patterns Do NOT use this skill when: - You need real-time chat (use pilot-chat with online peers) - You need streaming data (use pilot-connect) - You need immediate confirmation (use pilot-chat with receipts)license: AGPL-3.0---# pilot-relayStore-and-forward messaging for offline peers. Enables guaranteed message delivery to agents that may be temporarily offline, with automatic delivery when they come back online.## Essential Commands### Send message (auto-relayed if peer offline)```bashpilotctl --json send-message <hostname> --data "<message>"```### Check daemon status```bashpilotctl --json daemon status```### Retrieve messages from inbox```bashpilotctl --json inbox```### Clear inbox after processing```bashpilotctl --json inbox --clear```## Workflow ExampleAgent A sends to Agent B (message auto-relayed if B is offline):```bash#!/bin/bash# Agent A (sender)# Try to find Agent Bpilotctl --json find agent-b# Send message (auto-queued for relay if offline)pilotctl --json send-message agent-b --data "Important: Database migration tonight"# Check daemon statuspilotctl --json daemon status```Agent B comes online and retrieves messages:```bash#!/bin/bash# Agent B (receiver)# Start daemon (auto-retrieves relayed messages)pilotctl --json daemon start# Check inbox for messagesINBOX=$(pilotctl --json inbox)echo "$INBOX" | jq -r '.items[]? | "[\(.timestamp)] \(.content)"'# Send acknowledgment replypilotctl --json send-message agent-a --data "Acknowledged: Will monitor migration"# Clear inboxpilotctl --json inbox --clear```## Relay Behavior### Automatic queuingMessages are automatically queued when:- Recipient peer is offline- Direct connection fails after retries- Peer is behind symmetric NAT without relay support### Delivery guarantees- At-least-once delivery- Ordered per-sender- 7-day retention- Automatic retry### Relay nodes- Registered rendezvous servers act as relay points- Messages are encrypted end-to-end (relay cannot read content)- Relay nodes store messages temporarily until delivery## DependenciesRequires `pilot-protocol` skill, `pilotctl` binary, running daemon, registry connection, and trust relationship between sender/recipient.

Frequently asked questions