CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

teamharness-task-delegation

Use when you act as Leader to turn ready Quick Task or Project Work state into Worker task instructions, send assignment messages, check submitted results, and define completion/blocker report contracts. Do not use to create projects, create rooms, or execute Worker tasks.

Quality

87%

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

The canonical home for this skill is teamharness-task-delegation in agentscope-ai/AgentTeams

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

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

The body is highly actionable, with copy-paste JSON call payloads, exact message templates, and explicit validation and acceptance branches for the delegation workflow. Its main weakness is redundancy: the assignment-notification behavior is explained in three separate sections and the completion-report template appears twice, which costs token efficiency and slightly scatters the structure.

Suggestions

Consolidate the delegate_task auto-notify behavior into a single section — it is currently explained in the 'Before delegation' checklist (item 6), 'Assignment Message', and 'Post-Action Notification'.

State the create_quick_project no-auto-notify caveat once (in 'Assignment Message') instead of repeating it in 'Delegate Only Ready Nodes'.

Trim the duplicated completion-report template: keep the standalone 'Task Spec Completion Report' block and shorten the inline spec example in 'Delegate Task' to reference it.

DimensionReasoningScore

Conciseness

Mostly tight operational guidance with no concept-teaching padding, but the delegate_task auto-notify behavior is stated three times ("mentions the assigned Worker automatically", "automatically notifies the assigned Worker", "sends the Worker assignment automatically") and the create_quick_project no-notify caveat twice, so it could be meaningfully tightened.

3 / 5

Actionability

Fully executable guidance: copy-paste JSON payloads for delegate_task and check_task, exact file paths (shared/tasks/{task-id}/spec.md), exact assignment/completion message templates, and an explicit accepted-status list cover the common cases with no gaps.

5 / 5

Workflow Clarity

Clear sequence with explicit validation and feedback loops: a numbered pre-delegation checklist, the branch "If `effective` is false, do not accept the task. Tell the Worker what is missing and wait for a corrected result", and defined terminal-state handling (INTERRUPTED treated like BLOCKED).

5 / 5

Progressive Disclosure

A well-sectioned, single-level document with clearly signaled sibling-skill pointers (teamharness-project-management, teamharness-task-execution, teamharness-roomflow) and no bundle files; the repeated notification content spread across three sections is a minor organization gap keeping it below a 5.

4 / 5

Total

17

/

20

Passed

Description

87%Weight 40%Scale 1-5

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 clearly and explicitly states both what the skill does and when to use it, with concrete actions and an explicit exclusion boundary. The second-person "Use when you act as Leader" phrasing and some system-specific jargon keep specificity and trigger-term quality slightly below the top anchors.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("turn ready Quick Task or Project Work state into Worker task instructions, send assignment messages, check submitted results, and define completion/blocker report contracts"), which matches the 5 anchor, but the second-person phrasing "Use when you act as Leader" triggers the rubric's mandated 1-point specificity reduction.

4 / 5

Completeness

Explicitly answers both what (creating Worker task instructions, sending assignments, checking results, defining report contracts) and when ("Use when you act as Leader to turn ready Quick Task or Project Work state into...") with a concrete trigger, so it is a clear 5 rather than a 4 where the when-clause is only implicit or loosely specified.

5 / 5

Trigger Term Quality

Good natural terms for the niche ("task instructions", "assignment messages", "check submitted results", "Worker task"), but it leans on system jargon ("Project Work state", "Quick Task") and omits common phrasings like "delegate" or "assign a task".

4 / 5

Distinctiveness Conflict Risk

Clear niche (Leader-side task delegation) with an explicit negative boundary ("Do not use to create projects, create rooms, or execute Worker tasks") that separates it from sibling skills, leaving minimal conflict risk.

5 / 5

Total

18

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

agentscope-ai/AgentTeams

Path

plugins/agentteams-teamharness/skills/team/task-delegation/SKILL.md

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.