qdrant-hybrid-search-combining

Fuses ranked candidate lists from multiple Qdrant prefetches using RRF, DBSF, or custom fusion.

3|1|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/PALabs-v1/AI_friend --skill qdrant-hybrid-search-combining-palabs-v1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qdrant-hybrid-search-combining
Source: https://github.com/PALabs-v1/AI_friend/tree/main/.claude/skills/qdrant-search-quality/search-strategies/hybrid-search/combining-searches
Command: npx skills add https://github.com/PALabs-v1/AI_friend --skill qdrant-hybrid-search-combining-palabs-v1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Hybrid search pipelines run multiple parallel searches (dense, sparse, BM25) whose scores are on incomparable scales, making it unclear how to merge them into one ranked result. This Skill guides you through choosing and configuring the right fusion method in Qdrant so your combined ranking is sound. ## Core Features & Use Cases - Rank- and distribution-based fusion: Apply RRF (with tunable k and per-prefetch weights) or DBSF when prefetch scores are not comparable. - Custom fusion with FormulaQuery: Combine per-prefetch scores with payload-driven boosts like recency or popularity, with correct defaults and normalization. - Reranking-based fusion: Use multivector late-interaction models (ColBERT, ColPali, ColQwen) as the outer query for high-precision top-K results. - Use Case: You combine BM25 sparse search with dense cosine search and the merged ranking looks wrong; this Skill helps you pick RRF as a baseline, tune weights per collection, and avoid linear fusion on incomparable score ranges. ## Quick Start Ask how to combine sparse and dense search results in Qdrant and whether to use RRF or DBSF for your hybrid query.

Frequently Asked Questions about qdrant-hybrid-search-combining

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I combine sparse and dense search results in Qdrant?

Use the outer query to fuse ranked candidate lists from parallel prefetches. Start with RRF when scores are on incomparable scales like BM25 and cosine, or use DBSF to normalize score distributions per prefetch before fusing.

RRF vs DBSF: which fusion method should I use?

RRF is rank-based, ignores score magnitudes, and works as a decent default when scores are incomparable. DBSF normalizes each prefetch's score distribution using mean plus or minus three deviations, but its absolute scores are not comparable across queries.

How do I add per-prefetch weights in hybrid search fusion?

Use Weighted RRF to assign per-prefetch weights when one search should dominate. Weights must be tuned per collection and retriever score distributions rather than chosen by intuition.

Can I boost fused results by payload fields like recency?

Yes, use FormulaQuery to access each prefetch's score and payload values in a custom expression. Provide defaults for every score index and normalize each score with decay or min-max before combining linearly.

When should I use multivector reranking instead of RRF?

Use late-interaction multivector reranking (ColBERT, ColPali, ColQwen) when you need high top-K precision and prefetches already have good recall. It is the most precise but most resource-heavy option, so evaluate cheaper alternatives like MUVERA first.

Why does linear weighted fusion give bad hybrid search results?

Linear weighted fusion fails when prefetch scores are on incomparable ranges, such as BM25 versus cosine similarity. Normalize each score distribution first or switch to rank-based RRF before applying any weights.