What problem does it solve? Higress covers two distinct workflows — managing operator CRDs like WasmPlugin and McpBridge, and deploying Higress via Helm — and this Skill routes each request to the correct sub-skill so the right instructions load. ## Core Features & Use Cases - Task Routing: Maps user requests to either the higress-operator or higress-helm sub-skill based on intent. - CRD and AI Gateway Coverage: Directs WasmPlugin, Http2Rpc, McpBridge, AI Gateway, and service discovery tasks to the operator sub-skill. - Deployment Coverage: Directs Helm install, upgrade, Gateway API, Redis caching, and monitoring tasks to the helm sub-skill. - Use Case: A user asks to configure an AI Gateway with an OpenAI provider; the router sends them to higress-operator, while a Helm-based deployment request goes to higress-helm. ## Quick Start Ask to deploy a WasmPlugin for AI proxying or to install Higress on Kubernetes with Helm, and the router will load the matching sub-skill.