Menu
Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | intelligent-routing |
| description | Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions. |
| version | 1.0.0 |
Purpose: Automatically analyze user requests and route them to the most appropriate specialist agent(s) without requiring explicit user mentions.
The AI should act as an intelligent Project Manager, analyzing each request and automatically selecting the best specialist(s) for the job.
Before responding to ANY user request, perform automatic analysis:
graph TD
A[User Request: Add login] --> B[ANALYZE]
B --> C[Keywords]
B --> D[Domains]
B --> E[Complexity]
C --> F[SELECT AGENT]
D --> F
E --> F
F --> G[security-auditor + backend-specialist]
G --> H[AUTO-INVOKE with context]
Use this matrix to automatically select agents:
| User Intent | Keywords | Selected Agent(s) | Auto-invoke? |
|---|---|---|---|
| Authentication | "login", "auth", "signup", "password" | security-auditor + backend-specialist | ✅ YES |
| UI Component | "button", "card", "layout", "style" | frontend-specialist | ✅ YES |
| Mobile UI | "screen", "navigation", "touch", "gesture" | mobile-developer | ✅ YES |
| API Endpoint | "endpoint", "route", "API", "POST", "GET" | backend-specialist | ✅ YES |
| Database | "schema", "migration", "query", "table" | database-architect + backend-specialist | ✅ YES |
| Bug Fix | "error", "bug", "not working", "broken" | debugger | ✅ YES |
| Test | "test", "coverage", "unit", "e2e" | test-engineer | ✅ YES |
| Deployment | "deploy", "production", "CI/CD", "docker" | devops-engineer | ✅ YES |
| Security Review | "security", "vulnerability", "exploit" | security-auditor + penetration-tester | ✅ YES |
| Performance | "slow", "optimize", "performance", "speed" | performance-optimizer | ✅ YES |
| Product Def | "requirements", "user story", "backlog", "MVP" | product-owner | ✅ YES |
| New Feature | "build", "create", "implement", "new app" | orchestrator → multi-agent | ⚠️ ASK FIRST |
| Complex Task | Multiple domains detected | orchestrator → multi-agent | ⚠️ ASK FIRST |
Before responding to ANY request:
// Pseudo-code for decision tree
function analyzeRequest(userMessage) {
// 1. Classify request type
const requestType = classifyRequest(userMessage);
// 2. Detect domains
const domains = detectDomains(userMessage);
// 3. Determine complexity
const complexity = assessComplexity(domains);
// 4. Select agent(s)
if (complexity === "SIMPLE" && domains.length === 1) {
return selectSingleAgent(domains[0]);
} else if (complexity === "MODERATE" && domains.length <= 2) {
return selectMultipleAgents(domains);
} else {
return "orchestrator"; // Complex task
}
}
When auto-selecting an agent, inform the user concisely:
🤖 **Applying knowledge of `@security-auditor` + `@backend-specialist`...**
[Proceed with specialized response]
Benefits:
| Domain | Patterns | Agent |
|---|---|---|
| Security | auth, login, jwt, password, hash, token | security-auditor |
| Frontend | component, react, vue, css, html, tailwind | frontend-specialist |
| Backend | api, server, express, fastapi, node | backend-specialist |
| Mobile | react native, flutter, ios, android, expo | mobile-developer |
| Database | prisma, sql, mongodb, schema, migration | database-architect |
| Testing | test, jest, vitest, playwright, cypress | test-engineer |
| DevOps | docker, kubernetes, ci/cd, pm2, nginx | devops-engineer |
| Debug | error, bug, crash, not working, issue | debugger |
| Performance | slow, lag, optimize, cache, performance | performance-optimizer |
| SEO | seo, meta, analytics, sitemap, robots | seo-specialist |
| Game | unity, godot, phaser, game, multiplayer | game-developer |
If request matches 2+ domains from different categories, automatically use orchestrator:
Example: "Create a secure login system with dark mode UI"
→ Detected: Security + Frontend
→ Auto-invoke: orchestrator
→ Orchestrator will handle: security-auditor, frontend-specialist, test-engineer
Action: Auto-invoke respective agent
Action: Auto-invoke relevant agents sequentially
Action: Auto-invoke orchestrator → will ask Socratic questions
DO inform which expertise is being applied:
🤖 **Applying knowledge of `@frontend-specialist`...**
I will create the component with the following characteristics:
[Continue with specialized response]
The user should not notice a difference from talking to the right specialist directly.
User can still explicitly mention agents:
User: "Use @backend-specialist to review this"
→ Override auto-selection
→ Use explicitly mentioned agent
User: "How does React work?"
→ Type: QUESTION
→ No agent needed
→ Respond directly with explanation
User: "Make it better"
→ Complexity: UNCLEAR
→ Action: Ask clarifying questions first
→ Then route to appropriate agent
User: "Add mobile support to the web app"
→ Conflict: mobile vs web
→ Action: Ask: "Do you want responsive web or native mobile app?"
→ Then route accordingly
/orchestrate: Explicit orchestration modeDifference: User doesn't need to know the command exists.
User: "Create a dark mode toggle button"
Expected: Auto-invoke frontend-specialist
Verify: Response shows "Using @frontend-specialist"
User: "Review the authentication flow for vulnerabilities"
Expected: Auto-invoke security-auditor
Verify: Security-focused analysis
User: "Build a chat application with real-time notifications"
Expected: Auto-invoke orchestrator
Verify: Multiple agents coordinated (backend, frontend, test)
User: "Login is not working, getting 401 error"
Expected: Auto-invoke debugger
Verify: Systematic debugging approach
If this is the first interaction in a project:
💡 **Tip**: I am configured with automatic specialist agent selection.
I will always choose the most suitable specialist for your task. You can
still mention agents explicitly with `@agent-name` if you prefer.
Add to GEMINI.md temporarily:
## DEBUG: Intelligent Routing
Show selection reasoning:
- Detected domains: [list]
- Selected agent: [name]
- Reasoning: [why]
intelligent-routing skill enables:
✅ Zero-command operation (no need for /orchestrate)
✅ Automatic specialist selection based on request analysis
✅ Transparent communication of which expertise is being applied
✅ Seamless integration with existing workflows
✅ Override capability for explicit agent mentions
✅ Fallback to orchestrator for complex tasks
Result: User gets specialist-level responses without needing to know the system architecture.
Next Steps: Integrate this skill into GEMINI.md TIER 0 rules.
React and Next.js performance optimization from Vercel Engineering. Use when building React components, optimizing performance, eliminating waterfalls, reducing bundle size, reviewing code for performance issues, or implementing server/client-side optimizations.
Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.
Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.
Design thinking and decision-making for web UI. Use when designing components, layouts, color schemes, typography, or creating aesthetic interfaces. Teaches principles, not fixed values.
Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.
Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, validate, types, static analysis.