Claude Code Plugins

Community-maintained marketplace

Feedback

hybrid-search-implementation

@sickn33/antigravity-awesome-skills
39.7k
2

Combine vector and keyword search for improved retrieval. Use when implementing RAG systems, building search engines, or when neither approach alone provides sufficient recall.

Install Skill

Shared

Installs to .agents/skills, used by Codex, Amp, Warp, Cursor, OpenCode, and more.

CodexAmp
Warp
CursorOpenCode
Cline
Gemini CLI
GitHub Copilot
Personal

Available across projects.

$npx skills-installer add @sickn33/antigravity-awesome-skills/hybrid-search-implementation --client shared
Project

Writes to .agents/skills.

$npx skills-installer add @sickn33/antigravity-awesome-skills/hybrid-search-implementation -p --client shared
Note: Review the skill instructions before using it.

SKILL.md

name hybrid-search-implementation
description Combine vector and keyword search for improved retrieval. Use when implementing RAG systems, building search engines, or when neither approach alone provides sufficient recall.
risk safe
source community
date_added 2026-02-27

Hybrid Search Implementation

Patterns for combining vector similarity and keyword-based search.

Use this skill when

  • 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

Do not use this skill when

  • The task is unrelated to hybrid search implementation
  • You need a different domain or tool outside this scope

Instructions

  • Clarify goals, constraints, and required inputs.
  • Apply relevant best practices and validate outcomes.
  • Provide actionable steps and verification.
  • If detailed examples are required, open resources/implementation-playbook.md.

Resources

  • resources/implementation-playbook.md for detailed patterns and examples.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.