markdown-inbox

Name: markdown-inbox
Availability: InStock
Author: Emmitt

Deliver markdown messages between agents via per-agent inbox directories.

1|1|Updated Mar 9, 2026

Search Tags:#messaging #workflow #markdown #agents #inbox #asynchronous #inter-agent

Ready to run

npx skills add https://github.com/EmmittJ/guild --skill markdown-inbox

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: markdown-inbox
Source: https://github.com/EmmittJ/guild/tree/main/plugin/skills/setup/assets/skills/markdown-inbox
Command: npx skills add https://github.com/EmmittJ/guild --skill markdown-inbox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Async inbox for inter-agent messaging, enabling decoupled communication by exchanging markdown files in per-agent folders, with messages deleted after reading and no write conflicts.

Core Features & Use Cases

Async messaging between agents using a shared inbox with per-agent directories.
Message formats include subject, sender, recipient, and context; messages are read at session start and deleted after processing.
Use case: a builder posts a task in the inbox and the orchestrator picks it up in the next session.

Quick Start

Place messages in the inbox directory for the target agent and read them at session start.

Frequently Asked Questions about markdown-inbox

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

FAQPage Schema

How do I enable asynchronous messaging between agents in a multi-agent workflow?▼

Asynchronous messaging between agents is facilitated by delivering markdown-based messages through a per-agent inbox. This decouples communication, allowing agents to exchange tasks and context without blocking execution.

What is the best way to decouple inter-agent communication without write conflicts?▼

The best way to decouple inter-agent communication without write conflicts is exchanging markdown files in per-agent directories. Messages are written to the target agent's folder and deleted after reading to prevent conflicts.

How do I set up an asynchronous inbox for inter-agent messaging?▼

To set up an async inbox, define an inbox_root path and create per-agent subdirectories. Place messages in the target agent's directory using one file per timestamped filename, then read them at session start.

Does inter-agent messaging delete messages after they are read?▼

Yes, inter-agent messaging deletes message files after reading. Messages formatted with subject, sender, recipient, and context are read at session start and immediately deleted after processing.

Can I use markdown files to pass context and tasks to an orchestrator agent?▼

Yes, you can use markdown files to pass context and tasks to an orchestrator agent. A builder agent posts a task message in the orchestrator's inbox directory, which the orchestrator picks up in the next session.