swarm

Routes swarm invocations to the Team skill's staged pipeline for task execution.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/lpjhelder/kronon-forge --skill swarm-lpjhelder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swarm
Source: https://github.com/lpjhelder/kronon-forge/tree/main/skills/swarm
Command: npx skills add https://github.com/lpjhelder/kronon-forge --skill swarm-lpjhelder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Swarm provides a compatibility alias that routes swarm invocations to the Team skill's staged pipeline, unifying multi-agent coordination workflows.

Core Features & Use Cases

  • Compatibility alias for /team so existing /swarm invocations are automatically handled by the Team skill's pipeline.
  • Shared task coordination and agent routing leverage the Team skill's orchestration model for consistent execution across agents.

Quick Start

Invoke /swarm with an agent-type and description to route through the Team skill's staged pipeline.

Frequently Asked Questions about swarm

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

FAQPage Schema
How do I coordinate multiple agents on a shared task list?

Multi-agent coordination is handled by routing /swarm commands to the Team skill's staged pipeline, which provides shared task coordination and agent routing for consistent execution across multiple agents.

What is a swarm workflow for agent orchestration?

A swarm workflow provides multi-agent orchestration by mapping commands to the Team skill's staged pipeline, unifying task coordination and routing semantics for shared task execution.

How do I use /swarm commands for multi-agent task execution?

You use /swarm commands by providing an agent-type and task description, which routes the invocation to the Team skill's staged pipeline to handle the execution and coordination.

Do I need the Team skill to run swarm orchestration?

Yes, the swarm orchestration relies entirely on the Team skill's pipeline, documentation, and coordination semantics to function correctly and route multi-agent tasks.

Are there limitations when using swarm as a compatibility alias for team coordination?

The primary limitation is that swarm functions solely as a compatibility alias for the Team skill, meaning it depends completely on the Team skill's pipeline and cannot operate independently.