task-management

Use before any Leader taskflow call or task-level workflow involving delegating a ready DAG or Loop node, writing task meta/spec, checking a Worker task result, handling result statuses, task directory ownership, or Worker result contracts. Always use this skill when the request mentions delegate_task, check_task, task result.md, task spec.md, BLOCKED, REVISION_NEEDED, INTERRUPTED, SUCCESS, or assigning/delegating a Worker task.

Quality

90%

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 and well-sequenced content with concrete payloads and validation checkpoints, slightly held back by repeated cautionary statements and overlap between the inline flows and the bundled reference file.

Suggestions

Consolidate the repeated 'do not send a second assignment message' guidance into one canonical location instead of restating it in the Tool Boundary, delegate, and after-delegation sections.

Either defer the detailed delegate/check walk-through to references/dag-tasks.md or trim the reference to non-overlapping detail, so the body and reference are not near-duplicates.

Merge the recurring 'do not manually edit task files / use taskflow only' and 'do not mark [x] just because the Worker wrote SUCCESS' rules into single stated-once sections.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean operational directives without concept over-explanation, but several cautions are restated multiple times (the 'no second assignment message' rule appears at three points, the 'no manual file edits' and 'don't mark [x] just because SUCCESS' rules each recur), which could be consolidated.	3 / 5
Actionability	Provides copy-paste-ready JSON payloads for delegate_task, check_task, and ready_nodes, an executable bash block for Worker localpart lookup, and concrete path/status tables covering the common cases.	5 / 5
Workflow Clarity	The 'Check A Submitted Task' flow is a 9-step sequence with explicit validation checkpoints (paused-project stop, check_task validation, blocking sync-failure stop) and clear feedback loops; the delegate flow is similarly sequenced.	5 / 5
Progressive Disclosure	Clear section structure with a single one-level-deep, well-signaled reference (references/dag-tasks.md, a real file), but that reference substantially duplicates the body's delegate/check flows rather than cleanly separating detail.	4 / 5
	Total	17 / 20 Passed

Description

100%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 description: it states concrete capabilities, gives an explicit 'Use when' trigger clause with exact tool-action and status tokens, and carves out a niche clearly separated from related skills. No verbosity or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — delegating a ready DAG/Loop node, writing task meta/spec, checking a Worker result, handling result statuses, task directory ownership, and Worker result contracts — giving comprehensive rather than 1-2 action coverage.	5 / 5
Completeness	Explicitly answers both 'what' (first sentence enumerates the task-level actions) and 'when' ('Always use this skill when the request mentions ...') with concrete trigger phrases, matching the anchor.	5 / 5
Trigger Term Quality	Surfaces the exact tokens a user would naturally say — delegate_task, check_task, task result.md, task spec.md, BLOCKED, REVISION_NEEDED, INTERRUPTED, SUCCESS — covering the full set including status synonyms.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear task-execution niche keyed on tool actions delegate_task/check_task, distinct from the sibling project-management skill, with minimal overlap risk.	5 / 5
	Total	20 / 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: manager/agent/team-leader-agent/skills/task-management/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.