[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QP6B69SN8T2P4C0Q7WMQFW":3,"skill-same:01M6QP6B69SN8T2P4C0Q7WMQFW":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":14,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M6QP6B69SN8T2P4C0Q7WMQFW","intelligent-routing",null,"Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions.","LOrdEnRYQuE\u002FLRDEnE-Ai-Specialist","LOrdEnRYQuE","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F93767164?v=4","01M6QNZGVYDMQTN925B3BDB98Z","LOrdEnRYQuE | Advanced Digital Solutions ","01M6QNZH078JB4S8QJNNQNJPS5",0,"MIT","https:\u002F\u002Fgithub.com\u002FLOrdEnRYQuE\u002FLRDEnE-Ai-Specialist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fintelligent-routing\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32],"routing","intelligent routing","user","selection","task","requests","agent selection","automatic","specialist","2026-11-10 10:12:30",false,"---\nname: intelligent-routing\ndescription: Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions.\nversion: 1.0.0\n---\n\n# Intelligent Agent Routing\n\n**Purpose**: Automatically analyze user requests and route them to the most appropriate specialist agent(s) without requiring explicit user mentions.\n\n## Core Principle\n\n> **The AI should act as an intelligent Project Manager**, analyzing each request and automatically selecting the best specialist(s) for the job.\n\n## How It Works\n\n### 1. Request Analysis\n\nBefore responding to ANY user request, perform automatic analysis:\n\n```mermaid\ngraph TD\n    A[User Request: Add login] --> B[ANALYZE]\n    B --> C[Keywords]\n    B --> D[Domains]\n    B --> E[Complexity]\n    C --> F[SELECT AGENT]\n    D --> F\n    E --> F\n    F --> G[security-auditor + backend-specialist]\n    G --> H[AUTO-INVOKE with context]\n```\n\n### 2. Agent Selection Matrix\n\n**Use this matrix to automatically select agents:**\n\n| User Intent         | Keywords                                   | Selected Agent(s)                           | Auto-invoke? |\n| ------------------- | ------------------------------------------ | ------------------------------------------- | ------------ |\n| **Authentication**  | \"login\", \"auth\", \"signup\", \"password\"      | `security-auditor` + `backend-specialist`   | ✅ YES       |\n| **UI Component**    | \"button\", \"card\", \"layout\", \"style\"        | `frontend-specialist`                       | ✅ YES       |\n| **Mobile UI**       | \"screen\", \"navigation\", \"touch\", \"gesture\" | `mobile-developer`                          | ✅ YES       |\n| **API Endpoint**    | \"endpoint\", \"route\", \"API\", \"POST\", \"GET\"  | `backend-specialist`                        | ✅ YES       |\n| **Database**        | \"schema\", \"migration\", \"query\", \"table\"    | `database-architect` + `backend-specialist` | ✅ YES       |\n| **Bug Fix**         | \"error\", \"bug\", \"not working\", \"broken\"    | `debugger`                                  | ✅ YES       |\n| **Test**            | \"test\", \"coverage\", \"unit\", \"e2e\"          | `test-engineer`                             | ✅ YES       |\n| **Deployment**      | \"deploy\", \"production\", \"CI\u002FCD\", \"docker\"  | `devops-engineer`                           | ✅ YES       |\n| **Security Review** | \"security\", \"vulnerability\", \"exploit\"     | `security-auditor` + `penetration-tester`   | ✅ YES       |\n| **Performance**     | \"slow\", \"optimize\", \"performance\", \"speed\" | `performance-optimizer`                     | ✅ YES       |\n| **Product Def**     | \"requirements\", \"user story\", \"backlog\", \"MVP\" | `product-owner`                             | ✅ YES       |\n| **New Feature**     | \"build\", \"create\", \"implement\", \"new app\"  | `orchestrator` → multi-agent                | ⚠️ ASK FIRST |\n| **Complex Task**    | Multiple domains detected                  | `orchestrator` → multi-agent                | ⚠️ ASK FIRST |\n\n### 3. Automatic Routing Protocol\n\n## TIER 0 - Automatic Analysis (ALWAYS ACTIVE)\n\nBefore responding to ANY request:\n\n```javascript\n\u002F\u002F Pseudo-code for decision tree\nfunction analyzeRequest(userMessage) {\n    \u002F\u002F 1. Classify request type\n    const requestType = classifyRequest(userMessage);\n\n    \u002F\u002F 2. Detect domains\n    const domains = detectDomains(userMessage);\n\n    \u002F\u002F 3. Determine complexity\n    const complexity = assessComplexity(domains);\n\n    \u002F\u002F 4. Select agent(s)\n    if (complexity === \"SIMPLE\" && domains.length === 1) {\n        return selectSingleAgent(domains[0]);\n    } else if (complexity === \"MODERATE\" && domains.length \u003C= 2) {\n        return selectMultipleAgents(domains);\n    } else {\n        return \"orchestrator\"; \u002F\u002F Complex task\n    }\n}\n```\n\n## 4. Response Format\n\n**When auto-selecting an agent, inform the user concisely:**\n\n```markdown\n? **Applying knowledge of `@security-auditor` + `@backend-specialist`...**\n\n[Proceed with specialized response]\n```\n\n**Benefits:**\n\n- ✅ User sees which expertise is being applied\n- ✅ Transparent decision-making\n- ✅ Still automatic (no \u002Fcommands needed)\n\n## Domain Detection Rules\n\n### Single-Domain Tasks (Auto-invoke Single Agent)\n\n| Domain          | Patterns                                   | Agent                   |\n| --------------- | ------------------------------------------ | ----------------------- |\n| **Security**    | auth, login, jwt, password, hash, token    | `security-auditor`      |\n| **Frontend**    | component, react, vue, css, html, tailwind | `frontend-specialist`   |\n| **Backend**     | api, server, express, fastapi, node        | `backend-specialist`    |\n| **Mobile**      | react native, flutter, ios, android, expo  | `mobile-developer`      |\n| **Database**    | prisma, sql, mongodb, schema, migration    | `database-architect`    |\n| **Testing**     | test, jest, vitest, playwright, cypress    | `test-engineer`         |\n| **DevOps**      | docker, kubernetes, ci\u002Fcd, pm2, nginx      | `devops-engineer`       |\n| **Debug**       | error, bug, crash, not working, issue      | `debugger`              |\n| **Performance** | slow, lag, optimize, cache, performance    | `performance-optimizer` |\n| **SEO**         | seo, meta, analytics, sitemap, robots      | `seo-specialist`        |\n| **Game**        | unity, godot, phaser, game, multiplayer    | `game-developer`        |\n\n### Multi-Domain Tasks (Auto-invoke Orchestrator)\n\nIf request matches **2+ domains from different categories**, automatically use `orchestrator`:\n\n```text\nExample: \"Create a secure login system with dark mode UI\"\n→ Detected: Security + Frontend\n→ Auto-invoke: orchestrator\n→ Orchestrator will handle: security-auditor, frontend-specialist, test-engineer\n```\n\n## Complexity Assessment\n\n### SIMPLE (Direct agent invocation)\n\n- Single file edit\n- Clear, specific task\n- One domain only\n- Example: \"Fix the login button style\"\n\n**Action**: Auto-invoke respective agent\n\n### MODERATE (2-3 agents)\n\n- 2-3 files affected\n- Clear requirements\n- 2 domains max\n- Example: \"Add API endpoint for user profile\"\n\n**Action**: Auto-invoke relevant agents sequentially\n\n### COMPLEX (Orchestrator required)\n\n- Multiple files\u002Fdomains\n- Architectural decisions needed\n- Unclear requirements\n- Example: \"Build a social media app\"\n\n**Action**: Auto-invoke `orchestrator` → will ask Socratic questions\n\n## Implementation Rules\n\n### Rule 1: Silent Analysis\n\n#### DO NOT announce \"I'm analyzing your request...\"\n\n- ✅ Analyze silently\n- ✅ Inform which agent is being applied\n- ❌ Avoid verbose meta-commentary\n\n### Rule 2: Inform Agent Selection\n\n**DO inform which expertise is being applied:**\n\n```markdown\n? **Applying knowledge of `@frontend-specialist`...**\n\nI will create the component with the following characteristics:\n[Continue with specialized response]\n```\n\n### Rule 3: Seamless Experience\n\n**The user should not notice a difference from talking to the right specialist directly.**\n\n### Rule 4: Override Capability\n\n**User can still explicitly mention agents:**\n\n```text\nUser: \"Use @backend-specialist to review this\"\n→ Override auto-selection\n→ Use explicitly mentioned agent\n```\n\n## Edge Cases\n\n### Case 1: Generic Question\n\n```text\nUser: \"How does React work?\"\n→ Type: QUESTION\n→ No agent needed\n→ Respond directly with explanation\n```\n\n### Case 2: Extremely Vague Request\n\n```text\nUser: \"Make it better\"\n→ Complexity: UNCLEAR\n→ Action: Ask clarifying questions first\n→ Then route to appropriate agent\n```\n\n### Case 3: Contradictory Patterns\n\n```text\nUser: \"Add mobile support to the web app\"\n→ Conflict: mobile vs web\n→ Action: Ask: \"Do you want responsive web or native mobile app?\"\n→ Then route accordingly\n```\n\n## Integration with Existing Workflows\n\n### With \u002Forchestrate Command\n\n- **User types `\u002Forchestrate`**: Explicit orchestration mode\n- **AI detects complex task**: Auto-invoke orchestrator (same result)\n\n**Difference**: User doesn't need to know the command exists.\n\n### With Socratic Gate\n\n- **Auto-routing does NOT bypass Socratic Gate**\n- If task is unclear, still ask questions first\n- Then route to appropriate agent\n\n### With GEMINI.md Rules\n\n- **Priority**: GEMINI.md rules > intelligent-routing\n- If GEMINI.md specifies explicit routing, follow it\n- Intelligent routing is the DEFAULT when no explicit rule exists\n\n## Testing the System\n\n### Test Cases\n\n#### Test 1: Simple Frontend Task\n\n```text\nUser: \"Create a dark mode toggle button\"\nExpected: Auto-invoke frontend-specialist\nVerify: Response shows \"Using @frontend-specialist\"\n```\n\n#### Test 2: Security Task\n\n```text\nUser: \"Review the authentication flow for vulnerabilities\"\nExpected: Auto-invoke security-auditor\nVerify: Security-focused analysis\n```\n\n#### Test 3: Complex Multi-Domain\n\n```text\nUser: \"Build a chat application with real-time notifications\"\nExpected: Auto-invoke orchestrator\nVerify: Multiple agents coordinated (backend, frontend, test)\n```\n\n#### Test 4: Bug Fix\n\n```text\nUser: \"Login is not working, getting 401 error\"\nExpected: Auto-invoke debugger\nVerify: Systematic debugging approach\n```\n\n## Performance Considerations\n\n### Token Usage\n\n- Analysis adds ~50-100 tokens per request\n- Tradeoff: Better accuracy vs slight overhead\n- Overall SAVES tokens by reducing back-and-forth\n\n### Response Time\n\n- Analysis is instant (pattern matching)\n- No additional API calls required\n- Agent selection happens before first response\n\n## User Education\n\n### Optional: First-Time Explanation\n\nIf this is the first interaction in a project:\n\n```markdown\n? **Tip**: I am configured with automatic specialist agent selection.\nI will always choose the most suitable specialist for your task. You can\nstill mention agents explicitly with `@agent-name` if you prefer.\n```\n\n## Debugging Agent Selection\n\n### Enable Debug Mode (for development)\n\nAdd to GEMINI.md temporarily:\n\n```markdown\n## DEBUG: Intelligent Routing\n\nShow selection reasoning:\n\n- Detected domains: [list]\n- Selected agent: [name]\n- Reasoning: [why]\n```\n\n## Summary\n\n**intelligent-routing skill enables:**\n\n✅ Zero-command operation (no need for `\u002Forchestrate`)  \n✅ Automatic specialist selection based on request analysis  \n✅ Transparent communication of which expertise is being applied  \n✅ Seamless integration with existing workflows  \n✅ Override capability for explicit agent mentions  \n✅ Fallback to orchestrator for complex tasks\n\n**Result**: User gets specialist-level responses without needing to know the system architecture.\n\n---\n\n**Next Steps**: Integrate this skill into GEMINI.md TIER 0 rules.\n","# Intelligent Agent Routing\n\n**Purpose**: Automatically analyze user requests and route them to the most appropriate specialist agent(s) without requiring explicit user mentions.\n\n## Core Principle\n\n> **The AI should act as an intelligent Project Manager**, analyzing each request and automatically selecting the best specialist(s) for the job.\n\n## How It Works\n\n### 1. Request Analysis\n\nBefore responding to ANY user request, perform automatic analysis:\n\n```mermaid\ngraph TD\n    A[User Request: Add login] --> B[ANALYZE]\n    B --> C[Keywords]\n    B --> D[Domains]\n    B --> E[Complexity]\n    C --> F[SELECT AGENT]\n    D --> F\n    E --> F\n    F --> G[security-auditor + backend-specialist]\n    G --> H[AUTO-INVOKE with context]\n```\n\n### 2. Agent Selection Matrix\n\n**Use this matrix to automatically select agents:**\n\n| User Intent         | Keywords                                   | Selected Agent(s)                           | Auto-invoke? |\n| ------------------- | ------------------------------------------ | ------------------------------------------- | ------------ |\n| **Authentication**  | \"login\", \"auth\", \"signup\", \"password\"      | `security-auditor` + `backend-specialist`   | ✅ YES       |\n| **UI Component**    | \"button\", \"card\", \"layout\", \"style\"        | `frontend-specialist`                       | ✅ YES       |\n| **Mobile UI**       | \"screen\", \"navigation\", \"touch\", \"gesture\" | `mobile-developer`                          | ✅ YES       |\n| **API Endpoint**    | \"endpoint\", \"route\", \"API\", \"POST\", \"GET\"  | `backend-specialist`                        | ✅ YES       |\n| **Database**        | \"schema\", \"migration\", \"query\", \"table\"    | `database-architect` + `backend-specialist` | ✅ YES       |\n| **Bug Fix**         | \"error\", \"bug\", \"not working\", \"broken\"    | `debugger`                                  | ✅ YES       |\n| **Test**            | \"test\", \"coverage\", \"unit\", \"e2e\"          | `test-engineer`                             | ✅ YES       |\n| **Deployment**      | \"deploy\", \"production\", \"CI\u002FCD\", \"docker\"  | `devops-engineer`                           | ✅ YES       |\n| **Security Review** | \"security\", \"vulnerability\", \"exploit\"     | `security-auditor` + `penetration-tester`   | ✅ YES       |\n| **Performance**     | \"slow\", \"optimize\", \"performance\", \"speed\" | `performance-optimizer`                     | ✅ YES       |\n| **Product Def**     | \"requirements\", \"user story\", \"backlog\", \"MVP\" | `product-owner`                             | ✅ YES       |\n| **New Feature**     | \"build\", \"create\", \"implement\", \"new app\"  | `orchestrator` → multi-agent                | ⚠️ ASK FIRST |\n| **Complex Task**    | Multiple domains detected                  | `orchestrator` → multi-agent                | ⚠️ ASK FIRST |\n\n### 3. Automatic Routing Protocol\n\n## TIER 0 - Automatic Analysis (ALWAYS ACTIVE)\n\nBefore responding to ANY request:\n\n```javascript\n\u002F\u002F Pseudo-code for decision tree\nfunction analyzeRequest(userMessage) {\n    \u002F\u002F 1. Classify request type\n    const requestType = classifyRequest(userMessage);\n\n    \u002F\u002F 2. Detect domains\n    const domains = detectDomains(userMessage);\n\n    \u002F\u002F 3. Determine complexity\n    const complexity = assessComplexity(domains);\n\n    \u002F\u002F 4. Select agent(s)\n    if (complexity === \"SIMPLE\" && domains.length === 1) {\n        return selectSingleAgent(domains[0]);\n    } else if (complexity === \"MODERATE\" && domains.length \u003C= 2) {\n        return selectMultipleAgents(domains);\n    } else {\n        return \"orchestrator\"; \u002F\u002F Complex task\n    }\n}\n```\n\n## 4. Response Format\n\n**When auto-selecting an agent, inform the user concisely:**\n\n```markdown\n? **Applying knowledge of `@security-auditor` + `@backend-specialist`...**\n\n[Proceed with specialized response]\n```\n\n**Benefits:**\n\n- ✅ User sees which expertise is being applied\n- ✅ Transparent decision-making\n- ✅ Still automatic (no \u002Fcommands needed)\n\n## Domain Detection Rules\n\n### Single-Domain Tasks (Auto-invoke Single Agent)\n\n| Domain          | Patterns                                   | Agent                   |\n| --------------- | ------------------------------------------ | ----------------------- |\n| **Security**    | auth, login, jwt, password, hash, token    | `security-auditor`      |\n| **Frontend**    | component, react, vue, css, html, tailwind | `frontend-specialist`   |\n| **Backend**     | api, server, express, fastapi, node        | `backend-specialist`    |\n| **Mobile**      | react native, flutter, ios, android, expo  | `mobile-developer`      |\n| **Database**    | prisma, sql, mongodb, schema, migration    | `database-architect`    |\n| **Testing**     | test, jest, vitest, playwright, cypress    | `test-engineer`         |\n| **DevOps**      | docker, kubernetes, ci\u002Fcd, pm2, nginx      | `devops-engineer`       |\n| **Debug**       | error, bug, crash, not working, issue      | `debugger`              |\n| **Performance** | slow, lag, optimize, cache, performance    | `performance-optimizer` |\n| **SEO**         | seo, meta, analytics, sitemap, robots      | `seo-specialist`        |\n| **Game**        | unity, godot, phaser, game, multiplayer    | `game-developer`        |\n\n### Multi-Domain Tasks (Auto-invoke Orchestrator)\n\nIf request matches **2+ domains from different categories**, automatically use `orchestrator`:\n\n```text\nExample: \"Create a secure login system with dark mode UI\"\n→ Detected: Security + Frontend\n→ Auto-invoke: orchestrator\n→ Orchestrator will handle: security-auditor, frontend-specialist, test-engineer\n```\n\n## Complexity Assessment\n\n### SIMPLE (Direct agent invocation)\n\n- Single file edit\n- Clear, specific task\n- One domain only\n- Example: \"Fix the login button style\"\n\n**Action**: Auto-invoke respective agent\n\n### MODERATE (2-3 agents)\n\n- 2-3 files affected\n- Clear requirements\n- 2 domains max\n- Example: \"Add API endpoint for user profile\"\n\n**Action**: Auto-invoke relevant agents sequentially\n\n### COMPLEX (Orchestrator required)\n\n- Multiple files\u002Fdomains\n- Architectural decisions needed\n- Unclear requirements\n- Example: \"Build a social media app\"\n\n**Action**: Auto-invoke `orchestrator` → will ask Socratic questions\n\n## Implementation Rules\n\n### Rule 1: Silent Analysis\n\n#### DO NOT announce \"I'm analyzing your request...\"\n\n- ✅ Analyze silently\n- ✅ Inform which agent is being applied\n- ❌ Avoid verbose meta-commentary\n\n### Rule 2: Inform Agent Selection\n\n**DO inform which expertise is being applied:**\n\n```markdown\n? **Applying knowledge of `@frontend-specialist`...**\n\nI will create the component with the following characteristics:\n[Continue with specialized response]\n```\n\n### Rule 3: Seamless Experience\n\n**The user should not notice a difference from talking to the right specialist directly.**\n\n### Rule 4: Override Capability\n\n**User can still explicitly mention agents:**\n\n```text\nUser: \"Use @backend-specialist to review this\"\n→ Override auto-selection\n→ Use explicitly mentioned agent\n```\n\n## Edge Cases\n\n### Case 1: Generic Question\n\n```text\nUser: \"How does React work?\"\n→ Type: QUESTION\n→ No agent needed\n→ Respond directly with explanation\n```\n\n### Case 2: Extremely Vague Request\n\n```text\nUser: \"Make it better\"\n→ Complexity: UNCLEAR\n→ Action: Ask clarifying questions first\n→ Then route to appropriate agent\n```\n\n### Case 3: Contradictory Patterns\n\n```text\nUser: \"Add mobile support to the web app\"\n→ Conflict: mobile vs web\n→ Action: Ask: \"Do you want responsive web or native mobile app?\"\n→ Then route accordingly\n```\n\n## Integration with Existing Workflows\n\n### With \u002Forchestrate Command\n\n- **User types `\u002Forchestrate`**: Explicit orchestration mode\n- **AI detects complex task**: Auto-invoke orchestrator (same result)\n\n**Difference**: User doesn't need to know the command exists.\n\n### With Socratic Gate\n\n- **Auto-routing does NOT bypass Socratic Gate**\n- If task is unclear, still ask questions first\n- Then route to appropriate agent\n\n### With GEMINI.md Rules\n\n- **Priority**: GEMINI.md rules > intelligent-routing\n- If GEMINI.md specifies explicit routing, follow it\n- Intelligent routing is the DEFAULT when no explicit rule exists\n\n## Testing the System\n\n### Test Cases\n\n#### Test 1: Simple Frontend Task\n\n```text\nUser: \"Create a dark mode toggle button\"\nExpected: Auto-invoke frontend-specialist\nVerify: Response shows \"Using @frontend-specialist\"\n```\n\n#### Test 2: Security Task\n\n```text\nUser: \"Review the authentication flow for vulnerabilities\"\nExpected: Auto-invoke security-auditor\nVerify: Security-focused analysis\n```\n\n#### Test 3: Complex Multi-Domain\n\n```text\nUser: \"Build a chat application with real-time notifications\"\nExpected: Auto-invoke orchestrator\nVerify: Multiple agents coordinated (backend, frontend, test)\n```\n\n#### Test 4: Bug Fix\n\n```text\nUser: \"Login is not working, getting 401 error\"\nExpected: Auto-invoke debugger\nVerify: Systematic debugging approach\n```\n\n## Performance Considerations\n\n### Token Usage\n\n- Analysis adds ~50-100 tokens per request\n- Tradeoff: Better accuracy vs slight overhead\n- Overall SAVES tokens by reducing back-and-forth\n\n### Response Time\n\n- Analysis is instant (pattern matching)\n- No additional API calls required\n- Agent selection happens before first response\n\n## User Education\n\n### Optional: First-Time Explanation\n\nIf this is the first interaction in a project:\n\n```markdown\n? **Tip**: I am configured with automatic specialist agent selection.\nI will always choose the most suitable specialist for your task. You can\nstill mention agents explicitly with `@agent-name` if you prefer.\n```\n\n## Debugging Agent Selection\n\n### Enable Debug Mode (for development)\n\nAdd to GEMINI.md temporarily:\n\n```markdown\n## DEBUG: Intelligent Routing\n\nShow selection reasoning:\n\n- Detected domains: [list]\n- Selected agent: [name]\n- Reasoning: [why]\n```\n\n## Summary\n\n**intelligent-routing skill enables:**\n\n✅ Zero-command operation (no need for `\u002Forchestrate`)  \n✅ Automatic specialist selection based on request analysis  \n✅ Transparent communication of which expertise is being applied  \n✅ Seamless integration with existing workflows  \n✅ Override capability for explicit agent mentions  \n✅ Fallback to orchestrator for complex tasks\n\n**Result**: User gets specialist-level responses without needing to know the system architecture.\n\n---\n\n**Next Steps**: Integrate this skill into GEMINI.md TIER 0 rules.\n",{"name":5,"version":38,"description":7},"1.0.0","main","b04f8c98dcf3dfacf4e2aff1eae92616ed12d83d",".agent\u002Fskills\u002Fintelligent-routing","https:\u002F\u002Fgithub.com\u002FLOrdEnRYQuE\u002FLRDEnE-Ai-Specialist","https:\u002F\u002Fgithub.com\u002FLOrdEnRYQuE","2026-04-10 19:41:10",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add LOrdEnRYQuE\u002FLRDEnE-Ai-Specialist --skill intelligent-routing",{"tool":51,"command":52},"bunx","bunx skills add LOrdEnRYQuE\u002FLRDEnE-Ai-Specialist --skill intelligent-routing",{"tool":54,"command":55},"pnpm","pnpm dlx skills add LOrdEnRYQuE\u002FLRDEnE-Ai-Specialist --skill intelligent-routing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLOrdEnRYQuE\u002FLRDEnE-Ai-Specialist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fintelligent-routing\u002FSKILL.md",true,[],[60,87,120,148,154,163],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":33},"01M6QPEC0HA7GF9HY9S3YDF256","WebApp Architect","Plan, build, refactor, debug, and prepare web applications end-to-end. Activate for greenfield builds, feature additions, architecture reviews, and deployment prep.","https:\u002F\u002Fgithub.com\u002FLOrdEnRYQuE\u002FLRDEnE-Ai-Specialist\u002Fblob\u002Fmain\u002Fadapters\u002Fwindsurf\u002F.agents\u002Fskills\u002Fwebapp-architect\u002FSKILL.md",[],[67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86],"webapp architect","webapp","architect","web","architecture","prepare","debug","deployment","refactor","applications","plan","repo","build","activate","scan","feature","end","reviews","prep","for",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":101,"publishedAt":33},"01M6QPE68RNE5PWPC2CPK7ZHCZ","SEO Growth Auditor","Perform technical and on-page SEO audits, generate schema markup, and produce prioritized action reports. Activate for site launches, ranking improvements, and metadata fixes.","https:\u002F\u002Fgithub.com\u002FLOrdEnRYQuE\u002FLRDEnE-Ai-Specialist\u002Fblob\u002Fmain\u002Fadapters\u002Fwindsurf\u002F.agents\u002Fskills\u002Fseo-auditor\u002FSKILL.md",[93,96],{"categoryNo":94,"categoryName":95,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[102,103,104,105,86,106,107,108,109,110,111,112,113,114,115,116,117,118,119,80],"seo","seo growth auditor","auditor","growth","fixes","action","reports","ranking","crawl","generate","produce","metadata","audit","schema markup","site","page","technical","schema",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":129,"publishedAt":33},"01M6QPDSN4KMHFS4CTEMN3520Q","GDPR Compliance Copilot","Identify GDPR compliance gaps, map data flows, generate DSAR templates, and prepare privacy policy inputs. Always requires human legal review.","https:\u002F\u002Fgithub.com\u002FLOrdEnRYQuE\u002FLRDEnE-Ai-Specialist\u002Fblob\u002Fmain\u002Fadapters\u002Fwindsurf\u002F.agents\u002Fskills\u002Fgdpr-copilot\u002FSKILL.md",[126],{"categoryNo":127,"categoryName":128,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000037","律师与法务",[122,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,111],"gdpr compliance","gdpr","compliance","copilot","legal review","report","policy","privacy","flow","templates","dsar","map","human","gap","review","flows","privacy policy","gaps",{"skillNo":149,"name":150,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":33},"01M6QPDR5FMXB4X0960JKCMK80","webapp-architect","https:\u002F\u002Fgithub.com\u002FLOrdEnRYQuE\u002FLRDEnE-Ai-Specialist\u002Fblob\u002Fmain\u002Fadapters\u002Fcursor\u002Fskills\u002Fwebapp-architect\u002FSKILL.md",[],[67,68,69],{"skillNo":155,"name":156,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":161,"publishedAt":33},"01M6QPDM6FZDXXQS2KRJT1YD8P","seo-auditor","https:\u002F\u002Fgithub.com\u002FLOrdEnRYQuE\u002FLRDEnE-Ai-Specialist\u002Fblob\u002Fmain\u002Fadapters\u002Fcursor\u002Fskills\u002Fseo-auditor\u002FSKILL.md",[159,160],{"categoryNo":94,"categoryName":95,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},[102,162,104],"seo auditor",{"skillNo":164,"name":165,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":33},"01M6QPDGEH5RE1VEY57YZ1GA1Q","gdpr-copilot","https:\u002F\u002Fgithub.com\u002FLOrdEnRYQuE\u002FLRDEnE-Ai-Specialist\u002Fblob\u002Fmain\u002Fadapters\u002Fcursor\u002Fskills\u002Fgdpr-copilot\u002FSKILL.md",[],[133,131,169],"gdpr copilot"]