inbox

Send direct messages and broadcasts between agents via atomic file writes.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/kinnerkarmanish/mak --skill inbox-kinnerkarmanish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: inbox
Source: https://github.com/kinnerkarmanish/mak/tree/main/library/skills/coordination/inbox
Command: npx skills add https://github.com/kinnerkarmanish/mak --skill inbox-kinnerkarmanish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill provides a reliable, file-based messaging backbone for coordinating multiple autonomous agents. It enables direct messaging, broadcasts, and a complete message history with atomic writes and per-inbox organization.

Core Features & Use Cases

  • Direct messages: send private notes to a specific agent.
  • Broadcasts: relay information to all registered agents.
  • Message history: maintain an event log for debugging and traceability.
  • Atomic delivery: ensure no partial messages are read during writes.

Quick Start

Send a direct message to an agent named 'researcher' and verify it arrives in their inbox.

Frequently Asked Questions about inbox

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

FAQPage Schema
How do I set up reliable inter-agent messaging for a coordinated workflow?

Reliable inter-agent messaging uses file-based direct messages and broadcasts with atomic writes. It requires per-agent inbox directories and a shared event log to ensure traceability and prevent partial reads during writes.

What is atomic file delivery and why is it needed for agent coordination?

Atomic file delivery ensures no partial messages are read during writes by using atomic file operations. This guarantees that autonomous agents only access fully written messages in their respective inboxes.

Can I broadcast a message to all registered agents using a file-based system?

Yes, you can broadcast information to all registered agents. The system organizes messages into per-agent inbox directories, ensuring every targeted agent receives the broadcasted information reliably.

How do I trace message history when debugging multi-agent communication?

You trace message history by consulting the shared event log. This event log maintains a complete record of all direct messages and broadcasts, providing full traceability for debugging coordinated workflows.

What's the best way to coordinate multiple autonomous agents without message loss?

The best way to prevent message loss is using a file-based messaging backbone with atomic writes. This approach guarantees reliable delivery for direct messages and broadcasts across per-agent inbox directories.

Does inter-agent messaging require external dependencies or database setups?

No external dependencies are required. The messaging system relies entirely on file-based operations, utilizing per-agent inbox directories and a shared event log to coordinate autonomous agents without a database.