auto

# auto — Intent Router The front door to OrchestKit. **You describe a goal in plain English; the router classifies it and hands off to the right specialist.** One entry point, many execution paths. > **Why this exists:** OrchestKit has 107 skills, but usage telemetry shows users fire only the handful they can name by memory (10 distinct skills across thousands of sessions). The dominant cause of "dead" skills is **no front door** — not low quality. This router turns "you must know the exact `/ork:<name>`" into "describe what you want." **Core principle:** routing is a *deterministic workflow*, not an autonomous agent (Anthropic, *Building Effective Agents*). Classify → confirm → hand off. The router never does the work itself — it picks who does. ## When to use **By default, for any goal-shaped request.** An unambiguous goal is a 1-step route: auto classifies, confirms in one line, and hands off — no extra hops, so there is no "too obvious for auto". | Use `auto` for… | Skip only when… | |---|---| | Any goal description ("fix X", "get Y to Z") | Already executing inside another skill (no recursion) | | The right skill isn't obvious | Chaining a known multi-skill workflow you're mid-way through | | You think you know the skill — auto confirms & short-circuits | | > **Design note (2026-07-12):** this table previously said "Go direct when you > already know the skill / the request maps unambiguously to one". That inverted > instruction made the front door structurally unr...