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 is essentially a placeholder rather than a functional description.
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 content — invocation syntax is not useful for skill selection and wastes description space.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains 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, providing 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 actionable instructions for Claude. It spends most of its token budget explaining well-known concepts (pBFT, Raft, gossip protocols, DHTs) with illustrative pseudocode that Claude already understands, while failing to provide a clear workflow for what to actually do when invoked. The MCP tool commands are the only genuinely useful content, but they're buried in hundreds of lines of conceptual material.
Suggestions
Remove all textbook explanations of distributed systems concepts (pBFT, Raft, gossip, DHTs, Byzantine fault tolerance) — Claude already knows these. Focus only on project-specific configuration and tool usage.
Add a clear step-by-step workflow: 'When invoked, do step 1 (initialize network), step 2 (distribute tasks), step 3 (monitor and validate), step 4 (collect results)' with explicit validation checkpoints between steps.
Extract the Python class examples and consensus algorithm details into separate reference files (e.g., ALGORITHMS.md, PATTERNS.md) and link to them from a concise overview.
Replace pseudocode Python classes with actual executable MCP tool command sequences that demonstrate real task coordination scenarios end-to-end.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~350+ lines. Explains distributed systems concepts (gossip protocols, pBFT, Raft, DHTs, Byzantine fault tolerance) that Claude already knows. The Python class examples are conceptual illustrations of well-known algorithms, not project-specific executable code. Most content is textbook material that wastes token budget. | 1 / 3 |
Actionability | The MCP tool integration section provides concrete bash commands that are copy-paste ready, which is valuable. However, the bulk of the content consists of pseudocode Python classes (WorkStealingProtocol, HeartbeatMonitor, etc.) that are illustrative rather than executable—they reference undefined functions and can't actually be run. The skill lacks concrete guidance on what to do when invoked with a specific task. | 2 / 3 |
Workflow Clarity | There is no clear step-by-step workflow for how to actually coordinate a mesh network task from start to finish. The content describes many concepts and protocols but never sequences them into an actionable workflow with validation checkpoints. For a coordinator skill involving distributed operations, the absence of explicit validation steps and error recovery workflows is a significant gap. | 1 / 3 |
Progressive Disclosure | The entire skill is a monolithic wall of text with no references to external files. Content that could be split out (consensus algorithms, load balancing strategies, failure detection patterns) is all inline, making the file extremely long. There's no quick-start section or clear navigation structure—just a long sequence of sections at the same level of detail. | 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/ruflo
- Commit
0f7c750
- 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.