agent-mesh-coordinator
Agent skill for mesh-coordinator - invoke with $agent-mesh-coordinator
40
Quality
7%
Does it follow best practices?
Impact
99%
2.60xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-mesh-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 critically deficient across all dimensions. It provides only a name and invocation syntax without explaining what the skill does, what capabilities it offers, or when it should be selected. Claude would have no basis for choosing this skill appropriately from a list of available skills.
Suggestions
Add concrete actions describing what mesh-coordinator does (e.g., 'Coordinates multiple agents to work on parallel tasks, manages agent communication, and aggregates results').
Include a 'Use when...' clause with explicit triggers (e.g., 'Use when the user needs to orchestrate multiple agents, parallelize work, or coordinate complex multi-step workflows').
Add natural keywords users might say when needing this functionality (e.g., 'parallel processing', 'multi-agent', 'coordinate tasks', 'distribute work').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for mesh-coordinator' is completely abstract with no indication of 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 explanation of purpose or triggers. | 1 / 3 |
Trigger Term Quality | The only terms present are technical jargon ('mesh-coordinator', '$agent-mesh-coordinator') that users would not naturally say. No natural keywords or common variations are included. | 1 / 3 |
Distinctiveness Conflict Risk | While 'mesh-coordinator' is a specific term, the description is so vague that Claude cannot determine when to use it versus any other agent skill. The lack of context makes proper selection impossible. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is severely bloated with distributed systems theory that Claude already understands, while lacking the practical workflow guidance needed to actually coordinate mesh network tasks. The content explains what mesh networks are rather than instructing how to use this specific coordination system. The MCP tool examples are buried in conceptual explanations and there's no clear operational workflow.
Suggestions
Remove all explanatory content about distributed systems concepts (Byzantine fault tolerance, gossip protocols, consensus algorithms) - Claude knows these. Focus only on this specific implementation's usage.
Add a clear step-by-step workflow: 'To coordinate a mesh task: 1. Initialize network with X, 2. Distribute task using Y, 3. Monitor with Z, 4. Validate completion'
Move detailed algorithm implementations and best practices to separate reference files (e.g., ALGORITHMS.md, BEST_PRACTICES.md) and link to them from a concise overview
Replace illustrative Python classes with actual executable commands or real integration code that can be copy-pasted
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400 lines with extensive explanations of distributed systems concepts (Byzantine fault tolerance, gossip protocols, DHT) that Claude already knows. The content reads like a distributed systems textbook rather than actionable skill instructions. | 1 / 3 |
Actionability | Contains some concrete MCP tool commands and Python code examples, but much of the code is illustrative pseudocode (classes like WorkStealingProtocol, TaskAuction) rather than executable implementations. The actual MCP commands in bash blocks are more actionable. | 2 / 3 |
Workflow Clarity | No clear step-by-step workflow for how to actually coordinate a mesh network task. The content describes concepts and algorithms but lacks a concrete sequence like 'Step 1: Initialize network, Step 2: Distribute task, Step 3: Validate results'. No validation checkpoints for the coordination process. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline including detailed algorithm explanations, code examples, and best practices that could be split into separate reference documents. No navigation structure for finding specific information. | 1 / 3 |
Total | 5 / 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
b2618f9
- 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.