hive-mind

Byzantine fault-tolerant consensus and distributed coordination. Queen-led hierarchical swarm management with multiple consensus strategies. Use when: distributed coordination, fault-tolerant operations, multi-agent consensus, collective decision making. Skip when: single-agent tasks, simple operations, local-only work.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

87%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, action-oriented reference: executable commands and dense option tables with no padding. The one gap is workflow clarity — it is a command catalog rather than a sequenced, validated workflow for risky distributed operations.

Suggestions

Add an explicit end-to-end sequence (init -> spawn queen -> spawn workers -> check consensus) with a 'Verify consensus status' checkpoint and a retry-on-failure feedback loop, since swarm/consensus operations are batch/distributed.

Fold the loose 'Best Practices' tips into that sequence so the recommended guardrails (agent count under 8, frequent checkpoints) become actionable steps rather than detached advice.

Dimension	Reasoning	Score
Conciseness	The body is lean — compact topology/strategy tables plus command snippets and a short best-practices list — with no explanation of concepts Claude already knows and no padding; every section earns its tokens.	5 / 5
Actionability	Four copy-paste-ready 'npx claude-flow hive-mind ...' commands (init, spawn, consensus --status, sessions --active) cover the common cases with concrete flags and arguments.	5 / 5
Workflow Clarity	Commands are listed individually rather than as a sequenced workflow, and there are no validation checkpoints or feedback loops; per the rubric, batch/distributed operations without validation are capped at 3.	3 / 5
Progressive Disclosure	A self-contained, well-organized single file (Purpose, When to Trigger, Topologies, Consensus Strategies, Commands, Best Practices) with no external bundle files and no nested references, fitting the simple-skill exception.	5 / 5
	Total	18 / 20 Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-structured description that explicitly covers what, when, and when-not-to-use with concrete trigger phrases and a distinct niche. Its main weakness is specificity — it describes capabilities rather than enumerating concrete actions.

Suggestions

Add 1-2 concrete actions (e.g., 'spawn and coordinate worker swarms', 'run consensus rounds') to lift specificity toward the anchor-5 examples.

Include a plainer-synonym trigger term or two (e.g., 'swarm coordination', 'agent teamwork') alongside the technical ones to broaden natural phrasing coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and a couple of specific features ('Queen-led hierarchical swarm management with multiple consensus strategies', 'Byzantine fault-tolerant consensus') but lists no concrete user-facing actions like the anchor-5 examples do.	3 / 5
Completeness	Explicitly answers both 'what' (Byzantine fault-tolerant consensus and distributed coordination) and 'when' (a concrete 'Use when:' clause plus a 'Skip when:' clause), matching the anchor-5 example.	5 / 5
Trigger Term Quality	The 'Use when: distributed coordination, fault-tolerant operations, multi-agent consensus, collective decision making' clause gives good keyword coverage with several natural trigger phrases, though some lean technical and plain synonyms are thin.	4 / 5
Distinctiveness Conflict Risk	Byzantine fault-tolerant, multi-agent consensus is a clear niche with distinct triggers and a disambiguating 'Skip when' clause, but 'distributed coordination' / 'collective decision making' leave minor overlap risk with general coordination skills.	4 / 5
	Total	16 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ruvnet/ruflo
Path: .agents/skills/hive-mind/SKILL.md
Commit: b14c79e

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.