Help us improve
Share bugs, ideas, or general feedback.
From omni
Manages agent routing rules: create per-chat or per-user routes to providers/agents, test route resolution, update/delete routes, and view metrics via omni CLI.
npx claudepluginhub automagik-dev/omni --plugin omniHow this skill is triggered — by the user, by Claude, or both
Slash command
/omni:omni-routesThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
```bash
Guides connecting AI agents to Omni channels like WhatsApp, Telegram, Discord, Slack using providers, reply filters, routing, and testing via bash CLI.
Implements Python rules engine for OpenRouter model selection using user tier, task type, budget, tools, vision, and latency conditions with priorities and fallbacks.
Model routing configuration templates and strategies for cost optimization, speed optimization, quality optimization, and intelligent fallback chains. Use when building AI applications with OpenRouter, implementing model routing strategies, optimizing API costs, setting up fallback chains, implementing quality-based routing, or when user mentions model routing, cost optimization, fallback strategies, model selection, intelligent routing, or dynamic model switching.
Share bugs, ideas, or general feedback.
omni routes list --instance <id> --json
omni routes list --instance <id> --active --json
omni routes list --instance <id> --scope chat --json
omni routes list --instance <id> --scope user --json
omni routes get <routeId> --instance <id> --json
# Route a specific chat to an agent
omni routes create --instance <id> --scope chat --chat <chatId> --provider <providerId> --agent <agentId> --label "Support bot" --priority 10 --json
# Route all conversations from a person to an agent
omni routes create --instance <id> --scope user --person <personId> --provider <providerId> --agent <agentId> --json
# Create with gate and streaming options
omni routes create --instance <id> --scope chat --chat <chatId> --provider <providerId> --agent <agentId> --gate --gate-model <model> --gate-prompt "Only reply if relevant" --stream --timeout 60 --json
# Create as inactive (not yet active)
omni routes create --instance <id> --scope chat --chat <chatId> --provider <providerId> --agent <agentId> --inactive --json
omni routes update <routeId> --instance <id> --label "New label" --priority 20 --json
omni routes update <routeId> --instance <id> --active --json
omni routes update <routeId> --instance <id> --inactive --json
omni routes update <routeId> --instance <id> --agent <newAgentId> --timeout 120 --json
omni routes update <routeId> --instance <id> --no-gate --no-stream --json
omni routes delete <routeId> --instance <id> --json
# Test which route would be applied for a given chat
omni routes test --instance <id> --chat <chatId> --json
# Test for a specific person
omni routes test --instance <id> --person <personId> --json
# Test for both chat and person
omni routes test --instance <id> --chat <chatId> --person <personId> --json
omni routes metrics --json
--priority value wins when multiple routes could match.--gate enables an LLM-based filter that decides whether the agent should reply.--reply-filter-mode accepts all or filtered.--agent-type accepts agent, team, or workflow (default: agent).