agent-mailbox
/agent-mailbox
Coordinate two or more agents by exchanging append-only Markdown messages in a Handler-visible shared folder. The transport may be local filesystem, Git, a free registered Lyt (Link Your Think™) vault, or a sync-share such as OneDrive or SMB. The mailbox messages form an auditable causal graph rather than a chat transcript hidden in one runtime.
This is an agent operating protocol. It is not a broker, queue, daemon, authentication boundary, or a message-transport service. For registered cross-machine delivery, use a dedicated transport product and point this skill at the folder it exposes. Use this skill to teach agents how to handshake, divide work, deliver artifacts, listen, react once, recover, resume, and close over the mailbox the Handler supplies.
Structured execution spec: protocol.yon. Read it for the canonical rules and step sequence; this file is explanation. The two must stay in sync — if you edit one, update the other and refresh the @STAMP date.
First exchange: references/QUICKSTART.md. Templates: references/MESSAGE-TEMPLATE.md and references/PRIMER-TEMPLATE.md. Active collaboration resources: resources/INDEX.md. Operating choices: references/OPERATING-MODES.md. Transport and runtime diagnosis: references/CONNECTION-GUIDES.md. Field guidance: references/FIELD-GUIDE.md. Public evidence and known gaps: references/VALIDATION.md.
Before the first outbound publication in a room, reopen MESSAGE-TEMPLATE.md and copy its complete canonical envelope. Do not recreate meta.mailbox from memory. Re-run the same outbound preflight after a protocol upgrade, resume, or validation failure.