H
hybrid-search-implementation
About hybrid-search-implementation
A skill for engineers combining vector similarity and keyword search in retrieval systems. It outlines fusion and reranking approaches for queries that need both semantic matches and exact terms.
Key features
- 01Vector and keyword search
- 02RRF and weighted-score fusion
- 03Cross-encoder reranking
- 04Cascade retrieval pattern
- 05Search tuning and evaluation
Use cases
- 01Improving recall in RAG systems
- 02Finding exact names or codes
- 03Searching domain-specific vocabulary
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ wshobson/ agents --skill hybrid-search-implementationAfter installing, type/hybrid-search-implementationin Claude Code to confirm it loaded.
Bundled filesreferences/details.md
Details
From the project READMEHybrid Search Implementation
Patterns for combining vector similarity and keyword-based search.
When to Use This Skill
- Building RAG systems with improved recall
- Combining semantic understanding with exact matching
- Handling queries with specific terms (names, codes)
- Improving search for domain-specific vocabulary
- When pure vector search misses keyword matches
Core Concepts
1. Hybrid Search Architecture
Query → ┬─► Vector Search ──► Candidates ─┐
│ │
└─► Keyword Search ─► Candidates ─┴─► Fusion ─► Results
2. Fusion Methods
| Method | Description | Best For |
|---|---|---|
| RRF | Reciprocal Rank Fusion | General purpose |
| Linear | Weighted sum of scores | Tunable balance |
| Cross-encoder | Rerank with neural model | Highest quality |
| Cascade | Filter then rerank | Efficiency |
Templates and detailed worked examples
Full template library and detailed worked examples live in references/details.md. Read that file when you need the concrete templates.
Best Practices
Do's
- Tune weights empirically - Test on your data
- Use RRF for simplicity - Works well without tuning
- Add reranking - Significant quality improvement
- Log both scores - Helps with debugging
- A/B test - Measure real user impact
Don'ts
- Don't assume one size fits all - Different queries need different weights
- Don't skip keyword search - Handles exact matches better
- Don't over-fetch - Balance recall vs latency
- Don't ignore edge cases - Empty results, single word queries
Comments
Markdown supported