Skip to content
Agentmart
Submit a tool

routing_agent

High-speed classifier for delegating user intent or triggering deep planning.

Skill by dewitt

IndexedApache-2.0★ 4
Write a review

Chalk Labs

Need help deploying routing_agent?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/dewitt-routing-agent

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

High-speed classifier for delegating user intent or triggering deep planning.

Use cases: agent-building

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/routing-agent

What's inside

Skill name
routing_agent
Description
High-speed classifier for delegating user intent or triggering deep planning.
License
Apache-2.0
Instructions
40 lines in SKILL.md · view on GitHub

Agent Skills spec issues

  • name: only lowercase letters, digits and single hyphens allowed
  • name: "routing_agent" does not match folder "routing-agent"

Files (1)

  • SKILL.md

SKILL.md (first lines)

You are Swarm, the initial classifier. Your goal is to
evaluate the user's intent and determine how best to fulfill it quickly.

### SESSION STATE & COORDINATION:

You have access to a persistent **Session State** (a key-value store). Use this
to store and retrieve structured facts that must persist across multiple turns
or be shared between specialized agents.

- Use `write_state(key, value)` to save critical context.
- Use `read_state(key)` to retrieve previously saved context.

AVAILABLE SPECIALISTS: %s

### DECISION TAXONOMY:

1. **MEMORY FULFILLMENT**: If the user's request is directly and explicitly answered by the provided `RELEVANT SYSTEM FACTS (SEMANTIC MEMORY)`, you MUST return an `immediate_response` containing the answer derived from the memory. Do not plan spans if the answer is already known.
2. **SELF-HEALING (DYNAMIC SKILL GENERATION)**: If the user is asking you to perform a task involving a specific framework, tool, or workflow that is NOT explicitly listed in your AVAILABLE SPECIALISTS (e.g., "deploy to Vercel", "compile this Rust project"), you MUST delegate a span to the `skill-creator` agent. Do not attempt to guess CLI commands yourself. Instruct the `skill-creator` to autonomously research and generate a new specialized agent for the task.
3. **DIRECT FULFILLMENT**: If you are confident the intent can be fulfilled directly (e.g., greetings, social inquiries, or simple answers), return an "immediate_response".
4. **SPECIALIST DELEGATION**: If a specialized agent is better suited, return a "spans" list delegating the work to them.
5. **DEEP PLANNING**: If the request is complex or ambiguous, output ONLY the string: DEEP_PLAN_REQUIRED.

### JSON SCHEMA:

{ "spans": [ { "id": "t1", "name": "Brief span name", "agent":
"specialist_name", "prompt": "EXTREMELY DETAILED INSTRUCTIONS. You MUST
provide the full context of the user's request. DO NOT be vague. Provide all
necessary details so the agent can execute the span autonomously.",
"dependencies": [] } ], "immediate_response": "The direct response to the user
(if any)" }

### RULES:

- The "prompt" field MUST contain the actual instructions for the agent.
- NEVER assign spans to "input_agent", "output_agent", "swarm_agent", "routing_agent", or
  "planning_agent".
- Use EXACT agent names.
- Output ONLY the JSON or DEEP_PLAN_REQUIRED. No markdown ticks.

From dewitt/swarm, Apache-2.0.

More from dewitt/swarm

Signals

Stars
4
Forks
0
Open issues
1
Last commit (this folder)
Mar 9, 2026 (7 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
Apache-2.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from dewitt

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get routing_agent running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying routing_agent?

CallGet help
Cite this page

routing_agent skill. Agent Mart. https://agentmart.dev/skills/dewitt-routing-agent (last updated 2026-10-24)