
multi-model-orchestrator
Delegate tasks to specialist LLM CLIs based on their strengths
- version
- 0.1.0
Install
/plugin install multi-model-orchestrator@multi-model-cli-orchestratorRun it inside Claude Code after adding the marketplace with /plugin marketplace add syedadeel2/multi-model-cli-orchestrator.
Contents
Discovered from sourceSkills 1
Delegate to Specialist CLI
When the user uses @cli syntax (e.g., @kimi, @gemini, @codex), delegate the task to that CLI.
Syntax
@kimi <task>- Delegate to Kimi (frontend/design specialist)@gemini <task>- Delegate to Gemini (research/search specialist)@codex <task>- Delegate to Codex (large context specialist)@k,@g,@c- Shorthand aliases
Execution Steps
When you see @cli syntax in a user message:
-
Parse the request: Extract CLI name and task
@kimi design a modal→ cli=kimi, task="design a modal"@k build a navbar→ cli=kimi, task="build a navbar"
-
Check CLI availability: Run the registry check
${CLAUDE_PLUGIN_ROOT}/lib/registry.sh check <cli> -
If available: Execute the delegation
${CLAUDE_PLUGIN_ROOT}/lib/process-manager.sh run <cli> "<task>" "$(pwd)" -
Stream output: Show the CLI's response with attribution
-
Summarize: After completion, briefly summarize what the specialist did
CLI Specialties
| CLI | Strengths | Color |
|---|---|---|
| kimi | Frontend, design, UI/UX, CSS, animations, React, Vue, Tailwind | Magenta |
| gemini | Research, search, documentation, explanations, comparisons | Blue |
| codex | Large context analysis, codebase-wide refactoring, legacy code | Green |
Example Interaction
User: @kimi design a modern dashboard with charts
Response:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
kimi Starting...
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[kimi] Creating Dashboard.tsx...
[kimi] Adding chart components...
[kimi] Styling with Tailwind...
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
kimi ✓ Complete · 12s
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Summary: Kimi created a Dashboard component with LineChart and BarChart using Recharts, styled with Tailwind CSS dark theme.
Error Handling
If the CLI is not found:
[kimi:error] CLI not found. Is it installed?
To install Kimi CLI:
uv tool install kimi-cli
Or use a different specialist:
@gemini for research tasks
@codex for large codebase analysis
Notes
- Always use the process manager for execution to get proper streaming and attribution
- The working directory is passed to the CLI so it can access project files
- Timeout is CLI-specific (configured in registry.yaml)
Commands 1
Multi-Model Orchestrator Status
Your Task
Display the status of the Multi-Model CLI Orchestrator.
Step 1: Check CLI Registry
Run this command to get CLI availability:
${CLAUDE_PLUGIN_ROOT}/lib/registry.sh check_all
Step 2: Display the Status
Format the output nicely for the user, including:
-
CLI Registry Status
- Show which CLIs are available and their paths
- Use ✓ for available, ✗ for not found
-
Routing Thresholds
- Auto-delegate: ≥80% confidence
- Suggest: ≥50% confidence
-
Delegation Commands
@kimi <task>- Frontend, design, UI components@gemini <task>- Research, search, documentation@codex <task>- Large context, codebase analysis
Example Output
# Multi-Model Orchestrator Status
## CLI Registry
| CLI | Status | Path |
|-----|--------|------|
| kimi | ✓ Available | /home/user/.local/bin/kimi |
| gemini | ✓ Available | /usr/bin/gemini |
| codex | ✗ Not found | - |
## Routing Configuration
### Confidence Thresholds
- **Auto-delegate**: ≥80% confidence → Task automatically routed to specialist
- **Suggest**: ≥50% confidence → User prompted to confirm delegation
### Delegation Commands
| Command | Specialist | Best For |
|---------|------------|----------|
| `@kimi <task>` | Kimi | Frontend, design, UI components |
| `@gemini <task>` | Gemini | Research, search, documentation |
| `@codex <task>` | Codex | Large context, codebase analysis |
Hooks 2
Sponsors
Details
- Marketplace
- syedadeel2/multi-model-cli-orchestrator
- Author
- syedadeel2
- Category
- Development