agent-adaptive-coordinator
Agent skill for adaptive-coordinator - invoke with $agent-adaptive-coordinator
36
0%
Does it follow best practices?
Impact
100%
1.51xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-adaptive-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 is an extremely weak description that fails on every dimension. It provides no information about what the skill does, when it should be used, or what distinguishes it from other skills. It reads as a placeholder rather than a functional description.
Suggestions
Replace the entire description with concrete actions the skill performs, e.g., 'Coordinates multiple agents to handle complex multi-step tasks by breaking them into subtasks and routing them appropriately.'
Add an explicit 'Use when...' clause with natural trigger terms describing the scenarios where this skill should be selected, e.g., 'Use when the user needs to orchestrate multiple workflows, coordinate parallel tasks, or manage complex multi-agent processes.'
Remove the invocation instruction ('invoke with $agent-adaptive-coordinator') from the description field, as it does not help Claude decide when to select this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for adaptive-coordinator' is entirely abstract and gives no indication of 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 skill's name and how to invoke it, providing no functional or contextual information. | 1 / 3 |
Trigger Term Quality | There are no natural keywords a user would say. 'adaptive-coordinator' is internal jargon, and 'invoke with $agent-adaptive-coordinator' is a technical invocation instruction, not a trigger term. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so generic and uninformative that it provides no distinguishing characteristics. 'Adaptive-coordinator' could overlap with any coordination, orchestration, or management skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an extremely verbose, largely non-actionable document that reads more like a theoretical design document than a practical skill. The Python code blocks are all pseudocode with undefined methods, the MCP commands reference potentially non-existent tools, and there are no concrete, executable workflows. The content explains concepts Claude already understands (ML, load balancing, topology patterns) at great length while failing to provide the specific, actionable guidance needed for actual coordination tasks.
Suggestions
Replace all pseudocode Python classes with actual executable commands or concrete MCP tool invocations that Claude can directly use, removing conceptual code that serves no practical purpose.
Reduce the content by at least 70% — remove the KPI lists, best practices, ML optimization tips, and ASCII diagrams, keeping only the topology decision criteria and concrete MCP commands.
Add a clear, step-by-step workflow with explicit validation checkpoints for performing a topology switch, including specific commands to run at each step and how to verify success before proceeding.
Split detailed reference material (topology decision matrix, MCP command reference, rollback procedures) into separate bundle files and reference them from a concise overview in SKILL.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~350+ lines. Contains extensive Python class definitions that are conceptual pseudocode (not executable), lengthy YAML decision matrices, and detailed explanations of ML concepts Claude already understands. The 'Adaptive Architecture' ASCII diagram, KPI lists, and best practices sections are largely filler that don't provide actionable guidance. | 1 / 3 |
Actionability | Despite containing many code blocks, almost none are executable. The Python classes (WorkloadAnalyzer, TopologyOptimizer, AdaptiveAgentAllocator, PredictiveLoadManager, TopologyRollback) are all pseudocode with undefined methods like self.measure_complexity(), self.collect_performance_metrics(), etc. The MCP bash commands reference tools that may not exist (bottleneck_analyze, topology_optimize, load_balance, trend_analysis) without verification. No concrete, copy-paste-ready workflow exists. | 1 / 3 |
Workflow Clarity | While there is a 'Topology Transition Protocols' section with phases, it's entirely abstract YAML descriptions without concrete commands or validation checkpoints. There's no clear step-by-step workflow for actually performing adaptive coordination. The rollback mechanism is pseudocode with undefined methods. For a coordinator performing potentially destructive topology switches, the absence of real validation steps is a critical gap. | 1 / 3 |
Progressive Disclosure | Everything is crammed into a single monolithic file with no references to external files. The content is a wall of text mixing high-level concepts, pseudocode classes, bash commands, YAML configs, and best practices all inline. The Python classes, MCP command references, and topology decision matrices could all be split into separate reference files. No bundle files are provided to support the content. | 1 / 3 |
Total | 4 / 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.