hive-mind-advanced

Advanced Hive Mind collective intelligence system for queen-led multi-agent coordination with consensus mechanisms and persistent memory

1.88x

Quality

17%

Does it follow best practices?

Impact

100%

1.88x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/hive-mind-advanced/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 reads like a marketing tagline rather than a functional skill description. It is packed with buzzwords ('collective intelligence', 'consensus mechanisms', 'persistent memory') but fails to describe any concrete actions or provide trigger guidance. A user or Claude would struggle to know when to select this skill or what it actually does.

Suggestions

Replace abstract buzzwords with concrete actions the skill performs, e.g., 'Coordinates multiple agents to collaboratively solve tasks, aggregates responses, and resolves conflicts through voting mechanisms.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user requests multi-agent collaboration, parallel task execution, or coordinated problem-solving across multiple Claude instances.'

Remove or clarify jargon like 'queen-led' and 'Hive Mind' that users would not naturally use in requests, and instead describe the functionality in plain language.

Dimension	Reasoning	Score
Specificity	The description uses abstract, buzzword-heavy language ('collective intelligence system', 'consensus mechanisms', 'persistent memory') without listing any concrete actions the skill performs. There are no specific verbs describing what it actually does.	1 / 3
Completeness	The description vaguely addresses 'what' (a collective intelligence system) but provides no 'when' clause or explicit trigger guidance. There is no 'Use when...' or equivalent, and the 'what' itself is too abstract to be useful.	1 / 3
Trigger Term Quality	The terms used ('Hive Mind', 'queen-led multi-agent coordination', 'consensus mechanisms') are highly technical jargon that users would almost never naturally say when requesting help. No common user-facing keywords are present.	1 / 3
Distinctiveness Conflict Risk	The highly specific jargon ('Hive Mind', 'queen-led') does create some distinctiveness that would reduce conflicts with other skills, but the vagueness of the actual capabilities could still cause confusion about when to select it versus other multi-agent or coordination skills.	2 / 3
	Total	5 / 12 Passed

Implementation

27%

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

This skill is a comprehensive but severely bloated reference document that tries to be everything at once — tutorial, API reference, configuration guide, troubleshooting manual, and best practices guide — all in a single file. While it contains useful concrete commands and code examples, the sheer volume (~500+ lines) undermines its utility as a skill file, and it explains many concepts Claude already understands. The lack of bundle files means all content is crammed into one monolithic document with no progressive disclosure.

Suggestions

Split into multiple files: keep SKILL.md as a concise overview (~80-100 lines) with Quick Start and key commands, then move API reference, configuration, troubleshooting, and examples into separate referenced files.

Remove explanatory content Claude already knows (what Byzantine fault tolerance is, what LRU caches do, what WAL mode is, worker role descriptions) and focus only on tool-specific syntax and configuration.

Add explicit validation checkpoints to the core workflow: after init verify the hive is ready, after spawn verify agents are running, include error recovery steps inline rather than in a distant troubleshooting section.

Fix incomplete code examples: the createTask call has a syntax error, API examples need import/setup context, and pseudocode comments like '// Automatic - no configuration needed' should either show actual code or be removed.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~500+ lines. Explains concepts Claude already knows (what Byzantine fault tolerance is, what LRU caches are, what WAL mode is). Includes extensive API references, skill progression ladders, and related skills sections that bloat the document. Much of this content (API reference, memory types, worker specialization lists) should be in separate files or omitted entirely.	1 / 3
Actionability	Provides concrete CLI commands and JavaScript code snippets that are mostly executable. However, many code examples are incomplete (e.g., the createTask example has a syntax error with misplaced priority parameter), some are pseudocode-like with placeholder comments ('// Automatic - no configuration needed'), and the JavaScript API examples lack import statements or setup context needed to actually run them.	2 / 3
Workflow Clarity	The Getting Started section provides a reasonable 3-step sequence (init → spawn → monitor), but lacks validation checkpoints. There's no explicit verification after initialization, no error handling guidance in the main workflow, and the troubleshooting section is separated far from the workflows it supports. For a system involving multi-agent coordination with potential failures, missing feedback loops in the core workflow is a significant gap.	2 / 3
Progressive Disclosure	Monolithic wall of text with everything inlined — API references, configuration schemas, troubleshooting, examples, best practices, and skill progression all in one massive file. References at the bottom point to external docs but no bundle files are provided. The content desperately needs splitting into separate files (API_REFERENCE.md, CONFIGURATION.md, TROUBLESHOOTING.md, EXAMPLES.md) with the SKILL.md serving as a concise overview.	1 / 3
	Total	6 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (713 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: ruvnet/agentic-flow
Commit: 6a06854

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