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.
76
67%
Does it follow best practices?
Impact
92%
1.10xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/agent-teams/skills/task-coordination-strategies/SKILL.mdQuality
Discovery
85%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured description that clearly communicates both capabilities and usage triggers. It uses third person voice correctly and lists concrete actions. The main weakness is that trigger terms could be broader to capture more natural user phrasings, particularly simpler terms like 'split work', 'subtasks', or 'parallel execution'.
Suggestions
Expand trigger terms to include more natural user phrasings such as 'split up work', 'subtasks', 'parallel tasks', 'orchestrate', or 'task planning' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Decompose complex tasks', 'design dependency graphs', 'coordinate multi-agent work with proper task descriptions and workload balancing'. These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Decompose complex tasks, design dependency graphs, and coordinate multi-agent work') and when ('Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'task dependencies', 'agent teams', 'workload balancing', and 'multi-agent work', but misses common natural variations users might say such as 'split up work', 'parallel tasks', 'orchestrate agents', 'task planning', or 'subtasks'. | 2 / 3 |
Distinctiveness Conflict Risk | The focus on multi-agent coordination, dependency graphs, and workload balancing creates a clear niche that is unlikely to conflict with general task management or coding skills. The domain of agent team orchestration is quite specific. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a solid conceptual framework for task coordination with useful patterns (dependency graphs, task templates, workload monitoring table). However, it leans more toward teaching coordination concepts than providing precise, executable instructions — the decomposition strategies describe approaches Claude likely already understands, and the tool usage examples are schematic rather than copy-paste ready. Adding validation checkpoints and tightening the prose would meaningfully improve it.
Suggestions
Make the blockedBy/blocks examples fully executable with exact tool call syntax and complete parameter sets, rather than pseudo-API notation
Add a validation checkpoint after decomposition (e.g., 'Verify: no task modifies files owned by another task; critical path depth ≤ N; all tasks have acceptance criteria')
Remove or condense the 'When to Use This Skill' section and the decomposition strategy explanations ('Best for' lines) — Claude can infer when to apply these patterns
Add a concrete end-to-end example showing a real task being decomposed into subtasks with dependency graph, assigned descriptions, and a rebalancing scenario
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably well-organized but includes some unnecessary framing (e.g., 'When to Use This Skill' section largely restates the heading topics). The decomposition strategies section explains concepts Claude likely already understands (what layers/components/concerns are). Could be tightened by ~20-30%. | 2 / 3 |
Actionability | Provides a good task description template and concrete patterns (blockedBy/blocks usage, ASCII dependency graphs), but the guidance is more conceptual than executable. The blockedBy/blocks example uses pseudo-API calls rather than exact tool invocations with complete parameters. Decomposition strategies are descriptive rather than instructive. | 2 / 3 |
Workflow Clarity | The rebalancing steps provide a clear sequence (TaskList → identify → TaskUpdate → SendMessage → monitor), and the workload monitoring table is useful. However, the overall task coordination workflow lacks explicit validation checkpoints — there's no step to verify decomposition quality, no feedback loop for when dependency graphs have issues, and no verification that rebalancing actually improved throughput. | 2 / 3 |
Progressive Disclosure | Content is well-sectioned with clear headers and logical grouping, but everything is inline in a single file. The task description template and dependency patterns could be split into referenced files. For a skill of this length (~120 lines of substantive content), the inline approach is borderline acceptable but would benefit from references to supplementary materials. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- wshobson/agents
- Commit
91fe43e
- 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.