What problem does it solve?
When a Leader agent receives work in a Matrix room, it must know whether that room is a source/requester room or an existing task room, and it needs a dedicated task room before any project or task state can be created. This Skill removes ambiguity in room classification and prevents duplicate or misassigned task rooms.
Core Features & Use Cases
- Room Classification: Uses
roomflow describe_room to distinguish source/requester rooms from task rooms based on Matrix room names, topics, and tags rather than joined-room IDs.
- Task Room Creation and Reuse: Uses
roomflow create_task_room with a stable projectId to normalize room names to TASK:<projectId> and reuse task rooms only by project id.
- Source Metadata Preservation: Passes source metadata such as DingTalk
sourceRoomId and sender unchanged so project state retains the requester route.
- Use Case: A Leader receives a request in a DingTalk-connected Matrix room, classifies the room, creates a task room for the project, invites the required Workers by their full Matrix user IDs, and uses that room for handoff, delegation, and completion reports.
Quick Start
Ask the agent to classify the current Matrix room and create or reuse a task room for project 'website-redesign' before starting any task delegation.