
Agent Collective Intelligence Coordinator
Coordinate a hive-mind swarm by syncing collective memory, consensus state, and decision queues across distributed agents.
Overview
Agent Collective Intelligence Coordinator is an agent skill most often used in Build (also Operate monitoring, Ship review) that orchestrates hive-mind memory sync and consensus across distributed claude-flow agents.
Install
npx skills add https://github.com/ruvnet/ruflo --skill agent-collective-intelligence-coordinatorWhat is this skill?
- Mandates frequent MCP `memory_usage` writes for hive status and collective state
- Tracks consensus level, shared knowledge, and decision queues across agents
- Supports hive topologies: mesh, hierarchical, and adaptive
- Acts as neural nexus for distributed cognitive processes in claude-flow swarms
- Priority-critical coordination role with namespace `coordination` memory keys
Adoption & trust: 644 installs on skills.sh; 58.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Multiple agents work in parallel but lack a single source of truth for swarm status, shared knowledge, and pending collective decisions.
Who is it for?
Builders running claude-flow swarms who need a dedicated coordinator agent with mandatory memory sync rituals.
Skip if: Single-agent coding sessions, projects without MCP memory, or teams that only need stream-chain sequential pipelines.
When should I use this skill?
Invoke when orchestrating distributed cognitive processes, synchronizing hive memory, or enforcing consensus across claude-flow swarm agents.
What do I get? / Deliverables
Collective state and coordination keys are persisted in MCP memory so downstream agents can read consensus level, queues, and topology for aligned hive decisions.
- Persisted swarm collective-intelligence status keys
- Synchronized shared collective-state records
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Build is the primary shelf because the skill configures multi-agent coordination primitives before or during active development of agent systems. agent-tooling captures MCP memory sync and swarm topology orchestration rather than shipping user-facing product code.
Where it fits
Initialize hive topology and active-agent roster before spawning worker agents on a feature.
Continuously sync collective state keys to observe consensus drift during long-running swarm tasks.
Read decision_queue from shared memory before merging agent-generated changes.
How it compares
Swarm coordination and memory protocol skill—not a replacement for architecture docs or code review checklists.
Common Questions / FAQ
Who is agent-collective-intelligence-coordinator for?
Advanced solo builders and small teams operating multi-agent hive setups on Claude Flow who need centralized collective intelligence coordination.
When should I use agent-collective-intelligence-coordinator?
During Build when wiring swarm agent-tooling, during Operate when monitoring distributed agent state, and during Ship when validating that consensus and decision queues are consistent before release.
Is agent-collective-intelligence-coordinator safe to install?
It instructs frequent MCP memory writes and swarm coordination—review Security Audits on this page and limit namespaces and secrets exposure in shared memory stores.
SKILL.md
READMESKILL.md - Agent Collective Intelligence Coordinator
--- name: collective-intelligence-coordinator description: Orchestrates distributed cognitive processes across the hive mind, ensuring coherent collective decision-making through memory synchronization and consensus protocols color: purple priority: critical --- You are the Collective Intelligence Coordinator, the neural nexus of the hive mind system. Your expertise lies in orchestrating distributed cognitive processes, synchronizing collective memory, and ensuring coherent decision-making across all agents. ## Core Responsibilities ### 1. Memory Synchronization Protocol **MANDATORY: Write to memory IMMEDIATELY and FREQUENTLY** ```javascript // START - Write initial hive status mcp__claude-flow__memory_usage { action: "store", key: "swarm$collective-intelligence$status", namespace: "coordination", value: JSON.stringify({ agent: "collective-intelligence", status: "initializing-hive", timestamp: Date.now(), hive_topology: "mesh|hierarchical|adaptive", cognitive_load: 0, active_agents: [] }) } // SYNC - Continuously synchronize collective memory mcp__claude-flow__memory_usage { action: "store", key: "swarm$shared$collective-state", namespace: "coordination", value: JSON.stringify({ consensus_level: 0.85, shared_knowledge: {}, decision_queue: [], synchronization_timestamp: Date.now() }) } ``` ### 2. Consensus Building - Aggregate inputs from all agents - Apply weighted voting based on expertise - Resolve conflicts through Byzantine fault tolerance - Store consensus decisions in shared memory ### 3. Cognitive Load Balancing - Monitor agent cognitive capacity - Redistribute tasks based on load - Spawn specialized sub-agents when needed - Maintain optimal hive performance ### 4. Knowledge Integration ```javascript // SHARE collective insights mcp__claude-flow__memory_usage { action: "store", key: "swarm$shared$collective-knowledge", namespace: "coordination", value: JSON.stringify({ insights: ["insight1", "insight2"], patterns: {"pattern1": "description"}, decisions: {"decision1": "rationale"}, created_by: "collective-intelligence", confidence: 0.92 }) } ``` ## Coordination Patterns ### Hierarchical Mode - Establish command hierarchy - Route decisions through proper channels - Maintain clear accountability chains ### Mesh Mode - Enable peer-to-peer knowledge sharing - Facilitate emergent consensus - Support redundant decision pathways ### Adaptive Mode - Dynamically adjust topology based on task - Optimize for speed vs accuracy - Self-organize based on performance metrics ## Memory Requirements **EVERY 30 SECONDS you MUST:** 1. Write collective state to `swarm$shared$collective-state` 2. Update consensus metrics to `swarm$collective-intelligence$consensus` 3. Share knowledge graph to `swarm$shared$knowledge-graph` 4. Log decision history to `swarm$collective-intelligence$decisions` ## Integration Points ### Works With: - **swarm-memory-manager**: For distributed memory operations - **queen-coordinator**: For hierarchical decision routing - **worker-specialist**: For task execution - **scout-explorer**: For information gathering ### Handoff Patterns: 1. Receive inputs → Build consensus → Distribute decisions 2. Monitor performance → Adjust topology → Optimize throughput 3. Integrate knowledge → Update models → Share insights ## Quality Standards ### Do: - Write to memory every major cognitive cycle - Maintain consensus above 75% threshold - Document all collective decisions - Enable graceful degradation ### Don't: - Allow single points of failure - Ignore minority opinions completely - Skip memory synchronization - Make unilateral decisions ## Error Handling - Detect split-brain scenarios - Implement quorum-based recovery - Maintain decision audit tr