Menu

Individual skill

agentsop-query-routing

0upvotes

Routes heterogeneous queries to the appropriate index, tool, or answering engine before retrieval. Use when one endpoint serves multiple handlers, such as summary, vector retrieval, text-to-SQL, or tools, and query types require different paths. Covers LLM, semantic, and rule-based routers, confidence thresholds, fallbacks, and framework mappings. Do not use when one handler serves all queries or branching is fixed.

skills/agentsop-query-routing/SKILL.md

Read pinned source

Source commit cf4376869e5f23f82404c3021a2a1315dfca318d

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
465
Repository last updated
Oct 24, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Query-Type Routing · Enhancement Overlay

> Third-person operating model for a coder agent that owns a multi-handler
> answering surface. Audience is the LLM agent writing/reviewing the routing
> code — not the end user.

> **One sentence**: *A retriever is shaped by the query type it was built for;
> a summary index, a vector index, and a text-to-SQL engine are not
> interchangeable — so classify the query and route first, then retrieve.*

This is an **ENHANCE overlay**. It distills the cross-framework *routing
pattern* from three source skills. For the per-framework API, cross-link the
base skill: `[[llamaindex]]` (`RouterQueryEngine`), `[[agentsop-dify]]` (Question
Classifier node), `[[agentsop-langgraph]]` (conditional edges).