teamharness-task-delegation

Use when a Leader turns ready Quick Task or Project Work state into Worker task instructions, sends assignment messages, checks submitted results, and defines completion/blocker report contracts. Do not use to create projects, create rooms, or execute Worker tasks.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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.

Highly actionable content with concrete payloads, a clear sequenced workflow, and explicit validation/feedback loops. The main weakness is repetitive re-explanation of the auto-notification behavior across three sections.

Suggestions

Consolidate the 'delegate_task auto-notifies / do not send a second message' guidance into one section and reference it from the others to remove triplicate repetition (improves conciseness).

Deduplicate the Completion Report template: keep it once as its own section and have the delegate_task JSON spec reference it rather than inlining the full block twice (improves progressive_disclosure).

Consider moving the literal Result Contract format and accepted-status list into a short reference block or keeping them inline but cross-linked, to tighten the single-file structure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable JSON and tight contracts, but the auto-notification behavior ('delegate_task automatically notifies the assigned Worker ... do not send a second assignment message') is re-explained across the 'Delegate Only Ready Nodes', 'Assignment Message', and 'Post-Action Notification' sections, which could be tightened; not a 4 because the repetition is noticeable rather than minor.	3 / 5
Actionability	Provides copy-paste-ready JSON payloads for delegate_task and check_task, a concrete task spec template, an exact completion-report line, and a literal result contract format covering the common cases.	5 / 5
Workflow Clarity	Sequenced with a 6-step before-delegation checklist, an explicit validation checkpoint via check_task's effective field, and a feedback loop ('If effective is false ... tell the Worker what is missing and wait for a corrected result') for error recovery.	5 / 5
Progressive Disclosure	Well-organized single file with clearly signaled sections and no nested external references (no bundle files exist); not a 5 because the completion-report template appears both inline in the spec JSON and as its own section, a minor organization gap.	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.

A strong, third-person description that clearly states both capability and trigger conditions while explicitly delineating scope from related skills. Minor gains are possible only in trigger-term breadth.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('turns ready Quick Task or Project Work state into Worker task instructions, sends assignment messages, checks submitted results, and defines completion/blocker report contracts'), with only minor coverage gaps; not a 5 because the actions are scoped to one workflow rather than a broad comprehensive catalog.	4 / 5
Completeness	Explicitly answers both what ('turns ... state into Worker task instructions, sends assignment messages, checks submitted results, and defines completion/blocker report contracts') and when ('Use when a Leader turns ready Quick Task or Project Work state ...'), with concrete trigger phrases and an explicit do-not-use clause.	5 / 5
Trigger Term Quality	Uses natural domain terms a Leader would say ('Quick Task', 'Project Work', 'Worker task instructions', 'assignment messages', 'submitted results'); good coverage but a few natural phrasings or synonyms are missing, so not a 5.	4 / 5
Distinctiveness Conflict Risk	The explicit 'Do not use to create projects, create rooms, or execute Worker tasks' carves a clear niche apart from sibling teamharness skills, minimizing conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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/teamharness/skills/team/task-delegation/SKILL.md
Commit: 223ddc2

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.