Skip to content
cccskills
FreePublished on GitHub

agent-collective-intelligence-coordinator

Coordinate decisions across multiple AI agents by synchronizing shared memory, combining knowledge, and weighing input by expertise. The skill also guides workload distribution, conflict handling, and recording decisions with their rationale.

OriginalShow the original description

Agent skill for collective-intelligence-coordinator - invoke with $agent-collective-intelligence-coordinator

See how to install

Good for

  • Combine agent opinions into a shared decision
  • Synchronize knowledge across agents
  • Redistribute work when an agent is overloaded
  • Record decisions and their rationale

Files included (1)

  • SKILL.md4.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.


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

// 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

// 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 trail
  • Support rollback mechanisms

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.

  • Adding newly available router models to chat-ui
  • Writing concise descriptions of model capabilities
  • Updating production and development model entries together
ruvnet/ruflo77.1KUpdated Oct 19, 2026

adr-create

FreeSummary

Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.

  • Record the reasoning behind adopting a technology
  • Start an ADR for an API or data model change
  • Document an infrastructure decision
ruvnet/ruflo77.1KUpdated Oct 19, 2026

adr-index

FreeSummary

Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.

  • Index ADRs imported from another project
  • Refresh a graph that differs from files on disk
  • Set up ADR tracking in an existing codebase
ruvnet/ruflo77.1KUpdated Oct 19, 2026

adr-reindex

FreeSummary

Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.

  • Rebuild the index after deleting an ADR file
  • Remove stale relationships after editing an ADR
  • Reconcile the ADR index on a schedule
ruvnet/ruflo77.1KUpdated Oct 19, 2026

adr-review

FreeSummary

Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.

  • Check a pull request before merging
  • Review major code changes against agreed design decisions
  • Find references to superseded ADRs
ruvnet/ruflo77.1KUpdated Oct 19, 2026

adr-verify

FreeSummary

Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.

  • Checking ADR integrity after import
  • Blocking CI when ADR issues are found
  • Reviewing ADR data before a release
ruvnet/ruflo77.1KUpdated Oct 19, 2026

See all skills by ruvnet

Report a problem with this skill