agent-hierarchical-coordinator
Agent skill for hierarchical-coordinator - invoke with $agent-hierarchical-coordinator
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-hierarchical-coordinator31
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 critically deficient across all dimensions. It provides only a technical invocation command without explaining what the skill does, when to use it, or any natural trigger terms. The description would be essentially useless for Claude to select this skill appropriately from a pool of available skills.
Suggestions
Add concrete actions describing what hierarchical coordination actually does (e.g., 'Orchestrates multiple sub-agents to complete complex multi-step tasks, delegates work, and synthesizes results').
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when tasks require breaking down into subtasks, coordinating multiple agents, or managing complex workflows').
Remove or relocate the invocation syntax ('$agent-hierarchical-coordinator') as it doesn't help with skill selection and add domain-specific keywords instead.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for hierarchical-coordinator' is completely abstract and does not describe what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only provides an invocation command with no functional description or usage guidance. | 1 / 3 |
Trigger Term Quality | The only terms present are technical jargon ('hierarchical-coordinator', '$agent-hierarchical-coordinator'). No natural keywords a user would say when needing this skill. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'agent skill' is extremely generic and could apply to many skills. Without describing what hierarchical coordination actually involves, it's impossible to distinguish from other agent-related skills. | 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 with excessive verbosity that explains concepts Claude already understands (hierarchical coordination, delegation patterns, performance metrics). While it contains useful MCP commands and a mandatory memory protocol, the signal-to-noise ratio is poor. The content would benefit from aggressive trimming to focus on the essential commands, protocols, and worker spawn patterns.
Suggestions
Reduce content by 70%+ by removing explanatory sections (Architecture Overview, Decision Making Framework, Best Practices) and keeping only the MCP commands and mandatory memory protocol
Split detailed worker type specifications and performance metrics into separate reference files (e.g., WORKERS.md, METRICS.md) with brief inline summaries
Add explicit validation/error handling steps for agent spawning failures and task delegation issues in the workflow
Convert the Python pseudocode algorithm to either executable code or remove it entirely since Claude can infer task assignment logic
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanations Claude doesn't need (architecture diagrams, decision-making algorithms, best practices sections). The 300+ line document could be reduced to ~50 lines of essential commands and protocols. | 1 / 3 |
Actionability | Contains concrete MCP commands and code examples, but mixes executable commands with pseudocode (Python algorithm) and YAML descriptions. The mandatory memory protocol section is actionable, but much content is descriptive rather than executable. | 2 / 3 |
Workflow Clarity | Phases are listed (Planning, Execution, Integration) but lack explicit validation checkpoints. The mandatory memory protocol has clear sequencing, but the broader workflow lacks feedback loops for error recovery in agent spawning or task delegation failures. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content (worker types, coordination workflow, performance metrics, best practices) is inline when much could be split into separate reference documents. | 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.
- 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.