Deploys and orchestrates AI agent swarms and event-driven workflows using the Flow Nexus platform.
Install
mkdir -p .claude/skills/flow-nexus-swarm && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6225" && unzip -o skill.zip -d .claude/skills/flow-nexus-swarm && rm skill.zipInstalls to .claude/skills/flow-nexus-swarm
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Cloud-based AI swarm deployment and event-driven workflow automation with Flow Nexus platformKey capabilities
- →Initialize multi-topology agent swarms
- →Configure event-driven message queue processing
- →Orchestrate distributed AI agent task execution
- →Deploy scalable agent swarms in the cloud
How it works
Uses a provider-specific MCP interface to distribute tasks across a swarm of agents configured via a hierarchical or star topology.
Inputs & outputs
When to use flow-nexus-swarm
- →Deploying AI agent swarms
- →Building event-driven workflows
- →Managing distributed agent orchestration
- →Setting up message queue processing
About this skill
Flow Nexus Swarm & Workflow Orchestration
Deploy and manage cloud-based AI agent swarms with event-driven workflow automation, message queue processing, and intelligent agent coordination.
📋 Table of Contents
- Overview
- Swarm Management
- Workflow Automation
- Agent Orchestration
- Templates & Patterns
- Advanced Features
- Best Practices
Overview
Flow Nexus provides cloud-based orchestration for AI agent swarms with:
- Multi-topology Support: Hierarchical, mesh, ring, and star architectures
- Event-driven Workflows: Message queue processing with async execution
- Template Library: Pre-built swarm configurations for common use cases
- Intelligent Agent Assignment: Vector similarity matching for optimal agent selection
- Real-time Monitoring: Comprehensive metrics and audit trails
- Scalable Infrastructure: Cloud-based execution with auto-scaling
Swarm Management
Initialize Swarm
Create a new swarm with specified topology and configuration:
mcp__flow-nexus__swarm_init({
topology: "hierarchical", // Options: mesh, ring, star, hierarchical
maxAgents: 8,
strategy: "balanced" // Options: balanced, specialized, adaptive
})
Topology Guide:
- Hierarchical: Tree structure with coordinator nodes (best for complex projects)
- Mesh: Peer-to-peer collaboration (best for research and analysis)
- Ring: Circular coordination (best for sequential workflows)
- Star: Centralized hub (best for simple delegation)
Strategy Guide:
- Balanced: Equal distribution of workload across agents
- Specialized: Agents focus on specific expertise areas
- Adaptive: Dynamic adjustment based on task complexity
Spawn Agents
Add specialized agents to the swarm:
mcp__flow-nexus__agent_spawn({
type: "researcher", // Options: researcher, coder, analyst, optimizer, coordinator
name: "Lead Researcher",
capabilities: ["web_search", "analysis", "summarization"]
})
Agent Types:
- Researcher: Information gathering, web search, analysis
- Coder: Code generation, refactoring, implementation
- Analyst: Data analysis, pattern recognition, insights
- Optimizer: Performance tuning, resource optimization
- Coordinator: Task delegation, progress tracking, integration
Orchestrate Tasks
Distribute tasks across the swarm:
mcp__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:
- Parallel: Maximum concurrency for independent subtasks
- Sequential: Step-by-step execution with dependencies
- Adaptive: AI-powered strategy selection based on task analysis
Monitor & Scale Swarms
// 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"
})
Workflow Automation
Create Workflow
Define event-driven workflows with message queue processing:
mcp__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:
- Dependency Management: Define step dependencies with
depends_on - Parallel Execution: Set
parallel: truefor concurrent steps - Event Triggers: GitHub events, schedules, manual triggers
- Retry Policies: Automatic retry on transient failures
- Priority Queuing: High-priority workflows execute first
Execute Workflow
Run workflows synchronously or asynchronously:
mcp__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:
- Sync (async: false): Immediate execution, wait for completion
- Async (async: true): Message queue processing, non-blocking
Monitor Workflows
// 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"
})
Agent Assignment
Intelligently assign agents to workflow tasks:
mcp__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:
- Analyzes task requirements and agent capabilities
- Finds optimal agent based on past performance
- Considers workload and availability
Queue Management
Monitor and manage message queues:
mcp__flow-nexus__workflow_queue_status({
queue_name: "optional-specific-queue",
include_messages: true // Show pending messages
})
Agent Orchestration
Full-Stack Development Pattern
// 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"]
}
})
Research & Analysis Pattern
// 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"
})
CI/CD Pipeline Pattern
mcp__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
}
})
Data Processing Pipeline Pattern
mcp__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",
---
*Content truncated.*
When not to use it
- →Running single-threaded scripts
- →Direct database operations
Prerequisites
Limitations
- →Requires external platform connectivity
- →Agent effectiveness depends on chosen configuration strategy
How it compares
It shifts from local agent execution to cloud-based, multi-topology swarm management.
Compared to similar skills
flow-nexus-swarm side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| flow-nexus-swarm (this skill) | 1 | 6mo | Review | Advanced |
| swarm-advanced | 7 | 4mo | Review | Advanced |
| hosted-agents | 1 | 2mo | Review | Advanced |
| station | 0 | 7mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by ruvnet
View all by ruvnet →You might also like
swarm-advanced
ruvnet
Advanced swarm orchestration patterns for research, development, testing, and complex distributed workflows
hosted-agents
muratcankoylan
This skill should be used when the user asks to "build background agent", "create hosted coding agent", "set up sandboxed execution", "implement multiplayer agent", or mentions background agents, sandboxed VMs, agent infrastructure, Modal sandboxes, self-spawning agents, or remote coding environments.
station
cloudshipai
Use Station CLI (`stn`) for AI agent orchestration - creating agents, running tasks, managing environments, and deploying agent teams. Prefer CLI for file operations and exploration; use MCP tools for programmatic agent execution and detailed queries.
opencode-cli
SpillwaveSolutions
This skill should be used when configuring or using the OpenCode CLI for headless LLM automation. Use when the user asks to "configure opencode", "use opencode cli", "set up opencode", "opencode run command", "opencode model selection", "opencode providers", "opencode vertex ai", "opencode mcp servers", "opencode ollama", "opencode local models", "opencode deepseek", "opencode kimi", "opencode mistral", "fallback cli tool", or "headless llm cli". Covers command syntax, provider configuration, Vertex AI setup, MCP servers, local models, cloud providers, and subprocess integration patterns.
claude-automation-recommender
anthropics
Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.
applescript
martinholovsky
Expert in AppleScript and JavaScript for Automation (JXA) for macOS system scripting. Specializes in secure script execution, application automation, and system integration. HIGH-RISK skill due to shell command execution and system-wide control capabilities.