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 actions it performs, or when it should be selected. It fails on all dimensions because it lacks any concrete capabilities, trigger terms, or usage guidance. Claude would have no basis for choosing this skill from a list of available skills.

Suggestions

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

Add an explicit 'Use when...' clause with natural trigger terms that users would say when they need this skill (e.g., 'Use when the user needs to configure quorum settings, check cluster consensus, or manage node voting').

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 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. 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 extremely verbose, non-executable code dump that reads more like a design document or architectural sketch than actionable guidance. The hundreds of lines of JavaScript reference dozens of undefined classes and methods, making nothing copy-paste ready. The content would benefit enormously from being reduced to a concise overview with actual executable examples and clear workflow steps.

Suggestions

Reduce the content to under 100 lines: provide a concise overview of quorum management responsibilities and 1-2 small, actually executable code examples rather than hundreds of lines of speculative class definitions.

Replace the pseudo-implementations with concrete, actionable guidance — e.g., specific commands or API calls to invoke quorum adjustments, with real input/output examples.

Add a clear step-by-step workflow section (e.g., 'How to adjust quorum') with explicit validation checkpoints and error recovery steps.

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

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~600+ lines of code. The vast majority is speculative class implementations with placeholder methods that don't contain real logic (e.g., methods that call undefined helpers like `this.getNodeCPUCapacity()`). Claude already understands distributed consensus concepts; this explains them at length without adding actionable value.	1 / 3
Actionability	Despite the massive amount of code, none of it is executable. Every class depends on undefined imports and helper classes (NetworkAnalyzer, ConnectivityMatrix, PartitionPredictor, etc.). The code is elaborate pseudocode dressed up as JavaScript — it cannot be copy-pasted and run.	1 / 3
Workflow Clarity	The adjustQuorum method does show a clear multi-phase workflow (prepare → execute membership changes → update weights → reconfigure → verify) with rollback on failure, which demonstrates some workflow thinking. However, there are no explicit validation checkpoints the user/agent can follow, and the overall skill lacks a clear step-by-step process for when and how to invoke these operations.	2 / 3
Progressive Disclosure	The entire skill is a monolithic wall of code with no references to external files, no clear navigation structure, and no separation between overview and detailed content. Everything is dumped inline with no way to progressively discover information.	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: 398f7c2

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.