agent-byzantine-coordinator
Agent skill for byzantine-coordinator - invoke with $agent-byzantine-coordinator
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-byzantine-coordinator44
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 94%
↑ 1.06xAgent success when using this skill
Validation for skill structure
Discovery
7%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 severely deficient, providing only an invocation command without any explanation of capabilities, use cases, or trigger conditions. It fails to help Claude understand when to select this skill and what it actually does. The term 'byzantine-coordinator' is opaque technical jargon that provides no meaningful context.
Suggestions
Add concrete actions describing what the byzantine-coordinator actually does (e.g., 'Coordinates distributed consensus, manages fault-tolerant systems, handles node synchronization').
Include a 'Use when...' clause with natural trigger terms users would say when needing this functionality.
Replace or supplement the technical name with plain-language descriptions of the problem domain this skill addresses.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for byzantine-coordinator' is completely abstract with no indication of what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only provides an invocation command with no functional information. | 1 / 3 |
Trigger Term Quality | The only keyword is 'byzantine-coordinator' which is technical jargon that users would not naturally say. No natural language trigger terms are present. | 1 / 3 |
Distinctiveness Conflict Risk | The specific name 'byzantine-coordinator' is distinctive enough to avoid conflicts with other skills, but the lack of any functional description makes it unclear what domain it operates in. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a capability overview or design document than an actionable skill file. It describes what the Byzantine coordinator should do conceptually but provides no executable code, concrete commands, or step-by-step workflows that Claude could follow. The content would benefit significantly from actual implementation examples and clear procedural guidance.
Suggestions
Add executable code examples showing how to initiate PBFT consensus, validate messages, or detect malicious actors
Include a clear numbered workflow for the three-phase PBFT protocol with explicit validation checkpoints between phases
Provide concrete examples of message formats, signature verification commands, or detection heuristics rather than abstract descriptions
Link to separate reference files for detailed protocol specifications, attack vectors, and recovery procedures
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably organized but includes some unnecessary elaboration. Phrases like 'ensuring system integrity and reliability in the presence of malicious actors' are verbose, and the bullet points could be more terse while retaining meaning. | 2 / 3 |
Actionability | The skill describes concepts and responsibilities at a high level but provides no concrete code, commands, or executable examples. Statements like 'Deploy PBFT three-phase protocol' and 'Implement threshold signature schemes' are abstract directives without implementation details. | 1 / 3 |
Workflow Clarity | There is no clear sequenced workflow for executing Byzantine consensus. The content lists capabilities and approaches but lacks step-by-step processes, validation checkpoints, or error recovery procedures for multi-step consensus operations. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections with headers, but there are no references to external files for detailed implementation. For a complex topic like Byzantine consensus, the lack of links to protocol details, examples, or API references limits discoverability. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
100%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.
- Reviewed
Table of Contents
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.