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 known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-quorum-manager/SKILL.md

Quality

Discovery

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 domain it operates in, or when it should be selected. It fails on every dimension of the rubric and would be indistinguishable from any other generic agent skill description.

Suggestions

Describe the concrete actions this skill performs (e.g., 'Manages quorum configurations, checks node availability, validates consensus thresholds').

Add a 'Use when...' clause with natural trigger terms that describe scenarios where this skill should be selected (e.g., 'Use when the user needs to manage cluster quorum settings, check node health, or configure voting members').

Remove the invocation instruction ('invoke with $agent-quorum-manager') from the description and replace it with functional information that helps 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 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	The description is so vague that Claude would have no basis to distinguish this skill from others. 'Agent skill for quorum-manager' provides no clear niche or distinct triggers.	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 design document masquerading as an implementation guide. It contains hundreds of lines of JavaScript pseudocode that depends entirely on undefined classes and phantom APIs, providing no actionable guidance Claude could actually use. The content explains distributed consensus concepts Claude already understands while failing to provide any concrete, runnable code or clear operational instructions.

Suggestions

Replace the pseudocode with a concise, actionable specification: define the actual MCP tool APIs available, provide real executable examples, and remove all phantom class references (NetworkAnalyzer, FaultAnalyzer, etc.)

Reduce the content to under 100 lines focusing on: when to adjust quorum, the specific MCP tools to call, the decision criteria, and a clear workflow with concrete validation steps

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

Add concrete input/output examples showing what a quorum adjustment request looks like and what the expected response should be, rather than abstract class hierarchies

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~600+ lines of code. The vast majority is non-executable pseudocode with placeholder classes (NetworkAnalyzer, PartitionPredictor, etc.) that don't exist. Explains distributed systems concepts Claude already knows (Byzantine fault tolerance formulas, quorum calculations). Could be reduced to 10% of its size.	1 / 3
Actionability	Despite the massive amount of code, none of it is executable. Every class depends on undefined imports and phantom classes (NetworkConditionMonitor, FaultAnalyzer, ConnectivityMatrix, etc.). The MCP integration hooks reference tools (memory_usage, swarm_status, neural_patterns) without explaining their actual API. This is elaborate pseudocode dressed as implementation.	1 / 3
Workflow Clarity	The adjustQuorum method does show a clear multi-phase workflow (prepare → execute membership changes → update weights → reconfigure protocol → verify) with rollback on failure, which is good. However, there are no concrete validation commands or checkpoints that could actually be executed, and the verification steps are abstract method calls to undefined classes.	2 / 3
Progressive Disclosure	Monolithic wall of code with no references to external files and no bundle files. All content is inline in a single massive document with no clear navigation structure. The content would benefit enormously from being split into separate reference files for each strategy, with the SKILL.md providing a concise overview.	1 / 3
	Total	5 / 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/ruflo
Commit: 367cb82

Reviewed: 5 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.