teamharness-roomflow

Classifies Matrix rooms and creates project-scoped task rooms for TeamHarness workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about teamharness-roomflow

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

FAQPage Schema
How do I create a task room in Matrix for a project?

Call roomflow create_task_room with a stable projectId before creating any project or task state. The tool normalizes the Matrix room name to TASK:<projectId> and reuses an existing task room only when the project id matches.

How to tell if a Matrix room is a task room or source room?

Use roomflow describe_room to classify the room from Matrix state. A room named TASK:<projectId> or carrying a Project/Task marker in its topic or tags is a task room; external channels or DM/Team-named rooms are source rooms.

Can two projects from the same DingTalk group share a task room?

No. Task-room reuse is decided only by projectId, never by source room or sender identity. Different projects from the same DingTalk group or the same person each get their own task room.

Why should room purpose not be inferred from joined-room IDs?

Joined-room IDs carry no semantic information about a room's role, so classification from them is unreliable. The Skill classifies rooms from Matrix names, topics, and tags instead.

When should I not use the roomflow skill?

Do not use it for projectflow, taskflow, or message delivery work. It only covers room classification and task-room setup that happen before project or task state exists.