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 findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-consensus-coordinator/SKILL.md

Quality

Content

14%Scale 1-3

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, containing large amounts of textbook-level distributed systems knowledge that Claude already possesses. The code examples appear concrete but rely on 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 as operational guidance.

Suggestions

Cut the skill to under 80 lines by removing all conceptual explanations (BFT theory, CAP theorem, PoS mechanics, etc.) and keeping only the MCP tool invocation patterns with concrete parameters.

Make code examples truly executable by providing complete implementations rather than classes with undefined helper methods like `this.buildConsensusMatrix()`.

Add explicit validation checkpoints to workflows, e.g., 'Verify consensus reached by checking convergenceTime < maxIterations' and error recovery steps for Byzantine fault detection.

Remove the blockchain neural_train example which nonsensically uses a neural network training API for consensus, or replace it with an actual consensus-relevant MCP tool call.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~300+ lines. Contains extensive explanations of concepts Claude already knows (BFT, PoS, CAP theorem, sharding, etc.). Massive 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 add no 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 blockchain consensus section nonsensically uses a neural network training call for consensus, which is misleading.	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 a skill involving distributed systems with potential Byzantine failures, 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 provided. All content is inline regardless of depth or relevance. Sections like 'Advanced Consensus Algorithms' and 'Fault Tolerance Mechanisms' are pure bullet-point lists that could be separate reference documents but instead bloat the main file.	1 / 3
	Total	5 / 12 Passed

Description

0%Scale 1-3

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 unusable 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 description content — invocation syntax belongs in the skill body, not the description field.

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 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

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
Path: .agents/skills/agent-consensus-coordinator/SKILL.md
Commit: 913f9ea

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.