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 is an extremely weak description that provides essentially no useful information beyond the skill's name and invocation command. It fails on every dimension: no concrete actions, no trigger terms, no 'what' or 'when' guidance, and no distinguishing characteristics. Claude would have no basis for selecting this skill in response to any user request.

Suggestions

Add a clear explanation of what the skill does with specific concrete actions (e.g., 'Coordinates distributed consensus across multiple agents, resolves conflicting outputs, and manages fault-tolerant decision-making').

Add an explicit 'Use when...' clause with natural trigger terms that describe scenarios where this skill should be selected (e.g., 'Use when coordinating multiple agents, resolving disagreements between parallel outputs, or implementing fault-tolerant workflows').

Remove the invocation instruction ('invoke with $agent-byzantine-coordinator') from the description field, as this is operational detail rather than selection-relevant information, and replace it with functional context.

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 the invocation command, 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	While 'byzantine-coordinator' is a unique name, the description is so vague that Claude cannot determine when to use it versus any other skill. The lack of any functional description makes it impossible to distinguish from other agent skills.	1 / 3
	Total	4 / 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 like a high-level architecture document or feature wishlist rather than actionable instructions for Claude. It contains no executable code, no concrete commands, no examples, and no clear workflows. Every section describes what should be done in abstract terms without providing any guidance on how to actually do it.

Suggestions

Replace abstract descriptions with concrete, executable code examples showing how to implement PBFT consensus (e.g., message signing, vote collection, quorum verification)

Add a clear step-by-step workflow for the consensus protocol with explicit validation checkpoints (e.g., 'Pre-prepare → Prepare → Commit' with verification at each phase)

Remove explanations of well-known concepts (what PBFT is, what Byzantine fault tolerance means) and focus on project-specific implementation details, configurations, and tool invocations

Add references to specific files, APIs, or modules that Claude should use when coordinating consensus, rather than listing abstract capabilities

Dimension	Reasoning	Score
Conciseness	The content is verbose and describes concepts at a high level without adding anything Claude doesn't already know. Phrases like 'ensuring system integrity and reliability in the presence of malicious actors' and bullet points explaining what PBFT is are unnecessary padding. No concrete implementation details justify the token usage.	1 / 3
Actionability	The skill provides zero concrete code, commands, or executable guidance. Every bullet point is an abstract description ('Deploy PBFT three-phase protocol', 'Implement threshold signature schemes') with no actual implementation, configuration, or specific steps Claude could follow.	1 / 3
Workflow Clarity	There is no clear workflow sequence, no step-by-step process, and no validation checkpoints. The content lists responsibilities and approaches as bullet points but never defines how to actually execute a consensus round, detect a malicious actor, or perform a view change.	1 / 3
Progressive Disclosure	The content is a monolithic list of abstract bullet points with no references to detailed files, no examples, and no navigation structure. There are no links to implementation details, protocol specifications, or code references that would help Claude actually perform these tasks.	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/ruflo
Commit: 398f7c2

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.