mpi-message

Create and update MPI coordination message records under .agents/mpi-kanban/state/messages/.

1|Updated May 13, 2026

Search Tags:#messaging #coordination #asynchronous #workflows #mpi #in-project

Ready to run

npx skills add https://github.com/MadPonyInteractive/mpi-kanban --skill mpi-message

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mpi-message
Source: https://github.com/MadPonyInteractive/mpi-kanban/tree/main/skills/mpi-message
Command: npx skills add https://github.com/MadPonyInteractive/mpi-kanban --skill mpi-message

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate asynchronous, same-filesystem coordination messages between MPI agents by creating and organizing durable coordination records under .agents/mpi-kanban/state/messages/. This enables parallel work without collisions and keeps agents aligned on progress.

Core Features & Use Cases

Send and manage tells to other agents, read inbox messages, acknowledge, reply, and resolve coordination tasks.
Route messages to a known peer workspace while preserving a single coordination state per work context.

Quick Start

Tell an agent to initiate a coordination message and then verify the inbox for a response.

Frequently Asked Questions about mpi-message

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

FAQPage Schema

How do I coordinate asynchronous messaging between agents on the same filesystem?▼

You can coordinate asynchronous messaging between agents by creating and updating structured message records under .agents/mpi-kanban/state/messages/, ensuring parallel work proceeds without collisions.

What operations are supported for durable agent coordination messages?▼

Supported operations for durable coordination messages include tell, inbox, ack, reply, resolve, and routing to a peer workspace to keep all agents aligned on progress.

How does the agent messaging workflow ensure safe concurrency?▼

Safe concurrency is ensured by using shared references from mpi-lib alongside a validated claimed-file workflow, which prevents write collisions when multiple agents mutate coordination state.

Do I need to resolve the mpi-lib root before sending coordination messages?▼

Yes, resolving the mpi-lib root and reading coordination references are required prerequisites before mutating any state to send or manage asynchronous agent messages.

When do I need durable coordination records for asynchronous workflows?▼

Durable coordination records are needed when multiple agents work in parallel on the same filesystem and must stay aligned on task progress without overwriting each other's state updates.

Can I route coordination messages to a peer workspace?▼

Yes, you can route messages to a known peer workspace while preserving a single coordination state per work context to maintain consistent asynchronous task alignment.