agent-quorum-manager

Agent skill for quorum-manager - invoke with $agent-quorum-manager

2.32x

Quality

Does it follow best practices?

Impact

100%

2.32x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-quorum-manager/SKILL.md

Quality

Content

12%Scale 1-3

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 undefined dependencies, explains distributed consensus concepts Claude already understands, and provides no concrete commands, tools, or steps that could actually be followed. The content would need to be fundamentally restructured around actual executable operations with real tool integrations.

Suggestions

Replace illustrative pseudocode with actual executable code or concrete CLI commands that Claude can run — define what real tools/APIs are available and show their actual usage

Reduce the content by 80%+ by removing the three full strategy class implementations and instead providing a concise decision table or flowchart for when to use each strategy

Split detailed strategy implementations into separate referenced files (e.g., NETWORK_STRATEGY.md, PERFORMANCE_STRATEGY.md) and keep SKILL.md as a concise overview with clear navigation

Add concrete validation steps with real commands — e.g., how to actually verify a quorum is operational, what specific MCP tool calls to make with exact parameter schemas

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~600+ lines of JavaScript code that is entirely illustrative pseudocode with placeholder classes (NetworkAnalyzer, PartitionPredictor, etc.) that don't exist. The content explains distributed systems concepts Claude already knows and pads extensively with scoring formulas and strategy patterns that add no actionable value.	1 / 3
Actionability	Despite the massive amount of code, none of it is executable. Every class references undefined dependencies (NetworkConditionMonitor, FaultAnalyzer, ConnectivityMatrix, etc.), and the MCP integration hooks reference tools (memory_usage, swarm_status, neural_patterns) without specifying actual APIs or installation steps. This is architectural pseudocode dressed as implementation.	1 / 3
Workflow Clarity	The adjustQuorum method does show a clear multi-phase sequence (prepare → execute membership changes → update weights → reconfigure protocol → verify) with rollback on failure, which demonstrates some workflow thinking. However, there are no concrete validation commands, no real checkpoints Claude could execute, and the verification steps are abstract method calls.	2 / 3
Progressive Disclosure	The entire skill is a monolithic wall of code with no references to external files, no bundle structure, and no separation of concerns. All three strategy implementations are inlined in full, making the document extremely long with no navigation aids or layered organization.	1 / 3
	Total	5 / 12 Passed

Description

0%Scale 1-3

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 zero information about what the skill does, when to use it, or what domain it operates in. It fails on every dimension because it lacks any concrete actions, natural trigger terms, explicit usage guidance, or distinguishing details.

Suggestions

Describe what quorum-manager actually does with specific concrete actions (e.g., 'Manages distributed system quorum configurations, monitors node health, and handles consensus voting').

Add an explicit 'Use when...' clause with natural trigger terms a user might say (e.g., 'Use when the user needs to configure quorum settings, check cluster consensus, or manage node membership').

Remove the invocation instruction ('invoke with $agent-quorum-manager') from the description, as it is operational detail that doesn't help Claude decide when to select this skill.

Dimension	Reasoning	Score
Specificity	The description provides 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	The description is so vague that it provides no distinguishing characteristics. Without knowing what 'quorum-manager' does, Claude cannot differentiate it from any other agent skill.	1 / 3
	Total	4 / 12 Passed

Validation

90%

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 — 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
Path: .agents/skills/agent-quorum-manager/SKILL.md
Commit: 913f9ea

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.