agent-mesh-coordinator
Agent skill for mesh-coordinator - invoke with $agent-mesh-coordinator
40
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 is an extremely weak description that provides virtually no useful information for skill selection. It only names the skill and its invocation command without describing any capabilities, use cases, or trigger conditions. It fails on every dimension of the rubric.
Suggestions
Add concrete actions describing what mesh-coordinator actually does (e.g., 'Coordinates distributed agent tasks, routes messages between agents, manages agent lifecycle').
Add an explicit 'Use when...' clause with natural trigger terms that describe scenarios where this skill should be selected (e.g., 'Use when orchestrating multiple agents, distributing tasks, or managing inter-agent communication').
Replace the invocation instruction ('invoke with $agent-mesh-coordinator') with functional description — invocation details belong elsewhere, not in the selection-critical description field.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. 'Agent skill for mesh-coordinator' is entirely abstract with 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 it's an agent skill and how to invoke it, with no functional or contextual information. | 1 / 3 |
Trigger Term Quality | The only keyword is 'mesh-coordinator', which is technical jargon unlikely to be naturally used by users. There are no natural language trigger terms that a user would say when needing this skill. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it's impossible to distinguish it from any other agent skill. Without knowing what it does, there's no way to determine when it should or shouldn't be selected. | 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 reads like a distributed systems textbook chapter rather than an actionable agent instruction set. It spends most of its token budget explaining well-known concepts (pBFT, Raft, gossip protocols, DHTs, work stealing) that Claude already understands, while failing to provide a clear workflow for what the mesh coordinator should actually do when invoked. The MCP tool commands are the only genuinely useful, project-specific content.
Suggestions
Remove or drastically condense the theoretical explanations of distributed systems concepts (pBFT, Raft, gossip, DHT, work stealing) — Claude already knows these. Focus only on project-specific configuration and tool usage.
Add a clear, numbered step-by-step workflow showing what the coordinator does from task receipt to completion, including validation checkpoints and error recovery paths.
Extract reference material (consensus algorithm details, load balancing strategies, failure detection patterns) into separate bundle files and reference them from a concise overview section.
Replace pseudocode Python classes with actual MCP tool invocations and concrete examples showing real task coordination scenarios specific to this system.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~350+ lines. Includes extensive theoretical explanations of well-known distributed systems concepts (Byzantine fault tolerance, Raft consensus, gossip protocols, DHTs) that Claude already knows. The Python pseudocode classes for work stealing, heartbeat monitoring, partition handling, and load balancing are textbook implementations that add no novel, project-specific value. Most of this content is educational rather than instructional. | 1 / 3 |
Actionability | The MCP tool integration section provides concrete bash commands that are copy-paste ready, which is useful. However, the bulk of the content consists of pseudocode Python classes and YAML descriptions of well-known algorithms that aren't executable in context. The skill describes distributed systems concepts rather than giving specific, actionable steps for what this coordinator agent should actually do when invoked. | 2 / 3 |
Workflow Clarity | There is no clear sequential workflow for how the mesh coordinator should handle a task from start to finish. The content presents various strategies and algorithms in parallel without specifying when to use which, and lacks validation checkpoints or decision points. The hooks in the frontmatter suggest a workflow but the body doesn't reinforce or clarify it with explicit steps and error recovery. | 1 / 3 |
Progressive Disclosure | The entire skill is a monolithic wall of text with no references to external files and no bundle files to support it. Content that could be split into separate reference documents (consensus algorithms, load balancing strategies, failure detection patterns) is all inlined, making the skill overwhelming and poorly organized for quick consumption. | 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
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.