How do I install the Pilot Event Bus skill?

Run npx skillmds@latest add teoslayer/pilot-event-bus 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 Event Bus 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 Event Bus?

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

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

Who published Pilot Event Bus?

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

Pilot Event Bus by teoslayer — Agent Skill

Name: Pilot Event Bus
Author: TeoSlayer

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)

TeoSlayer 8509f42 2 files · 2.6 KB Updated Sep 17, 2026

File contents

Pilot Event Bus

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.

---name: pilot-event-busdescription: 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)license: AGPL-3.0---# Pilot Event BusMulti-agent event aggregation using Pilot Protocol's built-in pub/sub on port 1002.## Commands### Publish Event```bashpilotctl --json publish <target-hostname> <topic> --data <payload>```### Subscribe to Events```bashpilotctl --json subscribe <target-hostname> <topic> [--timeout <seconds>]```### List Trusted Agents```bashpilotctl --json trust```### Find Agent```bashpilotctl --json find <hostname>```### Establish Trust```bashpilotctl --json handshake <hostname> "reason for trust request"```## Workflow Example```bash#!/bin/bash# Fleet coordinationpilotctl --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.*`, `*`## DependenciesRequires pilot-protocol skill, pilotctl, running daemon, and mutual trust between agents.

Frequently asked questions

Pilot Event Bus

File contents

Pilot Event Bus

Commands

Publish Event

Subscribe to Events

List Trusted Agents

Find Agent

Establish Trust

Workflow Example

Topic Naming

Dependencies

Related skills

Frequently asked questions

How do I install the Pilot Event Bus skill?

What does the Pilot Event Bus skill do?

Is Pilot Event Bus safe to use?

Which AI agents work with Pilot Event Bus?

Is Pilot Event Bus free to use?

Who published Pilot Event Bus?