agent-team-message-send

Send compact run-scoped messages between agents with required fields.

2|Updated May 10, 2026

Search Tags:#workflow #communication #orchestration #inbox #message #send #agent-team

Ready to run

npx skills add https://github.com/tae2089/agent-team --skill agent-team-message-send

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agent-team-message-send
Source: https://github.com/tae2089/agent-team/tree/main/skills/agent-team-message-send
Command: npx skills add https://github.com/tae2089/agent-team --skill agent-team-message-send

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinators and agents often need to exchange concise, state-changing messages within a specific workflow run to coordinate tasks and updates.

Core Features & Use Cases

Send compact messages with run, from, to, kind, and body fields.
Optional task scope, message id, and metadata support for traceability.
Use cases include status updates, quick clarifications, and contract changes within a run.

Quick Start

Run the agent-team message send command to deliver a compact message to a recipient.

Frequently Asked Questions about agent-team-message-send

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

FAQPage Schema

How do I send status updates between agents in a workflow run?▼

You can send status updates between agents by delivering compact run-scoped messages with required fields: run, from, to, kind, and body. This ensures clear communication and task coordination within a single workflow execution.

What is a run-scoped message in agent orchestration?▼

A run-scoped message in agent orchestration is a concise, state-changing communication exchanged within a specific workflow run. It allows coordinators and agents to coordinate tasks, provide status updates, and manage contract changes effectively.

How do I include task context and metadata in agent messages?▼

You include task context and metadata in agent messages by utilizing the optional task, id, and metadata fields supported by the message sender. This provides richer traceability and contextual data for inter-agent communication within the run.

Can I use this for contract changes and task coordination within a single run?▼

Yes, you can use this for contract changes and task coordination within a single run. It is specifically applied to workflows requiring status updates, quick clarifications, and contract modifications between coordinating agents.

What fields are required for inter-agent communication in a workflow?▼

The required fields for inter-agent communication in a workflow are run, from, to, kind, and body. These mandatory fields ensure compact, properly routed, and structured messages between agents during task execution.