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.