intelligent-routing

Analyzes user requests and routes them to specialist agents automatically.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/juanjo-zurich/juarvis-v4 --skill intelligent-routing-juanjo-zurich
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: intelligent-routing
Source: https://github.com/juanjo-zurich/juarvis-v4/tree/main/plugins/core/skills/intelligent-routing
Command: npx skills add https://github.com/juanjo-zurich/juarvis-v4 --skill intelligent-routing-juanjo-zurich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Users must know which specialist agent to invoke for each task, forcing them to learn command syntax and agent names before getting expert-level responses. This Skill removes that burden by analyzing each request and selecting the right agent automatically. ## Core Features & Use Cases - Automatic Agent Selection: Matches keywords and domains in user requests against a selection matrix covering security, frontend, backend, mobile, database, testing, DevOps, and more. - Complexity-Based Routing: Classifies tasks as SIMPLE, MODERATE, or COMPLEX, invoking a single agent, multiple agents, or the orchestrator accordingly. - Transparent Notification: Informs the user which specialist expertise is being applied without verbose meta-commentary. - Use Case: A user types "Add login with JWT" and the system automatically applies security-auditor and backend-specialist knowledge without any explicit command. ## Quick Start Ask the AI to review your authentication flow for vulnerabilities and it will automatically apply the security-auditor specialist.

Frequently Asked Questions about intelligent-routing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does automatic agent routing select the right specialist?▼

Automatic agent routing analyzes keywords, domains, and complexity in each user request, then matches them against a selection matrix. Single-domain tasks invoke one specialist, while multi-domain or complex tasks route to an orchestrator agent.

How do I override automatic agent selection?▼

Explicitly mention an agent with the @ syntax, such as @backend-specialist, in your request. Explicit mentions take priority over the automatic selection logic.

What happens when a request matches multiple domains?▼

Requests matching two or more domains from different categories are routed to the orchestrator agent. The orchestrator then coordinates the relevant specialists, such as security-auditor and frontend-specialist, sequentially.

Does intelligent routing work with vague or unclear requests?▼

Vague requests trigger clarifying questions before any agent is invoked. The routing does not bypass the Socratic Gate, so ambiguous tasks like "make it better" are clarified first, then routed.

What are the limitations of keyword-based agent routing?▼

Keyword matching can misclassify requests with contradictory patterns, such as mixing mobile and web terms. In those cases the system asks a disambiguating question rather than guessing, and explicit project rules take priority over default routing.