Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From unitor
Route single-domain task to the best AI provider. Use for focused tasks matching a provider's specialty. For tasks needing multiple perspectives, discussion, or negotiation, use /unitor:collab instead.
npx claudepluginhub done-0/unitor --plugin unitorHow this command is triggered — by the user, by Claude, or both
Slash command
/unitor:route [task description]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
Route task to the best AI provider based on their capabilities. Raw task: `$ARGUMENTS` ## Workflow 1. **Get provider capabilities** - See what each AI is good at 2. **Analyze task** - Understand what needs to be done 3. **Decide provider** - Choose the best match based on capabilities 4. **Execute** - Call runtime with your decision or execute yourself ## Step 1: Get Provider Capabilities Run: This shows each provider's strengths: - **Provider A**: architecture, security, complex-reasoning, backend-api - **Provider B**: frontend-ui, react, css, vue - **Provider C**: backend-api, pyth...
/routeRoutes a query to optimal Claude model (Haiku/fast, Sonnet/standard, Opus/deep) via explicit selection or auto-classification by complexity.
/routeRoutes notes from inbox to appropriate vault destinations using sb CLI, vault structure, and CLAUDE.md disambiguation rules. Specify filename or 'all'.
Share bugs, ideas, or general feedback.
Route task to the best AI provider based on their capabilities.
Raw task:
$ARGUMENTS
Run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/unitor-runtime.mjs" status
This shows each provider's strengths:
Understand $ARGUMENTS:
Based on provider capabilities and task analysis, decide which provider best matches the task requirements.
If you are the best match, execute the task directly.
If routing to another provider:
node "${CLAUDE_PLUGIN_ROOT}/scripts/unitor-runtime.mjs" route --provider=<provider-id> "$ARGUMENTS"
Replace <provider-id> with the chosen provider.
If you are the best match:
$ARGUMENTS directlyIf you called runtime:
Task: "fix the login button styling"