agent-quorum-manager
Agent skill for quorum-manager - invoke with $agent-quorum-manager
46
Quality
17%
Does it follow best practices?
Impact
100%
2.32xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-quorum-manager/SKILL.mdQuality
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 a tool name and invocation command without any explanation of capabilities, use cases, or trigger conditions. It fails to help Claude understand when to select this skill from a list of options, as there's no indication of what 'quorum-manager' actually manages or what problems it solves.
Suggestions
Add concrete actions describing what quorum-manager does (e.g., 'Manages distributed system consensus, tracks node availability, handles voting protocols')
Include a 'Use when...' clause with natural trigger terms users might say (e.g., 'Use when managing cluster quorum, node consensus, distributed voting, or system availability')
Explain the domain context - what is a quorum in this context and what specific tasks can be performed
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for quorum-manager' 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 description or usage guidance. | 1 / 3 |
Trigger Term Quality | The only term present is 'quorum-manager' which is technical jargon. No natural keywords a user would say are included - no mention of what quorum management involves or related concepts. | 1 / 3 |
Distinctiveness Conflict Risk | The specific tool name 'quorum-manager' and invocation syntax '$agent-quorum-manager' provide some distinctiveness, but without knowing what it does, it's unclear if it would conflict with other management or coordination skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is severely over-engineered with excessive implementation detail that doesn't respect token budget. While it demonstrates comprehensive quorum management concepts, the content is a monolithic code dump rather than actionable guidance. The skill would benefit from dramatic reduction to essential patterns with references to detailed implementations elsewhere.
Suggestions
Reduce to a concise overview (under 100 lines) with key patterns and decision points, moving detailed implementations to referenced files like STRATEGIES.md or IMPLEMENTATION.md
Add explicit validation checkpoints with clear 'if validation fails, do X' recovery steps in the workflow sections
Replace incomplete class stubs with focused, executable code snippets that demonstrate specific quorum operations
Structure content with a quick-start section showing the most common use case before diving into advanced strategies
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~600+ lines with extensive code that explains concepts Claude already knows (basic quorum calculations, fault tolerance formulas, network topology analysis). Much of this is implementation detail that could be summarized in a fraction of the space. | 1 / 3 |
Actionability | Provides concrete JavaScript code examples, but they are incomplete class implementations with many undefined dependencies (NetworkAnalyzer, FaultAnalyzer, etc.) and placeholder methods. Not copy-paste executable without significant additional context. | 2 / 3 |
Workflow Clarity | The executeQuorumAdjustment method shows a 5-phase process with some validation, but lacks explicit error recovery steps and validation checkpoints are implicit rather than clearly documented. Missing feedback loops for when verification fails. | 2 / 3 |
Progressive Disclosure | Monolithic wall of code with no references to external files. All implementation details are inline rather than appropriately split. No clear overview section - jumps directly into massive code blocks without navigation structure. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (828 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- ruvnet/claude-flow
- Commit
b2618f9
- 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.