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 functions only as an invocation instruction ('invoke with $agent-consensus-coordinator') rather than a skill description, providing zero information about capabilities, use cases, or trigger conditions. Claude would have no basis for selecting this skill appropriately from a pool of available skills.
Suggestions
Add concrete actions describing what the 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 reach consensus on a decision').
Remove the invocation instruction ('invoke with $agent-consensus-coordinator') from the description field, as it is operational metadata rather than descriptive content useful 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 a technical/internal name rather than a natural term a user would say. No natural language trigger terms are present. | 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, spending most of its token budget on textbook-level descriptions of distributed systems concepts that Claude already knows. The code examples are not truly executable (relying on undefined helper methods), and the workflows lack concrete steps, validation checkpoints, and error recovery. The document would benefit enormously from being reduced to ~50 lines of actionable, tool-specific guidance with concrete examples.
Suggestions
Eliminate all conceptual explanations (BFT theory, CAP theorem, sharding concepts, etc.) and focus exclusively on how to use the specific MCP tools for consensus tasks.
Make code examples fully executable by removing references to undefined helper methods and showing complete, copy-paste-ready tool invocations with realistic inputs and expected outputs.
Add explicit validation checkpoints and error recovery steps to workflows, especially for Byzantine fault detection and network partition scenarios.
Split the content: keep a concise SKILL.md overview (~50 lines) with quick-start examples, and move detailed scenarios into separate referenced files if needed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. Extensively explains concepts Claude already knows (BFT, CAP theorem, sharding, PoS). Massive amounts of bullet-point lists that describe rather than instruct. The 'Advanced Consensus Algorithms', 'Performance Optimization', 'Fault Tolerance Mechanisms', and 'Integration Patterns' sections are essentially textbook summaries that waste tokens without adding actionable value. | 1 / 3 |
Actionability | Contains JavaScript code examples with MCP tool calls, which provides some concrete guidance. However, the code is pseudocode-like (references undefined methods like `this.buildConsensusMatrix`, `this.extractAgreement`, etc.), making it not truly executable. The majority of the content is descriptive bullet points rather than actionable instructions. The blockchain neural_train example appears nonsensical (training a transformer for blockchain consensus). | 2 / 3 |
Workflow Clarity | The 'Example Workflows' section lists high-level steps like 'Design consensus network topology' and 'Deploy consensus infrastructure' without any concrete commands, validation checkpoints, or error recovery steps. For operations involving distributed systems and Byzantine fault tolerance, the complete absence of validation/verification steps is a critical gap. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files and no bundle files. All content is inline regardless of depth or relevance. The document mixes quick-start material with deep theoretical sections and integration patterns, all at the same level, making navigation difficult. | 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
48ca369
- 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.