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 to use it, or what domain it operates in. It reads as a placeholder rather than a functional description, making it nearly impossible for Claude to correctly select this skill from a pool of available options.

Suggestions

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

Add an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when the user needs to gather input from multiple agents, resolve disagreements, or reach consensus on a decision').

Replace the invocation instruction ('invoke with $agent-consensus-coordinator') with domain-specific keywords that distinguish this skill from other coordination or collaboration 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. Without knowing what 'consensus-coordinator' does, it could overlap with anything involving coordination, collaboration, or decision-making.	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 describing distributed consensus concepts that Claude already understands rather than providing actionable, executable guidance. The code examples reference undefined helper methods making them non-executable, and one section (blockchain consensus) nonsensically uses a neural network training API for consensus. The numerous bullet-point sections read like a textbook table of contents rather than a practical skill guide.

Suggestions

Cut the content by 70%+ by removing all conceptual descriptions (BFT theory, CAP theorem, PoS concepts, etc.) and keeping only concrete tool usage patterns with executable code examples.

Make code examples truly executable by providing complete implementations rather than referencing undefined methods like `this.buildConsensusMatrix()` and `this.extractAgreement()`.

Add explicit validation checkpoints to workflows, e.g., 'Verify consensus reached by checking convergence metric < epsilon' with concrete code to perform the check.

Remove the blockchain neural network training section which incorrectly uses `neural_train` for consensus, and replace with an actual consensus-relevant example using the declared MCP tools.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~300+ lines. Contains extensive explanations of concepts Claude already knows (BFT, PoS, CAP theorem, sharding, etc.), bullet-point lists that describe rather than instruct, and large sections of conceptual overview that add no actionable value. The 'Advanced Consensus Algorithms', 'Performance Optimization', 'Fault Tolerance Mechanisms', and 'Integration Patterns' sections are almost entirely descriptive bullet points with no concrete guidance.	1 / 3
Actionability	The code examples show MCP tool calls with specific parameters, which is somewhat concrete. However, the code is pseudocode-like (references undefined methods like `this.buildConsensusMatrix`, `this.extractAgreement`, etc.), making it not truly executable. Many sections are purely descriptive bullet lists with no concrete commands or code. The blockchain consensus section nonsensically uses a neural network training call for 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 consensus (which are inherently risky and complex), there are no validation or verification steps anywhere. The workflows are vague descriptions rather than actionable sequences.	1 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files despite the massive length. All content is inline in a single file with no bundle files to support it. The content would benefit enormously from splitting into separate reference files for different consensus protocols, integration patterns, and examples. No navigation aids or clear hierarchy for finding specific information.	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: 9d4a9ea

Reviewed: 6 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.