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 an invocation command. It fails on every dimension: it describes no capabilities, includes no natural trigger terms, answers neither 'what' nor 'when', and provides no basis for distinguishing it from other skills.

Suggestions

Add concrete actions describing what byzantine-coordinator actually does (e.g., 'Coordinates distributed consensus, manages fault-tolerant replication, handles node failure detection').

Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user needs distributed consensus, fault tolerance, or coordination across multiple nodes').

Replace the generic 'Agent skill for' phrasing with a specific capability statement in third person (e.g., 'Manages Byzantine fault-tolerant coordination across distributed systems').

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. It only names a tool ('byzantine-coordinator') without describing what it does. 'Agent skill for' is completely vague.	1 / 3
Completeness	Neither 'what does this do' nor 'when should Claude use it' is answered. The description provides only an invocation command with no explanation of purpose or trigger conditions.	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 the name 'byzantine-coordinator' is unique, the description is so vague that Claude cannot determine when to use it versus any other skill. Without knowing what it does, it could conflict with anything or nothing.	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 content reads as a high-level architectural description rather than an actionable skill. It provides no executable code, no concrete commands, no specific workflows, and no examples. Every bullet point describes what should be done in abstract terms without telling Claude 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, phase transitions).

Add a clear step-by-step workflow with numbered phases for running a consensus round, including explicit validation checkpoints (e.g., 'Verify 2f+1 matching prepare messages before committing').

Remove explanations of concepts Claude already knows (what PBFT is, what Byzantine fault tolerance means) and focus on project-specific implementation details, APIs, and configuration.

Add references to specific files, modules, or external documentation that contain the actual implementation details for each capability listed.

Dimension	Reasoning	Score
Conciseness	The content is verbose and abstract, explaining concepts Claude already understands (what PBFT is, what Byzantine fault tolerance means). The bullet points read like a textbook overview rather than actionable instructions, and no token earns its place by providing novel, specific guidance.	1 / 3
Actionability	There is no concrete code, no executable commands, no specific examples, and no copy-paste ready guidance. Every item is a vague directive like 'Deploy PBFT three-phase protocol' or 'Implement threshold signature schemes' without any implementation details, APIs, or code snippets.	1 / 3
Workflow Clarity	There is no sequenced workflow, no step-by-step process, and no validation checkpoints. The content lists responsibilities and approaches as unordered bullet points without any clear execution order or feedback loops for error recovery.	1 / 3
Progressive Disclosure	The content is a monolithic list of abstract responsibilities with no references to external files, no navigation structure, and no separation between overview and detailed content. There are no links to implementation guides, examples, or reference materials.	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: ccb062f

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.