swarm

Route swarm invocations to the Team skill's staged pipeline.

2|2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/chrisxue90/oh-my-qwencode --skill swarm-chrisxue90
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swarm
Source: https://github.com/chrisxue90/oh-my-qwencode/tree/main/skills/swarm
Command: npx skills add https://github.com/chrisxue90/oh-my-qwencode --skill swarm-chrisxue90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Swarm provides a compatibility alias for the /team skill, so users can invoke swarm commands and have them executed through the Team skill's staged pipeline, avoiding duplicate implementations.

Core Features & Use Cases

  • Alias routing: swarm invocations are forwarded to the Team skill's pipeline.
  • Consistent behavior: uses the same staged pipeline, agents routing, and coordination semantics as Team.
  • Transition helper: enables gradual migration from swarm to Team without changing user prompts.

Quick Start

Invoke /swarm with your task description to route it to the Team workflow.

Frequently Asked Questions about swarm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route swarm calls to a staged agent coordination pipeline?

You can route swarm calls by invoking this alias layer, which forwards prompts directly to the Team skill's staged pipeline for agent routing and task coordination without requiring duplicate implementations.

What is the best way to migrate from swarm prompts to a team workflow?

The best way to migrate from swarm prompts to a team workflow is using a compatibility alias that forwards commands to the Team skill, enabling gradual migration without changing existing user prompts.

Does the swarm alias layer preserve instruction semantics when routing tasks?

Yes, the swarm alias layer preserves instruction semantics during task routing, ensuring that forwarded invocations execute through the Team skill's staged pipeline with consistent agent coordination behavior.

Can I use swarm commands for multi-agent task coordination?

You can use swarm commands for multi-agent task coordination because the alias layer forwards invocations to the Team skill's pipeline, utilizing its established agents routing and coordination semantics for execution.

Why does the swarm workflow avoid duplicate implementations for agent routing?

The swarm workflow avoids duplicate implementations by acting as a compatibility alias that directly routes calls to the Team skill's existing staged pipeline, rather than maintaining a separate agent coordination logic.