# Teamharness Communication

Use for TeamHarness message delivery details after a flow has decided a message must be...

- Repository: https://github.com/agentscope-ai/AgentTeams (5913 stars)
- Category: Engineering
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add agentscope-ai/AgentTeams --skill teamharness-communication -g -a claude-code -y`
Codex: `npx skills add agentscope-ai/AgentTeams --skill teamharness-communication -g -a codex -y`
Cursor: `npx skills add agentscope-ai/AgentTeams --skill teamharness-communication -g -a cursor -y`
Gemini CLI: `npx skills add agentscope-ai/AgentTeams --skill teamharness-communication -g -a gemini-cli -y`

## Description

Use for TeamHarness message delivery details after a flow has decided a message must be sent: current-session reply, NO_REPLY, cross-room/cross-channel message tool payloads, PROJECT_REQUESTED task-room handoff, and requester replyRoute reports. Do not use to choose work mode, create rooms, delegate, check, or accept tasks.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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.

## Channel / Room Selection Protocol

Use this protocol after another TeamHarness flow has already decided that a
message should be sent.

1. If the reply belongs in the current runtime session, answer directly.
2. If a project requester report is needed, prefer the project's `reply_route`.
3. Use the Task room for task-visible coordination: task request messages,
   Worker assignments, Worker completion/blocker reports, and downstream
   delegation notices.
4. If the selected destination is an external channel, another Matrix room, or
   another runtime session, use the `message` MCP tool.
5. If the destination is missing or ambiguous, do not guess. Restore project or
   task state first, or ask for the missing routing detail.

Use the Source channel / requester room for direct replies and requester-facing
reports only when the current session or recorded `reply_route` points there.
Use a project `reply_route` for requester-facing reports.

Do not treat a Task room assignment, Worker completion, Worker blocker report,
or downstream delegation as a requester report unless the recorded requester
route is exactly that current room.

## Requester Report Delivery Protocol

The rest: https://github.com/agentscope-ai/AgentTeams/blob/HEAD/plugins/agentteams-teamharness/skills/team/communication/SKILL.md