Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
qdrant-search-quality - Skill - OpenSmartRoute
Skillv1.0.0
qdrant-search-quality
Diagnoses and improves Qdrant search relevance. Use when someone reports 'search results are bad', 'wrong results', 'low precision', 'low recall', 'irrelevant matches', 'missing expected results', or…
Imported from github/awesome-copilot (skills/qdrant-search-quality/SKILL.md). Install upstream with npx skills add github/awesome-copilot --skill qdrant-search-quality. Copyright stays with the author.
Qdrant Search Quality
First determine whether the problem is the embedding model, Qdrant configuration, or the query strategy. Most quality issues come from the model or data, not from Qdrant itself. If search quality is low, inspect how chunks are being passed to Qdrant before tuning any parameters. Splitting mid-sentence can drop quality 30-40%.
Start by testing with exact search to isolate the problem Search API
Diagnosis and Tuning
Isolate the source of quality issues, tune HNSW parameters, and choose the right embedding model. Diagnosis and Tuning
Search Strategies
Hybrid search, reranking, relevance feedback, and exploration APIs for improving result quality. Search Strategies
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slotcurl-s-X POST https://osr-api.kindrock-caaab1a2.centralindia.azurecontainerapps.io/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Installed into a catalogue, chosen by a router
Install qdrant-search-quality and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.
{
"ocm": "1",
"id": "github-awesome-copilot-qdrant-search-quality",
"kind": "skill",
"name": "qdrant-search-quality",
"description": "Diagnoses and improves Qdrant search relevance. Use when someone reports 'search results are bad', 'wrong results', 'low precision', 'low recall', 'irrelevant matches', 'missing expected results', or asks 'how to improve search quality?', 'which embedding model?', 'should I use hybrid search?', 'should I use reranking?'. Also use when search quality degrades after quantization, model change, or data growth.",
"publisher": "github",
"version": "1.0.0",
"capabilities": {
"domains": [
"medical",
"coding"
],
"tags": [
"skill-md",
"skills-sh"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Diagnoses and improves Qdrant search relevance. Use when someone reports 'search results are bad', 'wrong results', 'low precision', 'low recall', 'irrelevant matches', 'missing expected results', or asks 'how to improve search quality?', 'which embedding model?', 'should I use hybrid search?', 'should I use reranking?'. Also use when search quality degrades after quantization, model change, or data growth."
],
"primary": false,
"metadata": {
"source": {
"provider": "skills.sh",
"repository": "https://github.com/github/awesome-copilot",
"path": "skills/qdrant-search-quality/SKILL.md",
"ref": "HEAD",
"url": "https://github.com/github/awesome-copilot/blob/HEAD/skills/qdrant-search-quality/SKILL.md",
"key": "github/awesome-copilot/skills/qdrant-search-quality/SKILL.md"
},
"allowed_tools": [
"Read",
"Grep",
"Glob"
]
},
"instructions": "# Qdrant Search Quality\n\nFirst determine whether the problem is the embedding model, Qdrant configuration, or the query strategy. Most quality issues come from the model or data, not from Qdrant itself. If search quality is low, inspect how chunks are being passed to Qdrant before tuning any parameters. Splitting mid-sentence can drop quality 30-40%.\n\n- Start by testing with exact search to isolate the problem [Search API](https://search.qdrant.tech/md/documentation/search/search/?s=search-api)\n\n\n## Diagnosis and Tuning\n\nIsolate the source of quality issues, tune HNSW parameters, and choose th",
"cost": {
"context_tokens": 209
}
}
Fetch it by URL: GET /api/v1/registry/github-awesome-copilot-qdrant-search-quality/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.
