Knowledge Router

Documentation lookups are routed by classifying a technical query to decide whether to use curated skills, Context7, or a hybrid approach. This classification determines the optimal knowledge retrieval strategy to deliver accurate framework and API answers.

A hybrid approach for API lookups is used when a technical query requires both pattern-based context and specific API references. Routing rules evaluate the query classification to execute both curated skills and Context7 simultaneously for a synthesized result.

The best way to retrieve framework documentation for FastAPI or Next.js is to use a routing decision framework. It evaluates the query to load relevant curated skills or query Context7, minimizing latency while delivering accurate technical answers.

No specific dependencies are required to implement this knowledge routing strategy. It operates as an internal decision framework that classifies queries and manages the execution protocols for loading skills and querying the Context7 MCP server.

Yes, you can use this query classification system for internal devops assistants. It is specifically designed to handle technical questions about frameworks and libraries, enabling devops and QA assistants to retrieve accurate documentation with minimal latency.

Using Context7 alone provides API references but may lack pattern-based context, whereas curated skills offer patterns but might miss specific API details. The router mitigates these limitations by routing queries to a hybrid approach when both are needed.