mailbox

Enforce an append-only shared mailbox for standardized agent team communication.

89|17|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/statsclaw/statsclaw --skill mailbox-statsclaw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mailbox
Source: https://github.com/statsclaw/statsclaw/tree/main/skills/mailbox
Command: npx skills add https://github.com/statsclaw/statsclaw --skill mailbox-statsclaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI agent teams working on isolated statistical software development pipelines lack a standardized, tamper-proof method to share critical updates, user input requests, and interface change notifications across teammates, risking lost messages, broken downstream workflows, and incomplete audit trails.

Core Features & Use Cases

  • Append-Only Mailbox Structure: Prevents message deletion, editing, or reordering to maintain a permanent, unaltered audit trail of all cross-teammate communication.
  • Standardized Message Types: Supports three distinct message types (INFO, HOLD_REQUEST, INTERFACE_CHANGE) with clear routing rules to ensure the team leader dispatches the correct actions for each update.
  • Clear Leader Responsibilities: Defines exact steps for the leader to process mailbox messages, including forwarding hold requests to users and notifying downstream agents of interface changes.
  • Use Case: When a builder renames a core function used by the tester and scriber, they send an INTERFACE_CHANGE message to the mailbox; the leader automatically includes this update in the dispatch prompts for both downstream teammates, eliminating broken dependencies.

Quick Start

Use the mailbox protocol to send a HOLD_REQUEST message to the team leader when you need user input to proceed with your assigned development task.

Frequently Asked Questions about mailbox

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

FAQPage Schema
How do I maintain an audit trail for inter-agent messaging in isolated workflows?▼

You can maintain an audit trail for inter-agent messaging by enforcing an append-only shared mailbox structure that prevents message deletion, editing, or reordering across teammates.

What is the best way to coordinate interface change notifications across AI agent teams?▼

The best way to coordinate interface changes is sending an INTERFACE_CHANGE message to the mailbox, allowing the team leader to automatically include updates in downstream agent dispatch prompts.

How does a standardized mailbox protocol handle hold requests in statistical development pipelines?▼

A standardized mailbox protocol handles hold requests by requiring agents to send a HOLD_REQUEST message to the team leader, who then processes the mailbox and forwards the request to the user.

Can I use an append-only mailbox structure for workflow coordination without external dependencies?▼

Yes, you can use an append-only mailbox structure for workflow coordination without external dependencies, as it operates independently to enforce standardized message formatting and clear routing rules.

Why does cross-agent communication fail in isolated AI agent teams without a shared mailbox?▼

Cross-agent communication fails without a shared mailbox because isolated teams lack a tamper-proof method to share critical updates, risking lost messages, broken downstream workflows, and incomplete audit trails.

What message types does this mailbox protocol support for multi-agent workflow coordination?▼

The mailbox protocol supports three distinct message types for workflow coordination: INFO, HOLD_REQUEST, and INTERFACE_CHANGE, each with clear routing rules for team leader dispatch actions.