task-coordination-strategies

Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.

1.10x

Quality

76%

Does it follow best practices?

Impact

92%

1.10x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/agent-teams/skills/task-coordination-strategies/SKILL.md

Quality

Content

65%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 concise, actionable, and well-organized with real supporting bundle files. Its main weaknesses are missing validation/feedback checkpoints in the rebalancing workflow and the absence of inline navigation to the existing reference files.

Suggestions

Add inline links to the bundled reference files where relevant (e.g., 'See references/dependency-graphs.md for more patterns') so progressive disclosure is clearly signaled.

Insert an explicit validation/verification checkpoint into the Rebalancing Steps workflow (e.g., confirm the reassigned task's blockedBy dependencies are still satisfiable before notifying teammates).

Move the full inline task-description template into a reference file and keep only a short pointer plus one minimal example in SKILL.md to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	Lean and well-structured with no padding of concepts Claude already knows; tables and diagrams are tight. A few sections (e.g., the full inline task template) could be trimmed slightly, keeping it just below a 5.	4 / 5
Actionability	Provides concrete TaskCreate/TaskUpdate calls, a full task-description template, and specific rebalancing steps; mostly executable with minor gaps where the template is scaffolding rather than fully copy-paste-ready code.	4 / 5
Workflow Clarity	Sequenced rebalancing steps and dependency principles are present, but operations that reassign work across a team (batch/state-changing) lack explicit validation checkpoints or feedback loops, which caps this dimension at 3.	3 / 5
Progressive Disclosure	Structure is reasonable and two real reference files exist in the bundle, but the body never inline-signals those references (no "See dependency-graphs.md" links), so references are not clearly signaled and some content that could live in references is inlined.	3 / 5
	Total	14 / 20 Passed

Description

88%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 is strong: it states concrete capabilities in third person, provides an explicit "Use this skill when..." trigger clause, and carves out a distinct niche. Minor gaps in trigger-term synonym coverage keep it just below perfect on two dimensions.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — "Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing" — covering the domain comprehensively, matching the score-5 anchor.	5 / 5
Completeness	Explicitly answers both what (decompose/design/coordinate) and when ("Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress") with concrete trigger phrases, matching the score-5 anchor.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ("breaking down work for agent teams", "managing task dependencies", "monitoring team progress") with good coverage, but misses common synonyms/variants that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (multi-agent task coordination) with distinct triggers and minimal conflict risk; not quite the maximally-distinct score-5 example but mostly distinct with only minor overlap risk.	4 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: wshobson/agents
Path: plugins/agent-teams/skills/task-coordination-strategies/SKILL.md
Commit: 367cb6a

Reviewed: about 3 hours 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.