agent-coordinator-swarm-init
Agent skill for coordinator-swarm-init - invoke with $agent-coordinator-swarm-init
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- agent-coordinator-swarm-init
- description
- Agent skill for coordinator-swarm-init - invoke with $agent-coordinator-swarm-init
03 SKILL.md 正文
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 coordinationCheck 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:
- WRITE initial status when starting:
swarm/[agent-name]$status - UPDATE progress after each step:
swarm/[agent-name]$progress - SHARE artifacts others need:
swarm$shared/[component] - CHECK dependencies before using: retrieve then wait if missing
- 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:
- Initialize swarm → Spawn agents → Orchestrate tasks
- Setup topology → Monitor performance → Auto-optimize
- 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
04 同仓库更多 Skills
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.