agent-consensus-coordinator

Agent skill for consensus-coordinator - invoke with $agent-consensus-coordinator

7.38x

Quality

Does it follow best practices?

Impact

96%

7.38x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-consensus-coordinator/SKILL.md

Quality

Discovery

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 fails on all dimensions. It provides no information about what the skill does, when it should be used, or what domain it operates in. It reads as a placeholder rather than a functional description that could help Claude select the right skill.

Suggestions

Add concrete actions describing what consensus-coordinator actually does (e.g., 'Coordinates multi-agent consensus by collecting responses, identifying agreements and disagreements, and synthesizing unified outputs').

Add an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when the user needs to gather input from multiple agents, resolve conflicting opinions, or reach agreement across parallel workflows').

Replace the invocation instruction ('invoke with $agent-consensus-coordinator') with domain-specific keywords that distinguish this skill from other agent or coordination skills.

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, providing no functional or contextual information.	1 / 3
Trigger Term Quality	The only keyword is 'consensus-coordinator', which is a technical/internal name, not a natural term a user would say. There are no natural language trigger terms like 'coordinate', 'agreement', 'voting', or any domain-specific terms.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that it's impossible to distinguish it from other skills. 'Agent skill' is completely generic and the name 'consensus-coordinator' alone doesn't provide enough context to avoid conflicts.	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 network training call for blockchain consensus. The workflow sections lack any concrete commands, validation steps, or error recovery mechanisms, making them essentially useless for guiding actual implementation.

Suggestions

Cut the content by 60-70%: remove all sections that describe concepts Claude already knows (BFT theory, CAP theorem, sharding concepts, fault tolerance categories) and focus only on the specific MCP tool usage patterns.

Make code examples truly 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 by checking that consensusResult.iterations < maxIterations and spectralGap > threshold before proceeding.'

Split content into a concise SKILL.md overview with references to separate files for detailed scenarios (e.g., BYZANTINE.md, VOTING.md, SWARM-COORDINATION.md).

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 token budget.	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 nonsensically uses a neural network training call for consensus, which is misleading. 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/complex), 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 inlined regardless of depth or relevance. The document mixes overview-level bullet lists with detailed code examples and conceptual descriptions in a single massive file with no navigation structure or cross-references.	1 / 3
	Total	5 / 12 Passed

Validation

100%

Warnings & errors only

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: 01070ed

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.