rag-engineer

Optimize retrieval-augmented generation pipelines for LLM-powered tasks.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/sixscripts-ai/ghostssh --skill rag-engineer-sixscripts-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rag-engineer
Source: https://github.com/sixscripts-ai/ghostssh/tree/main/skills/rag-engineer
Command: npx skills add https://github.com/sixscripts-ai/ghostssh --skill rag-engineer-sixscripts-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retrieval quality is the bottleneck in many LLM workflows; this Skill provides a structured approach to design, implement, and operate Retrieval-Augmented Generation systems that fuse embeddings, chunking strategies, and vector databases to deliver accurate, up-to-date results from large document collections.

Core Features & Use Cases

  • Vector embeddings and similarity search
  • Document chunking and preprocessing
  • Retrieval pipeline design
  • Semantic search implementation
  • Context window optimization
  • Hybrid search (keyword + semantic)
  • Use cases: building RAG pipelines, semantic document retrieval, and knowledge-base querying

Quick Start

Configure a base RAG pipeline and perform a first retrieval pass over your document corpus.

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 retrieval-augmented generation pipeline for document retrieval?

To build a retrieval-augmented generation pipeline, you need to orchestrate document chunking, generate vector embeddings, and configure a vector database for similarity search. This delivers accurate context to LLMs from large knowledge bases.

What is semantic chunking and when do I need it for vector search?

Semantic chunking splits documents into meaningful sections before generating vector embeddings. You need it for vector search workflows to preserve context boundaries, ensuring the retrieval pipeline returns highly relevant segments rather than arbitrary text fragments.

What's the best way to implement hybrid search for LLM workflows?

The best way to implement hybrid search is to fuse keyword search with semantic vector similarity. This approach optimizes retrieval pipeline design by capturing both exact term matches and conceptual relationships, improving overall document retrieval accuracy.

Does this approach require a dedicated vector database for semantic search?

Implementing semantic search requires a system to store and query vector embeddings. A dedicated vector database or vector search index is necessary to perform similarity searches across large document collections efficiently within the retrieval pipeline.

Why does my RAG pipeline return poor retrieval results from my knowledge base?

Poor retrieval results in a RAG pipeline often stem from suboptimal document chunking strategies or inadequate embedding design. Optimizing context window usage and integrating hybrid search can significantly improve semantic search relevance.