CtrlK
BlogDocsLog inGet started
Tessl Logo

teamharness-roomflow

Use for TeamHarness room classification and Matrix task-room setup: roomflow describe_room, roomflow create_task_room, source/requester room vs task room detection, project-scoped task-room reuse, and invite handling. Do not use for projectflow, taskflow, or message delivery.

57

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/teamharness/skills/team/roomflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-structured with specific tool guidance, but lacks a complete invocation example and an explicit validation feedback loop, capping actionability and workflow clarity at 2.

Suggestions

Add a concrete invocation example for 'roomflow create_task_room' showing the argument structure (projectId, source metadata, worker user IDs) so the guidance is copy-paste ready.

Insert an explicit validation checkpoint after 'roomflow describe_room' (e.g. confirm the returned classification before proceeding to create_task_room) with a retry on mismatch.

Clarify the handoff sequence end-to-end (create task room → use returned room for project state → delegate to Workers) as a numbered checklist.

DimensionReasoningScore

Conciseness

The body is lean and instruction-focused with no padding or explanation of concepts Claude already knows; every line earns its place.

3 / 3

Actionability

Concrete tool names and parameters are given ('roomflow create_task_room', 'projectId', DingTalk 'sourceRoomId' and 'sender', Worker Matrix user IDs), but no complete invocation template or argument-structure example is shown, leaving the guidance executable in intent but incomplete in form.

2 / 3

Workflow Clarity

A clear two-phase sequence (describe → create/reuse) with classification criteria is present, but there is no explicit validate→fix→retry feedback loop, so checkpoints remain implicit.

2 / 3

Progressive Disclosure

The skill is under 50 lines, has no bundle files requiring references, and is organized into well-signaled sections ('## Describe Room', '## Create Or Reuse Task Room'), satisfying the simple-skill rule for a top score.

3 / 3

Total

10

/

12

Passed

Description

57%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and well-bounded with clear exclusions, but its imperative voice, jargon-heavy triggers, and lack of an explicit 'Use when' clause keep it from the top tier.

Suggestions

Rewrite in third person (e.g. 'Classifies Matrix rooms and sets up task rooms…') instead of the imperative 'Use for…' to avoid the voice penalty.

Add an explicit 'Use when a Leader needs to identify the current Matrix room or prepare a task room…' trigger clause to raise completeness.

Soften jargon by pairing internal terms with natural phrases users would say (e.g. 'task room setup', 'which Matrix room am I in').

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('roomflow describe_room', 'roomflow create_task_room', 'project-scoped task-room reuse', 'invite handling'), but the imperative 'Use for…' opening is second-person voice, triggering the rubric's −1 specificity penalty from a baseline of 3.

2 / 3

Completeness

The 'what' is clearly specified via the enumerated actions, but there is no explicit 'Use when…' trigger clause describing the triggering situation, capping completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

Terms like 'roomflow', 'source/requester room', and 'task-room' are relevant to the niche but are domain jargon rather than natural phrases a user would say, and common variations are missing.

2 / 3

Distinctiveness Conflict Risk

The explicit exclusion 'Do not use for projectflow, taskflow, or message delivery' carves out a clear niche, making conflict with sibling skills unlikely.

3 / 3

Total

9

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
agentscope-ai/AgentTeams
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.