Pilot Event Bus

Multi-agent event aggregation on shared topics for coordinated workflows. Use this skill when: 1. You need to aggregate events from multiple agents on a shared topic 2. You need to broadcast events to all subscribed agents 3. You need to coordinate state changes across a fleet of agents 4. You need to implement fan-out messaging patterns Do NOT use this skill when: - You need point-to-point messaging (use pilot-protocol connect instead) - You need persistent storage (use pilot-event-log instead) - You need filtered or transformed events (use pilot-event-filter instead)

Multi-agent event aggregation using Pilot Protocol's built-in pub/sub on port 1002.

Commands

Publish Event

pilotctl --json publish <target-hostname> <topic> --data <payload>

Subscribe to Events

pilotctl --json subscribe <target-hostname> <topic> [--timeout <seconds>]

List Trusted Agents

pilotctl --json trust

Find Agent

pilotctl --json find <hostname>

Establish Trust

pilotctl --json handshake <hostname> "reason for trust request"

Workflow Example

#!/bin/bash
# Fleet coordination

pilotctl --json trust | jq -r '.data.trusted[].hostname'

pilotctl --json subscribe fleet-coordinator "tasks.assigned.*" --timeout 300 > /tmp/events.json &

pilotctl --json publish fleet-coordinator "tasks.assigned.worker-1" \
  --data "{\"task_id\":\"task-123\",\"assigned_at\":\"$(date -u +%Y-%m-%dT%H:%M:%SZ)\"}"

jq -r '.data.events[] | "\(.timestamp): \(.topic) -> \(.data)"' /tmp/events.json

Topic Naming

• category.subcategory.event (dotted hierarchy)
• Examples: tasks.assigned.worker-1, metrics.cpu.usage, alerts.error.database
• Wildcards: tasks.*, alerts.error.*, *

Dependencies

Requires pilot-protocol skill, pilotctl, running daemon, and mutual trust between agents.