routing_agent

Classifies user intents and delegates tasks to Swarm specialists via Session State API.

4|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/dewitt/swarm --skill routing-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: routing_agent
Source: https://github.com/dewitt/swarm/tree/main/skills/routing-agent
Command: npx skills add https://github.com/dewitt/swarm --skill routing-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Classify user intents and route tasks to the most capable Swarm specialist, accelerating decision making and reducing handoff latency.

Core Features & Use Cases

  • Intent classification: quickly analyze user input and map it to the appropriate agent.
  • Specialist orchestration: delegate tasks to memory, planning, or domain-specific agents with clear handoffs.
  • Stateful coordination: leverage the Session State API to persist context across turns and ensure continuity.

Quick Start

Provide a user query to the routing agent and review the resulting delegated spans.

Frequently Asked Questions about routing_agent

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

FAQPage Schema
How do I route user intents to specialized agents in a multi-turn conversation?

Intent classification analyzes user input to map queries to the appropriate Swarm specialist. It leverages a decision taxonomy and session-state access to drive agent spans, accelerating decision-making and reducing handoff latency.

How does session-state access work when orchestrating multiple agents?

Specialist orchestration delegates tasks to memory, planning, or domain-specific agents with clear handoffs. It implements a decision taxonomy to map user intents and generates an orchestration payload to drive agent spans.

What is the best way to classify user intents for rapid agent handoffs?

To route user intents to specialized agents, classify the user input and delegate the task to the appropriate Swarm specialist using an orchestration payload. This persists context across turns via the Session State API to ensure continuity.

Can I use this routing approach for memory and planning agents simultaneously?

Yes, you can route intents to memory and planning agents simultaneously. The routing agent classifies user intents and delegates tasks to the appropriate Swarm specialists, enabling rapid routing between memory, planning, and domain-specific agents during multi-turn conversations.

Why does agent orchestration require a decision taxonomy?

Agent orchestration requires a decision taxonomy to accurately classify user intents and determine the correct specialist for delegation. This structured classification reduces handoff latency and ensures tasks reach the most capable Swarm specialist.

When should I not use a dedicated routing agent for task delegation?

You should not use a dedicated routing agent for simple, single-turn queries that do not require stateful coordination. It is specifically designed for multi-turn conversations requiring rapid routing between memory, planning, and specialized agents with persistent session-state.