agent-team-inbox

Coordinate daemonless messaging and inbox management for agent-team workflows.

2|Updated May 10, 2026
One-click install
npx skills add https://github.com/tae2089/agent-team --skill agent-team-inbox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-team-inbox
Source: https://github.com/tae2089/agent-team/tree/main/skills/agent-team-inbox
Command: npx skills add https://github.com/tae2089/agent-team --skill agent-team-inbox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables daemonless, asynchronous messaging and inbox management for agent-team workflows, including checkpoints, acknowledgements, and contract-change notifications. It relies on the shared agent-team components.

Core Features & Use Cases

  • Message and inbox commands provide a lightweight interface to send and read messages within a run or task context.
  • Checkpoint and acknowledgement support helps track progress and confirm handling of messages to ensure synchronization without a daemon.
  • Contract-change notifications keep involved agents informed about updates to the workflow contract, enabling coordinated changes.
  • Preresquisite loading of agent-team-shared ensures access to shared utilities and consistent state handling.

Quick Start

Invoke the agent-team message and inbox commands to establish a simple asynchronous communication channel and verify inbox states.

Frequently Asked Questions about agent-team-inbox

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

FAQPage Schema
How do I set up asynchronous messaging between agents without a daemon?

Asynchronous messaging between agents without a daemon is managed through run-scoped inbox commands and local durable state. This enables agents to send, read, and acknowledge messages directly without requiring a background service.

What is daemonless inbox management for agent-team workflows?

Daemonless inbox management for agent-team workflows is a coordination mechanism that handles asynchronous messages, checkpoints, and contract-change notifications. It uses a local durable state model to synchronize tasks without a persistent background service.

How do I send and read messages within an agent-team task context?

To send and read messages within an agent-team task context, you invoke the message and inbox commands via the CLI. This lightweight interface establishes asynchronous communication channels and verifies inbox states for the current run.

Do I need to load agent-team-shared before using inbox commands?

Yes, you need to load agent-team-shared as a prerequisite before using inbox commands. Loading this shared component ensures access to shared utilities and consistent state handling across the agent-team workflow environment.

How do contract-change notifications work in asynchronous agent workflows?

Contract-change notifications in asynchronous agent workflows keep involved agents informed about updates to the workflow contract. This enables coordinated changes across agent-team tasks while maintaining synchronization through local durable state.

Are there limitations to using daemonless messaging for agent-team coordination?

Daemonless messaging for agent-team coordination relies entirely on local durable state rather than a centralized background service. It is scoped to asynchronous run-scoped communications, meaning synchronization depends on explicit inbox checks and acknowledgements.