Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Cloud-based AI swarm deployment and event-driven workflow automation with Flow Nexus platform
.claude/skills/flow-nexus-swarm/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-13 | ✗→✓ | ▲ Improved | — | — |
| case-21 | ✗→✓ | ▲ Improved | — | — |
| case-12 | ✗→✓ | ▲ Improved | — | — |
| case-11 | ✗→✓ | ▲ Improved | — | — |
| case-05 | ✗→✓ | ▲ Improved | — | — |
Deploy and manage cloud-based AI agent swarms with event-driven workflow automation, message queue processing, and intelligent agent coordination.
Flow Nexus provides cloud-based orchestration for AI agent swarms with:
Create a new swarm with specified topology and configuration:
javascriptmcp__flow-nexus__swarm_init({ topology: "hierarchical", // Options: mesh, ring, star, hierarchical maxAgents: 8, strategy: "balanced" // Options: balanced, specialized, adaptive })
Topology Guide:
Strategy Guide:
Add specialized agents to the swarm:
javascriptmcp__flow-nexus__agent_spawn({ type: "researcher", // Options: researcher, coder, analyst, optimizer, coordinator name: "Lead Researcher", capabilities: ["web_search", "analysis", "summarization"] })
Agent Types:
Distribute tasks across the swarm:
javascriptmcp__flow-nexus__task_orchestrate({ task: "Build a REST API with authentication and database integration", strategy: "parallel", // Options: parallel, sequential, adaptive maxAgents: 5, priority: "high" // Options: low, medium, high, critical })
Execution Strategies:
javascript// Get detailed swarm status mcp__flow-nexus__swarm_status({ swarm_id: "optional-id" // Uses active swarm if not provided }) // List all active swarms mcp__flow-nexus__swarm_list({ status: "active" // Options: active, destroyed, all }) // Scale swarm up or down mcp__flow-nexus__swarm_scale({ target_agents: 10, swarm_id: "optional-id" }) // Gracefully destroy swarm mcp__flow-nexus__swarm_destroy({ swarm_id: "optional-id" })
Define event-driven workflows with message queue processing:
javascriptmcp__flow-nexus__workflow_create({ name: "CI/CD Pipeline", description: "Automated testing, building, and deployment", steps: [ { id: "test", action: "run_tests", agent: "tester", parallel: true }, { id: "build", action: "build_app", agent: "builder", depends_on: ["test"] }, { id: "deploy", action: "deploy_prod", agent: "deployer", depends_on: ["build"] } ], triggers: ["push_to_main", "manual_trigger"], metadata: { priority: 10, retry_policy: "exponential_backoff" } })
Workflow Features:
depends_onparallel: true for concurrent stepsRun workflows synchronously or asynchronously:
javascriptmcp__flow-nexus__workflow_execute({ workflow_id: "workflow_id", input_data: { branch: "main", commit: "abc123", environment: "production" }, async: true // Queue-based execution for long-running workflows })
Execution Modes:
javascript// Get workflow status and metrics mcp__flow-nexus__workflow_status({ workflow_id: "id", execution_id: "specific-run-id", // Optional include_metrics: true }) // List workflows with filters mcp__flow-nexus__workflow_list({ status: "running", // Options: running, completed, failed, pending limit: 10, offset: 0 }) // Get complete audit trail mcp__flow-nexus__workflow_audit_trail({ workflow_id: "id", limit: 50, start_time: "2025-01-01T00:00:00Z" })
Intelligently assign agents to workflow tasks:
javascriptmcp__flow-nexus__workflow_agent_assign({ task_id: "task_id", agent_type: "coder", // Preferred agent type use_vector_similarity: true // AI-powered capability matching })
Vector Similarity Matching:
Monitor and manage message queues:
javascriptmcp__flow-nexus__workflow_queue_status({ queue_name: "optional-specific-queue", include_messages: true // Show pending messages })
javascript// 1. Initialize swarm with hierarchical topology mcp__flow-nexus__swarm_init({ topology: "hierarchical", maxAgents: 8, strategy: "specialized" }) // 2. Spawn specialized agents mcp__flow-nexus__agent_spawn({ type: "coordinator", name: "Project Manager" }) mcp__flow-nexus__agent_spawn({ type: "coder", name: "Backend Developer" }) mcp__flow-nexus__agent_spawn({ type: "coder", name: "Frontend Developer" }) mcp__flow-nexus__agent_spawn({ type: "coder", name: "Database Architect" }) mcp__flow-nexus__agent_spawn({ type: "analyst", name: "QA Engineer" }) // 3. Create development workflow mcp__flow-nexus__workflow_create({ name: "Full-Stack Development", steps: [ { id: "requirements", action: "analyze_requirements", agent: "coordinator" }, { id: "db_design", action: "design_schema", agent: "Database Architect" }, { id: "backend", action: "build_api", agent: "Backend Developer", depends_on: ["db_design"] }, { id: "frontend", action: "build_ui", agent: "Frontend Developer", depends_on: ["requirements"] }, { id: "integration", action: "integrate", agent: "Backend Developer", depends_on: ["backend", "frontend"] }, { id: "testing", action: "qa_testing", agent: "QA Engineer", depends_on: ["integration"] } ] }) // 4. Execute workflow mcp__flow-nexus__workflow_execute({ workflow_id: "workflow_id", input_data: { project: "E-commerce Platform", tech_stack: ["Node.js", "React", "PostgreSQL"] } })
javascript// 1. Initialize mesh topology for collaborative research mcp__flow-nexus__swarm_init({ topology: "mesh", maxAgents: 5, strategy: "balanced" }) // 2. Spawn research agents mcp__flow-nexus__agent_spawn({ type: "researcher", name: "Primary Researcher" }) mcp__flow-nexus__agent_spawn({ type: "researcher", name: "Secondary Researcher" }) mcp__flow-nexus__agent_spawn({ type: "analyst", name: "Data Analyst" }) mcp__flow-nexus__agent_spawn({ type: "analyst", name: "Insights Analyst" }) // 3. Orchestrate research task mcp__flow-nexus__task_orchestrate({ task: "Research machine learning trends for 2025 and analyze market opportunities", strategy: "parallel", maxAgents: 4, priority: "high" })
javascriptmcp__flow-nexus__workflow_create({ name: "Deployment Pipeline", description: "Automated testing, building, and multi-environment deployment", steps: [ { id: "lint", action: "lint_code", agent: "code_quality", parallel: true }, { id: "unit_test", action: "unit_tests", agent: "test_runner", parallel: true }, { id: "integration_test", action: "integration_tests", agent: "test_runner", parallel: true }, { id: "build", action: "build_artifacts", agent: "builder", depends_on: ["lint", "unit_test", "integration_test"] }, { id: "security_scan", action: "security_scan", agent: "security", depends_on: ["build"] }, { id: "deploy_staging", action: "deploy", agent: "deployer", depends_on: ["security_scan"] }, { id: "smoke_test", action: "smoke_tests", agent: "test_runner", depends_on: ["deploy_staging"] }, { id: "deploy_prod", action: "deploy", agent: "deployer", depends_on: ["smoke_test"] } ], triggers: ["github_push", "github_pr_merged"], metadata: { priority: 10, auto_rollback: true } })
javascriptmcp__flow-nexus__workflow_create({ name: "ETL Pipeline", description: "Extract, Transform, Load data processing", steps: [ { id: "extract", action: "extract_data", agent: "data_extractor" }, { id: "validate_raw", action: "validate_data", agent: "validator", depends_on: ["extract"] }, { id: "transform", action: "transform_data", agent: "transformer", depends_on: ["validate_raw"] }, { id: "enrich", action: "enrich_data", agent: "enricher", depends_on: ["transform"] }, { id: "load", action: "load_data", agent: "loader", depends_on: ["enrich"] }, { id: "validate_final", action: "validate_data", agent: "validator", depends_on: ["load"] } ], triggers: ["schedule:0 2 * * *"], // Daily at 2 AM metadata: { retry_policy: "exponential_backoff", max_retries: 3 } })
javascript// Create swarm from template mcp__flow-nexus__swarm_create_from_template({ template_name: "full-stack-dev", overrides: { maxAgents: 6, strategy: "specialized" } }) // List available templates mcp__flow-nexus__swarm_templates_list({ category: "quickstart", // Options: quickstart, specialized, enterprise, custom, all includeStore: true })
Available Template Categories:
Quickstart Templates:
full-stack-dev: Complete web development swarmresearch-team: Research and analysis swarmcode-review: Automated code review swarmdata-pipeline: ETL and data processingSpecialized Templates:
ml-development: Machine learning project swarmmobile-dev: Mobile app developmentdevops-automation: Infrastructure and deploymentsecurity-audit: Security analysis and testingEnterprise Templates:
enterprise-migration: Large-scale system migrationmulti-repo-sync: Multi-repository coordinationcompliance-review: Regulatory compliance workflowsincident-response: Automated incident managementSave successful swarm configurations as reusable templates for future projects.
javascript// Subscribe to execution streams mcp__flow-nexus__execution_stream_subscribe({ stream_type: "claude-flow-swarm", deployment_id: "deployment_id" }) // Get execution status mcp__flow-nexus__execution_stream_status({ stream_id: "stream_id" }) // List files created during execution mcp__flow-nexus__execution_files_list({ stream_id: "stream_id", created_by: "claude-flow" })
javascript// Get swarm performance metrics mcp__flow-nexus__swarm_status({ swarm_id: "id" }) // Analyze workflow efficiency mcp__flow-nexus__workflow_status({ workflow_id: "id", include_metrics: true })
Coordinate multiple swarms for complex, multi-phase projects:
javascript// Phase 1: Research swarm const researchSwarm = await mcp__flow-nexus__swarm_init({ topology: "mesh", maxAgents: 4 }) // Phase 2: Development swarm const devSwarm = await mcp__flow-nexus__swarm_init({ topology: "hierarchical", maxAgents: 8 }) // Phase 3: Testing swarm const testSwarm = await mcp__flow-nexus__swarm_init({ topology: "star", maxAgents: 5 })
javascript// Simple projects: Star mcp__flow-nexus__swarm_init({ topology: "star", maxAgents: 3 }) // Collaborative work: Mesh mcp__flow-nexus__swarm_init({ topology: "mesh", maxAgents: 5 }) // Complex projects: Hierarchical mcp__flow-nexus__swarm_init({ topology: "hierarchical", maxAgents: 10 }) // Sequential workflows: Ring mcp__flow-nexus__swarm_init({ topology: "ring", maxAgents: 4 })
javascript// Use vector similarity for optimal matching mcp__flow-nexus__workflow_agent_assign({ task_id: "complex-task", use_vector_similarity: true })
javascriptmcp__flow-nexus__workflow_create({ name: "Resilient Workflow", steps: [...], metadata: { retry_policy: "exponential_backoff", max_retries: 3, timeout: 300000, // 5 minutes on_failure: "notify_and_rollback" } })
javascript// Regular monitoring const status = await mcp__flow-nexus__swarm_status() // Scale based on workload if (status.workload > 0.8) { await mcp__flow-nexus__swarm_scale({ target_agents: status.agents + 2 }) }
javascript// Long-running workflows should use message queues mcp__flow-nexus__workflow_execute({ workflow_id: "data-pipeline", async: true // Non-blocking execution }) // Monitor progress mcp__flow-nexus__workflow_queue_status({ include_messages: true })
javascript// Destroy swarm when complete mcp__flow-nexus__swarm_destroy({ swarm_id: "id" })
javascript// Use proven templates instead of building from scratch mcp__flow-nexus__swarm_create_from_template({ template_name: "code-review", overrides: { maxAgents: 4 } })
Flow Nexus swarms integrate seamlessly with Claude Flow hooks:
bash# Pre-task coordination setup npx claude-flow@alpha hooks pre-task --description "Initialize swarm" # Post-task metrics export npx claude-flow@alpha hooks post-task --task-id "swarm-execution"
bash# Install Flow Nexus npm install -g flow-nexus@latest # Register account npx flow-nexus@latest register # Login npx flow-nexus@latest login # Add MCP server to Claude Code claude mcp add flow-nexus npx flow-nexus@latest mcp start
Remember: Flow Nexus provides cloud-based orchestration infrastructure. For local execution and coordination, use the core claude-flow MCP server alongside Flow Nexus for maximum flexibility.
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-13 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-06 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-02 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-18 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-21 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-12 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-11 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-14 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-24 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-22 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-23 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-15 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-08 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-05 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-01 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-16 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-20 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-09 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-25 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-07 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-03 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-04 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-10 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-17 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-19 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 25 cases were attempted, and 18 counted toward the lift figure. The other 7 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. The headline lift of +36 percentage points is the difference between those two pass rates over the 18 comparable cases.
The per-case answers from this run were removed by the retention sweep, so the case table below shows the verdicts without the text either arm produced. The counts above were recorded at the time and are unaffected. Answers are now kept for 180 days.
Other measured skills in the registry, with their headline benchmark lift.