teamharness-communication

Delivers cross-room and cross-channel messages using Matrix and DingTalk routing protocols.

5.5k|677|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/agentscope-ai/HiClaw --skill teamharness-communication
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: teamharness-communication
Source: https://github.com/agentscope-ai/HiClaw/tree/main/plugins/teamharness/skills/team/communication
Command: npx skills add https://github.com/agentscope-ai/HiClaw --skill teamharness-communication

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating multi-agent teams across Matrix rooms, DingTalk sessions, and other channels requires precise message routing; sending to the wrong room or losing the requester's reply route breaks project reporting and creates ping-pong loops between agents.

Core Features & Use Cases

  • Channel and Room Selection Protocol: Decides whether to reply directly in the current session, use a task room, or invoke the message MCP tool for cross-room and cross-channel delivery.
  • PROJECT_REQUESTED Handoff: Sends a structured self-trigger payload that hands Quick Task or Project Work from a source session into a Matrix task room while preserving the requester replyRoute.
  • Requester Report Delivery: Delivers project progress reports to the recorded replyRoute on Matrix, DingTalk, Feishu, or legacy requester encodings, with optional DingTalk sender mentions.
  • Use Case: A Leader agent finishes a project in a Matrix task room and must report back to the original DingTalk requester; this Skill supplies the exact message tool payload with the persisted replyRoute so the report reaches the right session.

Quick Start

Use the teamharness-communication skill to send the project completion report to the requester using the recorded replyRoute.

Frequently Asked Questions about teamharness-communication

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

FAQPage Schema
How do I send a message from a Matrix task room back to a DingTalk requester?

Send a message tool payload with the recorded replyRoute containing channel dingtalk, targetUser, and targetSession. Add mentionSender true only when the original DingTalk sender should be notified, and do not mark the report sent if delivery fails.

How do I hand off a project request to a Matrix task room?

Send a PROJECT_REQUESTED self-trigger payload with channel matrix, the task room as target, and a structured replyRoute object. The message field must be a JSON object, not a serialized string, so the tool can attach the TeamHarness trigger marker.

When should I use the message MCP tool instead of a direct reply?

Use the message tool only for explicit cross-room, cross-channel, or cross-session sends. For ordinary replies in the current room or session, answer directly so the runtime emits a single formatted event.

When should I use NO_REPLY in TeamHarness communication?

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, and avoid creating repeated cross-room replies from acknowledgements.

What happens if the requester replyRoute is missing or ambiguous?

Do not guess missing channel, user, room, or session values. Restore project or task state first, or ask for the missing routing detail; legacy requester strings are parsed only when they match known Matrix or DingTalk encodings.

Can I attach workspace files to DingTalk or Feishu requester reports?

No. The artifact tool publishes Matrix room files only, so for DingTalk, Feishu, or WeChat reports include the shared file paths in the report text and note they are available from the shared workspace or object-storage view.