agent-quorum-manager
Agent skill for quorum-manager - invoke with $agent-quorum-manager
39
6%
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
0%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 critically deficient across all dimensions. It provides no information about what the skill does, when to use it, or what domain it operates in. It reads as a placeholder rather than a functional description, making it essentially useless for skill selection among multiple options.
Suggestions
Add concrete actions describing what quorum-manager does (e.g., 'Manages distributed system quorum configurations, monitors node health, adjusts voting thresholds').
Add an explicit 'Use when...' clause with natural trigger terms that users would actually say when they need this skill.
Replace the invocation instruction ('invoke with $agent-quorum-manager') with functional context—invocation details belong elsewhere, not in the description used for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for quorum-manager' is entirely vague and does not describe 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, with no functional or contextual information. | 1 / 3 |
Trigger Term Quality | The only keyword is 'quorum-manager', which is a technical/internal name rather than a natural term a user would say. No natural language trigger terms are present. | 1 / 3 |
Distinctiveness Conflict Risk | While 'quorum-manager' is a unique name, the description is so vague that Claude cannot determine when to select it versus any other skill. There's no domain or action specificity to differentiate it. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
12%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an extremely verbose, non-executable code dump that describes a theoretical quorum management system. It fails to provide actionable guidance—every class depends on undefined components, making nothing copy-paste ready. The content would be better served by a concise overview of quorum management principles with specific, executable examples and clear references to detailed implementations.
Suggestions
Replace the massive non-executable class hierarchy with a concise overview (under 100 lines) covering the key quorum calculation formulas (e.g., Byzantine: >2n/3+1, crash: >n/2+1) and a single executable example.
Make code actionable by providing a minimal working implementation or concrete CLI commands rather than classes that reference dozens of undefined dependencies.
Split detailed strategy implementations (network-based, performance-based, fault-tolerance) into separate referenced files, keeping SKILL.md as a navigational overview.
Add explicit workflow steps with validation checkpoints for performing a quorum adjustment, such as a numbered checklist with concrete verification commands.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~600+ lines of code. Explains distributed consensus concepts Claude already knows, includes extensive pseudocode-style class implementations with placeholder methods that aren't executable, and massive amounts of boilerplate that don't add actionable value. | 1 / 3 |
Actionability | Despite the volume of code, none of it is executable. Classes reference undefined dependencies (NetworkConditionMonitor, FaultAnalyzer, etc.), methods call unimplemented functions, and MCP tool calls reference non-standard APIs. There are no concrete, copy-paste-ready commands or real examples. | 1 / 3 |
Workflow Clarity | The adjustQuorum method does show a phased approach (prepare, execute membership changes, update weights, reconfigure, verify) with rollback on failure, which demonstrates some workflow thinking. However, validation steps are embedded in non-executable code rather than being clear, actionable checkpoints. | 2 / 3 |
Progressive Disclosure | Monolithic wall of code with no references to external files and no clear separation of concerns. Everything is inlined in a single massive document with no navigation aids, table of contents, or links to supplementary materials. | 1 / 3 |
Total | 5 / 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
01070ed
- 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.