agent-hierarchical-coordinator
Agent skill for hierarchical-coordinator - invoke with $agent-hierarchical-coordinator
42
13%
Does it follow best practices?
Impact
87%
9.66xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-hierarchical-coordinator/SKILL.mdQuality
Discovery
0%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 description is essentially a label and invocation command with no substantive content. It fails on every dimension: it does not describe what the skill does, when to use it, or provide any natural trigger terms. It would be nearly impossible for Claude to correctly select this skill from a pool of available skills.
Suggestions
Describe the concrete actions this skill performs (e.g., 'Coordinates multi-agent workflows by breaking complex tasks into subtasks and delegating to specialized agents').
Add an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when the user needs to orchestrate multiple agents, coordinate parallel tasks, or manage hierarchical task decomposition').
Include specific keywords and scenarios that distinguish this from other agent or coordination skills (e.g., mention specific workflow types, task delegation patterns, or domains it handles).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for hierarchical-coordinator' is entirely abstract and does not describe what the skill actually does. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. The description only states the invocation command, providing no functional or contextual information. | 1 / 3 |
Trigger Term Quality | The only keyword is 'hierarchical-coordinator', which is technical jargon unlikely to be used naturally by a user. There are no natural trigger terms that a user would say. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it could overlap with any coordination or orchestration skill. 'Hierarchical-coordinator' gives a slight hint of domain but is far too generic to be distinctive. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is significantly over-engineered and verbose, containing extensive generic management concepts (performance metrics, best practices, communication patterns) that don't provide actionable value to Claude. While it does include concrete MCP tool commands and a structured memory coordination protocol, the useful content is buried in a monolithic document that could be reduced by more than half. The workflow lacks explicit validation checkpoints critical for multi-agent coordination.
Suggestions
Cut the content by at least 50%: remove the Architecture Overview ASCII art, Decision Making Framework pseudocode, Communication Patterns, Performance Metrics, and Best Practices sections—these are generic concepts Claude already knows.
Add explicit validation checkpoints to the workflow: after spawning a worker, verify it's active before assigning tasks; after task completion, validate deliverables before integration.
Split detailed reference content (worker type specifications, escalation protocols, MCP tool reference) into separate files and link from a concise overview in SKILL.md.
Replace the abstract YAML workflow phases with concrete, executable step-by-step commands showing a real end-to-end coordination example.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~250+ lines. Includes extensive conceptual explanations (architecture overview, communication patterns, performance metrics, best practices) that Claude already understands. The decision-making framework pseudocode, escalation protocols, and quality metrics sections are generic management concepts that don't add actionable value. Much of this could be cut by 60-70%. | 1 / 3 |
Actionability | Provides concrete MCP tool commands (spawn, monitor, orchestrate) and the mandatory memory coordination protocol with specific code examples. However, much of the content is descriptive rather than instructive (e.g., the task assignment algorithm is pseudocode illustrating a concept, escalation protocols are abstract thresholds, and the coordination workflow phases are high-level YAML descriptions rather than executable steps). | 2 / 3 |
Workflow Clarity | The three-phase workflow (Planning, Execution, Integration) provides a clear sequence, and the mandatory memory coordination protocol has numbered steps. However, there are no explicit validation checkpoints or feedback loops for error recovery. For a coordination skill involving multi-agent orchestration (a complex, potentially destructive operation), the absence of validation steps (e.g., verify worker spawned successfully before assigning tasks, validate deliverables before integration) is a significant gap. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content—from architecture overview to best practices to performance metrics—is inlined in a single massive document. Content like the decision-making framework, escalation protocols, communication patterns, and performance metrics could easily be split into separate reference files. | 1 / 3 |
Total | 6 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- ruvnet/claude-flow
- Commit
9d4a9ea
- 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.