apm-communication

Defines agent communication standards and a file-based Message Bus protocol for inter-agent messaging.

1|Updated Dec 13, 2025
One-click install
npx skills add https://github.com/ZK-Theory/TDL --skill apm-communication-zk-theory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apm-communication
Source: https://github.com/ZK-Theory/TDL/tree/main/.agents/skills/apm-communication
Command: npx skills add https://github.com/ZK-Theory/TDL --skill apm-communication-zk-theory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating multiple AI agents in a session requires consistent communication rules and a reliable way to pass tasks and reports between agents without losing or overwriting messages. ## Core Features & Use Cases - Communication Standards: Defines how agents talk to users (visible reasoning, natural language, terminology boundaries) and how they write structured artifacts. - File-Based Message Bus: Specifies a protocol using per-agent directories under .apm/bus/ with task.md and report.md files, including write ownership, collision safety, and identity validation rules. - External Agent Integration: A companion guide lets non-APM agents join the bus by creating their own slug directory and exchanging task and report files. - Use Case: A Manager agent assigns work to a Frontend Agent by writing to .apm/bus/frontend-agent/task.md; the Worker reads it, completes the task, and reports back via report.md without message collisions. ## Quick Start Ask the agent to set up the APM message bus directories and explain how to send a task message to a worker agent.

Frequently Asked Questions about apm-communication

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

FAQPage Schema
How do agents communicate with each other in APM?

Agents communicate through a file-based Message Bus under `.apm/bus/`, where each agent has a directory containing `task.md` for incoming assignments and `report.md` for outgoing reports. Messages are written, read, and cleared according to the bus protocol rules.

How do I integrate an external agent with the APM message bus?

Create a slug-named directory under `.apm/bus/` with `task.md` and `report.md` files, then write reports to `report.md` and direct the user to run `/apm-5-check-reports <your-agent-slug>` in the Manager's chat. External agents participate at the communication level only.

What happens when two messages collide in the bus?

A bus file may only be overwritten when it is the same logical message being deliberately updated and all identity fields match. Otherwise the write is refused, the collision is reported to the User or Manager, and the existing content is preserved.

How are agent slugs and identities resolved in APM?

Slugs derive from Worker names by lowercasing and replacing spaces with hyphens, such as `frontend-agent`. Agent ID arguments resolve against `.apm/bus/` directory names by exact match, then prefix, then best plausible match, asking the user when ambiguous.

What are the limitations of the file-based message bus?

Each bus file holds at most one message at a time, so delivery depends on files being read and cleared after successful processing. Reading a file does not prove ownership, so writers must verify identity fields before overwriting any non-empty slot.