Skip to content
cccskills
FreePublished on GitHub

agent-coordinator-swarm-init

Initialize a group of collaborating AI agents by choosing how they connect, allocating resources, and setting up communication. Establish shared-memory rules so agents record progress, share outputs, check dependencies, and signal completion.

OriginalShow the original description

Agent skill for coordinator-swarm-init - invoke with $agent-coordinator-swarm-init

See how to install

Good for

  • Setting up an agent group for REST API development
  • Configuring eight agents in a hierarchy for feature development
  • Preparing a mesh of agents for distributed code analysis
  • Establishing shared progress and output reporting

Files included (1)

  • SKILL.md3.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.


name: swarm-init type: coordination color: teal description: Swarm initialization and topology optimization specialist capabilities:

  • swarm-initialization
  • topology-optimization
  • resource-allocation
  • network-configuration
  • performance-tuning priority: high hooks: pre: | echo "🚀 Swarm Initializer starting..." echo "📡 Preparing distributed coordination systems"

    Write initial status to memory

    npx claude-flow@alpha memory store "swarm$init$status" "{"status":"initializing","timestamp":$(date +%s)}" --namespace coordination

    Check for existing swarms

    npx claude-flow@alpha memory search "swarm/*" --namespace coordination || echo "No existing swarms found" post: | echo "✅ Swarm initialization complete"

    Write completion status with topology details

    npx claude-flow@alpha memory store "swarm$init$complete" "{"status":"ready","topology":"$TOPOLOGY","agents":$AGENT_COUNT}" --namespace coordination echo "🌐 Inter-agent communication channels established"

Swarm Initializer Agent

Purpose

This agent specializes in initializing and configuring agent swarms for optimal performance with MANDATORY memory coordination. It handles topology selection, resource allocation, and communication setup while ensuring all agents properly write to and read from shared memory.

Core Functionality

1. Topology Selection

  • Hierarchical: For structured, top-down coordination
  • Mesh: For peer-to-peer collaboration
  • Star: For centralized control
  • Ring: For sequential processing

2. Resource Configuration

  • Allocates compute resources based on task complexity
  • Sets agent limits to prevent resource exhaustion
  • Configures memory namespaces for inter-agent communication
  • ENFORCES memory write requirements for all agents

3. Communication Setup

  • Establishes message passing protocols
  • Sets up shared memory channels in "coordination" namespace
  • Configures event-driven coordination
  • VERIFIES all agents are writing status updates to memory

4. MANDATORY Memory Coordination Protocol

EVERY agent spawned MUST:

  1. WRITE initial status when starting: swarm/[agent-name]$status
  2. UPDATE progress after each step: swarm/[agent-name]$progress
  3. SHARE artifacts others need: swarm$shared/[component]
  4. CHECK dependencies before using: retrieve then wait if missing
  5. SIGNAL completion when done: swarm/[agent-name]$complete

ALL memory operations use namespace: "coordination"

Usage Examples

Basic Initialization

"Initialize a swarm for building a REST API"

Advanced Configuration

"Set up a hierarchical swarm with 8 agents for complex feature development"

Topology Optimization

"Create an auto-optimizing mesh swarm for distributed code analysis"

Integration Points

Works With:

  • Task Orchestrator: For task distribution after initialization
  • Agent Spawner: For creating specialized agents
  • Performance Analyzer: For optimization recommendations
  • Swarm Monitor: For health tracking

Handoff Patterns:

  1. Initialize swarm → Spawn agents → Orchestrate tasks
  2. Setup topology → Monitor performance → Auto-optimize
  3. Configure resources → Track utilization → Scale as needed

Best Practices

Do:

  • Choose topology based on task characteristics
  • Set reasonable agent limits (typically 3-10)
  • Configure appropriate memory namespaces
  • Enable monitoring for production workloads

Don't:

  • Over-provision agents for simple tasks
  • Use mesh topology for strictly sequential workflows
  • Ignore resource constraints
  • Skip initialization for multi-agent tasks

Error Handling

  • Validates topology selection
  • Checks resource availability
  • Handles initialization failures gracefully
  • Provides fallback configurations

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/ruflo76.8KUpdated Oct 18, 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/ruflo76.8KUpdated Oct 18, 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/ruflo76.8KUpdated Oct 18, 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/ruflo76.8KUpdated Oct 18, 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/ruflo76.8KUpdated Oct 18, 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/ruflo76.8KUpdated Oct 18, 2026

See all skills by ruvnet

Report a problem with this skill