agent-consensus-coordinator
Agent skill for consensus-coordinator - invoke with $agent-consensus-coordinator
40
7%
Does it follow best practices?
Impact
96%
7.38xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-consensus-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 no information about what the skill does, when it should be used, or what user requests should trigger it. It reads as a placeholder rather than a functional description, making it essentially useless for skill selection among multiple options.
Suggestions
Add concrete actions describing what consensus-coordinator does (e.g., 'Coordinates multi-agent consensus by collecting responses, resolving conflicts, and synthesizing agreed-upon outputs').
Add an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when the user needs to gather agreement across multiple agents, resolve conflicting outputs, or coordinate parallel task results').
Replace the invocation instruction ('invoke with $agent-consensus-coordinator') with functional context—invocation details belong in the skill body, not the description used for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. 'Agent skill for consensus-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 'consensus-coordinator', which is technical jargon unlikely to be used naturally by users. There are no natural trigger terms describing tasks or scenarios. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it's impossible to distinguish it from other skills. 'Consensus-coordinator' hints at a niche but without any elaboration, it could overlap with collaboration, voting, decision-making, or other coordination skills. | 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 is excessively verbose, mixing large amounts of conceptual knowledge Claude already possesses with semi-functional pseudocode examples. The code examples reference undefined helper methods and include a nonsensical neural_train call for blockchain consensus. The numerous bullet-point sections on fault tolerance, performance optimization, and integration patterns provide no actionable guidance beyond what Claude already knows about distributed systems.
Suggestions
Cut the content by 60-70%: remove all conceptual sections (Advanced Consensus Algorithms, Performance Optimization, Fault Tolerance Mechanisms) that describe knowledge Claude already has, and focus only on how to use the specific MCP tools for consensus tasks.
Make code examples executable by providing complete implementations rather than classes with undefined helper methods like `this.buildConsensusMatrix()` and `this.extractAgreement()`.
Add explicit validation checkpoints to workflows, e.g., verify consensus convergence, check Byzantine resilience thresholds, and define error recovery steps when consensus fails.
Split detailed code examples and integration patterns into separate referenced files, keeping SKILL.md as a concise overview with clear navigation links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. Massive amounts of bullet-point lists that describe concepts Claude already knows (BFT, CAP theorem, crash fault tolerance, sharding). The 'Advanced Consensus Algorithms', 'Performance Optimization', 'Fault Tolerance Mechanisms', and 'Integration Patterns' sections are almost entirely conceptual descriptions that add no actionable value and waste tokens. | 1 / 3 |
Actionability | Contains JavaScript code examples with MCP tool calls that show concrete usage patterns, but the code is pseudocode-like (references undefined methods like `this.buildConsensusMatrix`, `this.extractAgreement`, etc.) making it not truly executable. The blockchain consensus section misuses a neural_train API for consensus which is nonsensical. Many sections are just bullet-point descriptions with no concrete guidance. | 2 / 3 |
Workflow Clarity | The 'Example Workflows' section lists high-level steps like 'Deploy consensus infrastructure' and 'Monitor consensus performance' with no concrete commands, validation checkpoints, or error recovery steps. For operations involving distributed systems and Byzantine fault tolerance (inherently risky), there are zero validation or verification steps anywhere in the skill. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline regardless of depth or relevance. The document mixes overview-level concepts with detailed code examples and exhaustive bullet-point taxonomies, with no clear navigation structure or separation of concerns. | 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
ccb062f
- 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.