message-bus

Facilitate asynchronous agent communication via journal-based topic and inbox messaging.

3|2|Updated May 12, 2026
One-click install
npx skills add https://github.com/kriscendobot/garden --skill message-bus-kriscendobot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: message-bus
Source: https://github.com/kriscendobot/garden/tree/main/skills/message-bus
Command: npx skills add https://github.com/kriscendobot/garden --skill message-bus-kriscendobot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of coordinating communication between multiple autonomous agents running across different hosts by providing a robust, journal-based messaging system.

Core Features & Use Cases

  • Topic-based Fan-out: Enables broadcast messaging where multiple agents can subscribe to specific roles or global topics.
  • Directed Point-to-Point Messaging: Facilitates secure, stateful communication between specific agents using an inbox mechanism.
  • Maintainer Channel: Provides a dedicated interface for human users to interact with agents, allowing for message replies, archiving, and status updates.

Quick Start

Use the message-bus skill to send a broadcast notification to all active agents regarding the current job status.

Frequently Asked Questions about message-bus

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

FAQPage Schema
How do I coordinate asynchronous communication between distributed agents?

Agent-to-agent coordination uses a journal-based messaging architecture that supports both topic-based fan-out broadcasting and directed point-to-point inbox delivery for reliable task coordination.

What is the best way to broadcast a message to multiple autonomous agents at once?

Broadcast messaging across agents is handled through topic-based fan-out, enabling multiple agents to subscribe to specific roles or global topics and receive notifications simultaneously.

Can I send a directed message to one specific agent instead of broadcasting?

Directed point-to-point messaging uses a dedicated inbox mechanism to facilitate secure, stateful communication between specific agents without relying on broadcast channels.

How does cross-agent referencing work when agents share GitHub issues and pull requests?

Cross-agent referencing enforces strict validation of issue and pull request references, ensuring that distributed agents maintain unambiguous links to shared GitHub resources.

Is there a way for human users to interact with autonomous agents through the messaging system?

A dedicated maintainer channel provides an interface for human users to interact with agents, supporting message replies, archiving, and status updates within the journal-based system.

Do I need any external dependencies to set up agent-to-agent messaging?

No external dependencies are required; the messaging system operates as a standalone skill, relying entirely on its internal journal-based architecture to manage communication between distributed agents.