do

Automating intent routing involves classifying user input and directing execution to the cheapest capable orchestrator or skill. This unified router uses SKILL.md frontmatter to build live routing tables, eliminating manual tool selection across single-session or multi-skill campaigns.

Intent classification for workflow orchestration determines the appropriate orchestrator or skill for a given task. It reads installed SKILL.md frontmatter to build a routing registry, applying tiered routing that prefers direct actions, then single-skill routes, then complex orchestrators.

Yes, automatic skill discovery requires every installed skill to expose a SKILL.md frontmatter with name and description fields. The router reads this frontmatter to build live routing tables and provide fallback paths for cost-effective execution.

The best way to manage multi-skill campaigns is using a unified router that automatically discovers installed skills and routes execution to the most cost-effective path. It supports status checks, list views, and direct invocation for power users.

Yes, a unified router applies across single-session tasks to multi-skill campaigns. It uses tiered routing to escalate from direct actions to single-skill routes, and finally to complex orchestrators like marshal, archon, or fleet as needed.

Automatic skill discovery fails when installed skills do not expose a SKILL.md frontmatter with valid name and description fields. The router requires this metadata to classify user intent, build routing tables, and execute fallback paths correctly.