Communication

This skill expands the TEAMS.md Communication Contract.

It only handles message delivery protocols. It does not choose Direct Reply, Quick Task, or Project Work. It does not create rooms, delegate tasks, check Worker results, or accept project state.

For ordinary direct replies and lightweight one-off answers in the current room/session, answer directly. Use the message MCP tool only when a message must leave the current runtime conversation.

Use NO_REPLY exactly when the current event is a low-information acknowledgement, self echo, or non-actionable mention-only message. Do not add extra explanation to NO_REPLY.

Prevent ping-pong loops. Do not let acknowledgements, mention-only messages, or same-room status echoes create repeated cross-room or cross-agent replies.