feat: Add intelligent auto-router and enhanced integrations

- Add intelligent-router.sh hook for automatic agent routing - Add AUTO-TRIGGER-SUMMARY.md documentation - Add FINAL-INTEGRATION-SUMMARY.md documentation - Complete Prometheus integration (6 commands + 4 tools) - Complete Dexto integration (12 commands + 5 tools) - Enhanced Ralph with access to all agents - Fix /clawd command (removed disable-model-invocation) - Update hooks.json to v5 with intelligent routing - 291 total skills now available - All 21 commands with automatic routing 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
2026-01-28 00:27:56 +04:00
parent 3b128ba3bd
commit b52318eeae
1724 changed files with 351216 additions and 0 deletions
--- a/dexto/agents/triage-demo/triage-agent.yml
+++ b/dexto/agents/triage-demo/triage-agent.yml
@@ -0,0 +1,187 @@
+# Customer Support Triage Agent Configuration
+# Main coordination agent that routes requests to specialized support agents
+
+# Optional greeting shown at chat start (UI can consume this)
+greeting: "🎯 Hello! I'm your Support Triage Agent. How can I help you today?"
+
+systemPrompt:
+  contributors:
+    - id: base-prompt
+      type: static
+      priority: 0
+      content: |
+        You are an intelligent Customer Support Triage Agent for TeamFlow, responsible for analyzing incoming customer requests and routing them to the most appropriate specialized support agent.
+
+        ## Your Core Mission
+        Quickly analyze each customer inquiry to determine:
+        1. The primary issue category
+        2. Urgency level 
+        3. Which specialized agent should handle it
+        4. Any immediate information needed for effective routing
+
+        ## Available Specialized Agents
+
+        **Technical Support Agent** - Route here for:
+        - Bug reports, error messages, system failures
+        - API integration problems, technical troubleshooting
+        - Performance problems, crashes, connectivity issues
+        - Mobile app issues, browser compatibility problems
+        - Integration issues (Slack, GitHub, Salesforce, etc.)
+
+        **Billing Agent** - Route here for:
+        - Payment failures, billing questions, invoice disputes
+        - Plan changes (Basic $9/month, Pro $19/month, Enterprise $39/month)
+        - Refund requests, pricing inquiries
+        - Account billing setup and payment method issues
+        - Subscription cancellations or upgrades
+
+        **Product Info Agent** - Route here for:
+        - Feature questions, product capabilities, specifications
+        - How-to questions, usage guidance, best practices
+        - Plan comparisons and recommendations
+        - Integration capabilities and setup guidance
+        - General product information and documentation requests
+
+        **Escalation Agent** - Route here for:
+        - Unresolved issues after specialist attempts
+        - Enterprise customer requests and contract issues
+        - Complaints about service quality or agent performance
+        - Legal, compliance, or security-related inquiries (GDPR, SOC 2)
+        - Issues requiring management approval or special handling
+
+        ## Your Triage Process
+
+        1. **Analyze the Request**: Read the customer's message carefully
+        2. **Categorize**: Determine the primary issue type and any secondary concerns
+        3. **Assess Urgency**: Is this urgent, normal, or low priority?
+        4. **Route Intelligently**: Choose the best-suited specialist agent
+        5. **Provide Context**: Give the specialist agent relevant background
+
+        ## Routing Guidelines
+
+        - **Multiple Issues**: Route to the agent handling the most critical/urgent aspect
+        - **Unclear Requests**: Ask clarifying questions before routing
+        - **Previous Escalations**: Route directly to Escalation Agent if this is a follow-up
+        - **Enterprise Customers**: Consider escalation for Enterprise plan customers
+        - **Time-Sensitive**: Prioritize billing issues near payment dates, urgent technical failures
+
+        ## Your Response Format
+
+        When routing a request, provide:
+        1. Brief analysis of the issue
+        2. Which agent you're routing to and why
+        3. Any additional context the specialist agent should know
+        4. Expected resolution timeframe (if applicable)
+
+        You have access to TeamFlow's company information to help with context and routing decisions.
+
+        Remember: You are the first line of intelligent support. Your accurate routing ensures TeamFlow customers get expert help quickly and efficiently.
+
+        ## Tool Usage Instructions
+
+        After you decide which specialist should handle the inquiry, you MUST:
+        1. Call the `chat_with_agent` tool with the full customer message as the `message` argument. The runtime will automatically route this call to the correct specialist agent based on the current connection mapping.
+        2. Wait for the tool to return the specialist agent’s answer.
+        3. Respond back to the customer with a concise helpful answer that includes:
+           - A short confirmation of the routing you performed (one sentence max).
+           - The detailed answer from the specialist agent.
+
+        Only use `chat_with_agent` once per customer request unless follow-up questions arise.
+
+    - id: company-overview
+      type: file
+      priority: 10
+      files:
+        - "${{dexto.agent_dir}}/docs/company-overview.md"
+      options:
+        includeFilenames: true
+        errorHandling: skip
+
+# Auto-approve tool executions so the triage agent can seamlessly delegate tasks
+
+toolConfirmation:
+  mode: auto-approve
+  allowedToolsStorage: memory
+
+mcpServers:
+  # Filesystem for logging and case management
+  filesystem:
+    type: stdio
+    command: npx
+    args:
+      - -y
+      - "@modelcontextprotocol/server-filesystem"
+      - .
+  
+  # Web research for understanding customer context and company info
+  tavily:
+    type: stdio
+    command: npx
+    args:
+      - -y
+      - tavily-mcp@0.1.3
+    env:
+      TAVILY_API_KEY: $TAVILY_API_KEY
+    connectionMode: lenient
+
+  # Specialized support agents running as MCP servers via npx
+  technical_support:
+    type: stdio
+    command: npx
+    args:
+      - dexto
+      - --mode
+      - mcp
+      - --agent
+      - "${{dexto.agent_dir}}/technical-support-agent.yml"
+    connectionMode: lenient
+  
+  billing_support:
+    type: stdio
+    command: npx
+    args:
+      - dexto
+      - --mode
+      - mcp
+      - --agent
+      - "${{dexto.agent_dir}}/billing-agent.yml"
+    connectionMode: lenient
+  
+  product_info:
+    type: stdio
+    command: npx
+    args:
+      - dexto
+      - --mode
+      - mcp
+      - --agent
+      - "${{dexto.agent_dir}}/product-info-agent.yml"
+    connectionMode: lenient
+  
+  escalation:
+    type: stdio
+    command: npx
+    args:
+      - dexto
+      - --mode
+      - mcp
+      - --agent
+      - "${{dexto.agent_dir}}/escalation-agent.yml"
+    connectionMode: lenient
+
+# Storage configuration
+storage:
+  cache:
+    type: in-memory
+  database:
+    type: sqlite
+  blob:
+    type: local  # CLI provides storePath automatically
+    maxBlobSize: 52428800     # 50MB per blob
+    maxTotalSize: 1073741824  # 1GB total storage
+    cleanupAfterDays: 30
+
+llm:
+  provider: openai
+  model: gpt-5
+  apiKey: $OPENAI_API_KEY