Skill Market

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.

GitHub
githubcommunityclaude
0.0
0 installs73.4K GitHub starsby ruvnet

Skill Introduction

Overview
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.

Core value

Turns reusable Other know-how into an installable skill, helping users complete github, community, claude work faster.

Target users

  • Developers, testers, and maintainers who handle Other tasks in Focus Code.
  • Teams that already trust workflows or content from ruvnet.
  • Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

  • Read the skill content first to confirm required inputs, expected outputs, and dependencies.
  • Try it on a small task before relying on it for critical work.
  • Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
  • For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

  • Tasks related to github, community, claude that need a reusable execution flow.
  • Converting a community repo, team convention, or personal workflow into day-to-day assistance.
  • Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

  • Results depend on the quality of the original skill content and may need human correction.
  • It does not replace code review, tests, security review, or professional judgment.
  • External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

  • Structured around Other, making it easier to discover and reuse than loose prompt snippets.
  • Marked as GitHub, which helps users judge trust and maintenance expectations.
  • Keeps the original source link available for repository, documentation, or discussion follow-up.
  • Tagged with github, community, claude, so it can be filtered by concrete task intent.

Install and use

Install
Copy Install Command
focus install hive-mind-888586
View source

Detail Preview

SKILL.md

Primary filemarkdown2 KB

name: hive-mind description: > 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.

Hive-Mind Skill

Purpose

Byzantine fault-tolerant consensus and distributed swarm coordination.

When to Trigger

  • Multi-agent distributed tasks
  • Fault-tolerant operations needed
  • Collective decision making
  • Complex coordination patterns

Topologies

TopologyDescriptionUse Case
hierarchicalQueen controls workersDefault, anti-drift
meshFully connected peersResearch, exploration
hierarchical-meshHybridRecommended for complex
adaptiveDynamic based on loadAuto-scaling

Consensus Strategies

StrategyToleranceUse Case
byzantinef < n/3 faultyUntrusted environment
raftf < n/2 faultyLeader-based, consistent
gossipEventualLarge scale, availability
crdtConflict-freeConcurrent updates
quorumConfigurableTunable consistency

Commands

Initialize Hive-Mind

npx claude-flow hive-mind init --topology hierarchical-mesh --consensus raft

Spawn Queen

npx claude-flow hive-mind spawn --role queen --name coordinator

Check Consensus Status

npx claude-flow hive-mind consensus --status

View Sessions

npx claude-flow hive-mind sessions --active

Best Practices

  1. Use hierarchical for coding tasks (anti-drift)
  2. Use raft consensus for consistency
  3. Keep agent count under 8 for coordination
  4. Run frequent checkpoints

Reviews

Overall rating

0.0
0.0

0 comments

No reviews yet