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 essentially a label with an invocation command, providing no information about what the skill does, what capabilities it offers, or when it should be selected. It fails on every dimension because it lacks any concrete actions, natural trigger terms, or explicit guidance on when to use it.
Suggestions
Add concrete actions describing what quorum-manager does (e.g., 'Manages distributed system quorum configurations, monitors node health, adjusts voting members').
Add an explicit 'Use when...' clause with natural trigger terms a user might say (e.g., 'Use when the user needs to manage cluster quorum, check node consensus, or configure voting members').
Replace the invocation instruction ('invoke with $agent-quorum-manager') with functional description content — invocation details belong in the skill body, not the description field.
| 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 trigger 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. There are no natural language trigger terms. | 1 / 3 |
Distinctiveness Conflict Risk | While 'quorum-manager' is a unique name, the description is so vague that Claude cannot determine when to use it versus any other skill. Without knowing what it does, conflict risk is high due to ambiguity. | 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 architectural design document masquerading as an actionable skill. It contains hundreds of lines of non-executable JavaScript pseudocode with dozens of undefined dependencies, making it impossible for Claude to actually use any of it. The content would be far more useful as a concise set of actual instructions for when and how to adjust quorum settings, with concrete commands and real tool invocations.
Suggestions
Replace the illustrative pseudocode with actual executable code or concrete step-by-step instructions that Claude can follow — define what tools/APIs are actually available and how to call them.
Reduce the content by 80%+ — distill the three strategies into a concise decision table or flowchart rather than hundreds of lines of abstract class definitions.
Split the content into a brief SKILL.md overview with references to separate files for each strategy (network-based, performance-based, fault-tolerance) if detailed code is truly needed.
Add concrete validation steps with real commands — e.g., how to actually verify a quorum is operational, what specific MCP tool calls to make, and what success/failure responses look like.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~600+ lines of JavaScript code that is entirely illustrative/pseudocode with undefined dependencies (NetworkAnalyzer, PartitionPredictor, etc.). The content explains distributed systems concepts Claude already knows and pads extensively with scoring formulas and strategy patterns that aren't executable or actionable. | 1 / 3 |
Actionability | None of the code is executable — it references dozens of undefined classes (NetworkConditionMonitor, FaultAnalyzer, ConnectivityMatrix, etc.) and undefined methods. The MCP integration hooks reference tools (memory_usage, swarm_status, neural_patterns) without specifying their actual APIs or how to invoke them. This is architectural pseudocode dressed as implementation. | 1 / 3 |
Workflow Clarity | The adjustQuorum method does show a phased workflow (prepare → execute membership changes → update weights → reconfigure → verify) with rollback on failure, which demonstrates some workflow thinking. However, there are no concrete validation checkpoints with actual commands, and the phases themselves are all abstract method calls with no real implementation. | 2 / 3 |
Progressive Disclosure | The entire skill is a monolithic wall of code with no references to external files, no table of contents, and no separation of concerns. Everything from network strategy to performance strategy to fault tolerance strategy is inlined in a single massive document with no bundle files to support it. | 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
9d4a9ea
- 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.