Qdrant Search Strategies logo

Qdrant Search Strategies

Organization
qdrant
qdrant-search-strategies

Guides Qdrant search strategy selection. Use when someone asks 'should I use hybrid search?', 'how to rerank?', 'results are not relevant', 'I don't get needed results from my dataset but they're there', 'retrieval quality is not good enough', 'results too similar', 'need diversity', 'MMR', 'relevance feedback', 'recommendation API', 'discovery API', or 'missing keyword matches'

Overview

Publisherqdrant
Repositoryskills
Skill nameqdrant-search-strategies
Stars
262
Forks
31
Bundled files
Instructions only
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by qdrant on GitHub. Read the source before you install it.

Installation

Install the Qdrant Search Strategies AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/qdrant/skills/tree/main/skills/qdrant-search-quality/search-strategies
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/qdrant/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/qdrant-search-quality/search-strategies .claude/skills/qdrant-search-strategies
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Qdrant Search Strategies in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Qdrant Search Strategies on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Qdrant Search Strategies is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

How to Improve Search Results with Advanced Strategies

These strategies complement basic vector search. Use them after confirming the embedding model is fitting the task and HNSW config is correct. If exact search returns bad results, verify the selection of the embedding model (retriever) first. If the user wants to use a weaker embedding model because it is small, fast, and cheap, use reranking or relevance feedback to improve search quality.

Each symptom may require a different strategy: diagnose and address them independently. A single project can have multiple symptoms at once, and fixing one (e.g. adding hybrid search for keyword misses) may not fix the others (e.g. redundant results may still need MMR; poor precision may still need reranking).

SymptomStrategy
Missing exact/keyword matchesHybrid search
Right documents exist but rank low (good recall, poor precision)Multistage queries / reranking
Dense retriever misses relevant items entirely, or reranking too costlyRelevance feedback
Results are redundant / near-duplicateMMR
Need to steer with example pointsRecommendation / Discovery API
Need business-logic-based rankingScore boosting

Missing Keyword Matches or Need to Combine Multiple Search Signals

Use when: pure vector search misses keyword/domain term matches, or the use case benefits from combining searches on multiple representations (including languages and modalities) of the same item.

See how to use hybrid search

Right Documents Found But Not in the Top Results

Use when: good recall but poor precision (right docs in top-100, not top-10).

Dense Retriever Misses Relevant Items or Reranking Is Too Costly

Use when: dense retriever misses relevant items you know exist in the collection; relevant documents lie outside the initial ANN retrieval pool; reranking a large candidate pool is too slow or expensive; using a small/cheap embedding model but need quality close to a larger model; or want to improve top-1/3 precision without the full cost of reranking.

See Relevance Feedback in Qdrant

Results Too Similar

Use when: top results are redundant, near-duplicates, or lack diversity. Common in dense content domains (academic papers, product catalogs).

  • Use MMR (v1.15+) as a query parameter with diversity to balance relevance and diversity MMR
  • Start with diversity=0.5, lower for more precision, higher for more exploration
  • MMR is slower than standard search. Only use when redundancy is an actual problem.

Want to improve search results based on examples (positive and negative)

Use when: you can provide positive and negative example points to steer search closer to positive and further from negative.

  • Recommendation API: positive/negative examples to recommend fitting vectors Recommendation API
    • Best score strategy: better for diverse examples, supports negative-only Best score
  • Discovery API: context pairs (positive/negative) constrain the search region, either around a target (discovery search) or without one (context search) Discovery

Have Business Logic Behind Results Relevance

Use when: results should be additionally ranked according to some business logic based on data, like recency or distance.

Check how to set up in Score Boosting docs

What NOT to Do

  • Use hybrid search before verifying pure vector search quality (adds complexity, may mask model issues)
  • Apply one strategy (e.g. hybrid search) as a blanket fix for multiple distinct symptoms, diagnose and treat each symptom separately (see table above)
  • Skip evaluation when adding relevance feedback: score the end-to-end pipeline to confirm it actually helps Pipeline Output Quality

Frequently asked questions

What does the Qdrant Search Strategies AI skill do?

Guides Qdrant search strategy selection. Use when someone asks 'should I use hybrid search?', 'how to rerank?', 'results are not relevant', 'I don't get needed results from my dataset but they're there', 'retrieval quality is not good enough', 'results too similar', 'need diversity', 'MMR', 'relevance feedback', 'recommendation API', 'discovery API', or 'missing keyword matches'

Why use Qdrant Search Strategies on TypingMind?

Because you install it once and use it with any model. Qdrant Search Strategies is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Qdrant Search Strategies in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/qdrant/skills/tree/main/skills/qdrant-search-quality/search-strategies. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Qdrant Search Strategies?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Qdrant Search Strategies?

As many as you like. As long as a model supports skills, you can use Qdrant Search Strategies with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Qdrant Search Strategies AI skill free?

Yes. It is published on GitHub by qdrant under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇