agent-byzantine-coordinator

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

1.06x

Quality

Does it follow best practices?

Impact

94%

1.06x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-byzantine-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 description is essentially a stub that provides no useful information about the skill's purpose, capabilities, or appropriate usage context. It only names the skill and provides an invocation command, making it nearly impossible for Claude to determine when to select this skill from a pool of available options.

Suggestions

Add a clear description of what the skill does with concrete actions (e.g., 'Coordinates distributed consensus across multiple agents, handles fault-tolerant decision-making, and manages replicated state').

Add an explicit 'Use when...' clause with natural trigger terms that describe scenarios where this skill should be selected (e.g., 'Use when the user needs distributed coordination, fault tolerance, consensus protocols, or multi-agent agreement').

Replace the invocation instruction with functional content — invocation syntax belongs in usage documentation, not in the description field used for skill selection.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Agent skill for byzantine-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 'byzantine-coordinator', which is technical jargon that no user would naturally say. There are no natural language trigger terms that would help Claude match user requests to this skill.	1 / 3
Distinctiveness Conflict Risk	The unique name 'byzantine-coordinator' is distinctive enough that it's unlikely to conflict with other skills, but the lack of any functional description means Claude has no basis for selecting it appropriately.	2 / 3
	Total	5 / 12 Passed

Implementation

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads as a high-level architectural overview or feature list rather than an actionable skill that teaches Claude how to perform specific tasks. It lacks any concrete code, commands, examples, or step-by-step workflows. The content describes what a Byzantine consensus coordinator should do conceptually but provides zero guidance on how to actually implement or execute any of it.

Suggestions

Add executable code examples for at least the core PBFT three-phase protocol (pre-prepare, prepare, commit) with concrete message structures and validation logic.

Define a clear step-by-step workflow for consensus rounds with explicit validation checkpoints (e.g., 'Verify 2f+1 matching prepare messages before entering commit phase').

Replace abstract bullet points like 'Implement threshold signature schemes' with specific commands, function signatures, or concrete implementation patterns.

Remove or drastically condense the high-level descriptions (Core Responsibilities, Security Integration) and replace with actionable instructions Claude can directly follow.

Dimension	Reasoning	Score
Conciseness	The content is verbose and abstract, listing high-level concepts (zero-knowledge proofs, threshold signatures, PBFT phases) without any concrete implementation details. It reads like a feature brochure rather than actionable instructions, and explains concepts Claude already understands without adding novel, specific guidance.	1 / 3
Actionability	There is no executable code, no concrete commands, no specific examples, and no copy-paste ready guidance. Every bullet point is a vague description ('Deploy PBFT three-phase protocol', 'Implement threshold signature schemes') with no actual implementation steps or code.	1 / 3
Workflow Clarity	Despite describing a multi-phase consensus protocol (which inherently requires clear sequencing and validation checkpoints), there are no sequenced steps, no validation checkpoints, no error recovery flows, and no feedback loops. The content merely lists responsibilities without defining how to execute them.	1 / 3
Progressive Disclosure	The content has some structural organization with headers and subsections, but there are no references to external files, no bundle files to support deeper content, and the collaboration section references other components without linking to them. The structure exists but doesn't effectively organize actionable content.	2 / 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: 2b9e2de

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.