rag-engineer

Designs retrieval-augmented generation pipelines with chunking, embeddings, and hybrid search strategies.

2|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/Shubh2310-developer/ENGUNITYCORE --skill rag-engineer-shubh2310-developer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rag-engineer
Source: https://github.com/Shubh2310-developer/ENGUNITYCORE/tree/main/.claude/skills/rag-engineer
Command: npx skills add https://github.com/Shubh2310-developer/ENGUNITYCORE --skill rag-engineer-shubh2310-developer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building RAG systems that return relevant context instead of hallucinations is hard: poor chunking, wrong embedding choices, and missing reranking silently degrade answer quality. This Skill provides expert guidance on designing retrieval pipelines where retrieval quality is measured and optimized separately from generation. ## Core Features & Use Cases - Semantic Chunking Strategies: Chunk documents by meaning and structure rather than fixed token counts, preserving sentence boundaries and context continuity. - Hierarchical & Hybrid Retrieval: Combine multi-level indexing (paragraph, section, document) with BM25/vector hybrid search and Reciprocal Rank Fusion for better precision. - Retrieval Evaluation & Anti-Patterns: Identify common failure modes such as embedding everything, skipping reranking, and never refreshing stale embeddings. - Use Case: When building a document Q&A feature over a company knowledge base, use this Skill to design the chunking strategy, select embedding models per content type, add metadata pre-filtering, and set up retrieval quality metrics before wiring the LLM prompt. ## Quick Start Ask the assistant to design a RAG pipeline for your document collection, including chunking strategy, embedding model selection, and hybrid search with reranking.

Frequently Asked Questions about rag-engineer

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

FAQPage Schema
How do I build a RAG pipeline for document question answering?

Start with semantic chunking that respects document structure, embed chunks with a model suited to your content type, and store them in a vector database. Add hybrid search combining BM25 with vector similarity, then rerank results before passing them to the LLM.

What chunking strategy works best for RAG systems?

Semantic chunking outperforms fixed-size chunking because it respects sentence boundaries, detects topic shifts via embedding similarity, and preserves headers and paragraphs. Include overlap between chunks for context continuity and attach metadata for filtering.

Should I use hybrid search or pure vector search for retrieval?

Hybrid search is recommended because pure semantic search misses exact keyword matches while BM25 misses conceptual similarity. Combine both scores with Reciprocal Rank Fusion and tune weights based on your query types.

Why does my RAG system return irrelevant context?

Common causes include fixed-size chunking that breaks context, missing metadata pre-filtering, no reranking step after first-stage retrieval, and stale embeddings after source documents change. Measure retrieval quality separately from generation to isolate the issue.

When should I not use the same embedding model for all content?

Different content types such as code, prose, and tables have different semantic structures, so a single embedding model may underperform on some of them. Evaluate embedding models per content type and refresh embeddings whenever source documents change.