rag-development
/rag-development
Knowledge base for production question-answering pipelines. TRIGGER WHEN: building, optimizing, or auditing RAG systems, including Graph RAG, CRAG, Self-RAG, and Agentic RAG.
- Author
- acaprino ↗
- Repository
- alfio-claude-plugins ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 8
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Knowledge base for production question-answering pipelines. TRIGGER WHEN: building, optimizing, or auditing RAG systems, including Graph RAG, CRAG, Self-RAG, and Agentic RAG.
Original author description
Knowledge base for production question-answering pipelines. TRIGGER WHEN: building, optimizing, or auditing RAG systems, including Graph RAG, CRAG, Self-RAG, and Agentic RAG.
How it works
- When to Use
- Quick Start Recommendation
- Reference Materials
- Pipeline Architecture
- Key Decision Points
SKILL.md preview
--- name: rag-development description: > Knowledge base for production question-answering pipelines. TRIGGER WHEN: building, optimizing, or auditing RAG systems, including Graph RAG, CRAG, Self-RAG, and Agentic RAG. --- <daodan_host_binding host="codex"> This binding governs execution of this package and its loaded references. It takes precedence over executable examples written for another host. Use only registered tools and their actual input schema; an example never creates a tool, argument, permission, model alias or nested worker capability. Preserve the generated worker allowlist, dependency closure, scope and delivery contracts. Codex binding: the adapter binds repository read to read_file, writes to apply_patch and shell execution to shell; use the equivalent registered tools of the active Codex runtime and their actual fields. In particular, a shell example's command, timeout and background fields are not automatically another runtime's cmd, yield_time_ms or session controls. Start the runtime's available isolated subagent mechanism with the complete rendered role body in its task prompt. Role Markdown and generated dispatch bodies are resources, not registered skills or a native role/subagent_type parameter. Use only declared role bindings and report an unavailable isolation mechanism. Load installed skills by their advertised exact IDs; workflow skills carry the <workflow>-workflow suffix. Named-agent examples do not override inline delivery. Required foreign providers use Codex's marketplace/install commands: codex plugin marketplace add <source>, then codex plugin add <provider>@<marketplace>. Register plugin-declared MCP servers through the active host's MCP configuration using the generated server command. Do not assume registration makes every tool available to a restricted worker. Inherit the active session's model and default variant. A source model alias such as sonnet is not a portable override; request a different model only through an explicit adapter mapping to a valid host identity and user authorization. The executing agent and its coordinator own continuation, recovery, verification and delivery. Skills supply knowledge and method instructions; they are not executors or a runtime persistence mechanism. Resolve each component by kind and exact installed identity. A role is dispatched as a worker, a skill loads instructions, and a workflow starts its declared method. Kernel owner-qualified skill references are logical provider identities: resolve them to the actual host registry name and verified installed provider path. Do not invent a registry string by adding an owner's prefix when the host does not use it. Do not load an agent identity as a skill or execute a workflow name as a shell command. Declared required foreign providers remain mandatory. If a required provider or capability (including required MCP access or isolation) is unavailable, stop its dependent phase and report the missing capability. Optional external providers follow the method's declared selection and absence behavior; their absence alone does not block the base workflow. Report any explicitly requested but unavailable provider contribution as unfulfilled and continue independent work. Do not install a different host's plugin or substitute unrelated skills to claim coverage. Shell execution alone does not establish interactive stdin. Before a capture or checkpoint, use an available session-control mechanism. When stdin is unavailable, keep user-driven capture in a supported background process with bounded output and an explicit stop signal controlled by the coordinator after the user's completion message. Close owned browser/process resources on completion or cancellation. Continue working within the current authorization while the requested result is achievable. After a tool error, inspect its cause, correct the relevant input or implementation, retry when justified and verify the outcome; never repeat a failing action blindly. Do not close the turn with a promise or a partial result when an authorized next step can still produce or verify the requested result. Stop only for a documented real impediment, a missing required capability, an unresolved human decision or the caller's stop request. At that boundary, report completed results, remaining work and the concrete prerequisite for continuation; continue any independent work that the blocker does not prevent. A tool's successful exit, a worker stop or an idle session is not the deliverable. Return final text naming observed findings, artifact paths, executed checks and blockers. An empty worker result is missing delivery: inspect or resume that worker when permitted, or record failure. Verify required artifacts and candidate gates before marking the requested outcome complete. This is an execution binding, not a rewrite of source examples. Preserve programming language fences, domain code and host APIs that are the subject of marketplace-ops or agent-sdk-builder. A host-as-subject API is not a tool provided to this session. Compiled binding and static checks do not prove an installed host executed a run. </daodan_host_binding> # RAG Development Comprehensive knowledge base for building production-grade Retrieval-Augmented Generation systems. ## When to Use - Building a new RAG pipeline from scratch - Choosing chunking strategy, embedding model, or vector database - Implementing hybrid search, re-ranking, or contextual retrieval - Evaluating RAG quality with RAGAS or DeepEval - Optimizing production RAG for cost, latency, or accuracy - Designing multi-tenant RAG with access control - Upgrading from naive RAG to advanced patterns ## Quick Start Recommendation For 80% of use cases, start with: 1. **Chunking**: Recursive character splitting at 512 tokens, 10-15% overlap 2. **Embedding**: OpenAI `text-embedding-3-small` (best value) or Cohere `embed-v4` (best accuracy) 3. **Vector DB**: Qdrant with scalar INT8 quantization 4. **Retrieval**: Hybrid search (dense + sparse + RRF) 5. **Evaluation**: RAGAS metrics from day one Then upgrade incrementally based on measured failures: - Keyword misses -> add sparse vectors (SPLADE/BM25) - Ambiguous chunks -> add contextual retrieval (Anthropic pattern) - Irrelevant results -> add cross-encoder re-ranking - Multi-hop failures -> upgrade to agentic RAG ## Reference Materials Detailed reference documents are in the `references/` directory: - `chunking-strategies.md` -- all chunking approaches with code, benchmarks, and selection guide - `embedding-models.md` -- model comparison, Matryoshka embeddings, fine-tuning, sparse/dense/multi-vector - `retrieval-patterns.md` -- hybrid search, HyDE, contextual retrieval, re-ranking, MMR - `advanced-rag-patterns.md` -- Graph RAG, RAPTOR, CRAG, Self-RAG, Agentic RAG, multi-modal RAG - `vector-databases.md` -- Qdrant deep dive, database comparison, scaling strategies - `production-guide.md` -- evaluation, observability, caching, security, cost optimization ## Pipeline Architecture ``` Document Ingestion: Raw Docs -> Preprocessing (Unstructured.io) -> Chunking -> Context Enrichment -> Embedding -> Vector DB Query Pipeline: User Query -> Query Transform -> Encode (Dense + Sparse) -> Hybrid Search -> Re-rank -> LLM Generation Evaluation Loop: Ground Truth + Predictions -> RAGAS/DeepEval -> Faithfulness, Relevancy, Precision, Recall ``` ## Key Decision Points | Decision | Default | Upgrade When | |----------|---------|-------------| | Chunking | Recursive 512 tok | Structured docs -> markdown-aware; cross-refs -> late chunking | | Embedding | text-embedding-3-small | Need accuracy -> embed-v4; self-hosted -> NV-Embed-v2 | | Vector DB | Qdrant + INT8 | Already on Postgres -> pgvector; need managed -> Pinecone | | Search | Dense only | Keyword misses -> add sparse hybrid; poor diversity -> add MMR | | Re-ranking | None | Top-k results contain irrelevant items -> add Cohere Rerank | | Caching | None | Production latency/cost concerns -> semantic cache | | Evaluation | Manual spot checks | Any production use -> RAGAS automated metrics |
Files in this package (8)
- SKILL.md 8 KB
- SKILL.toml 1 KB
- references/advanced-rag-patterns.md 11 KB
- references/chunking-strategies.md 9 KB
- references/embedding-models.md 14 KB
- references/production-guide.md 11 KB
- references/retrieval-patterns.md 11 KB
- references/vector-databases.md 8 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · acaprino/alfio-claude-plugins | 100 | MIT |
| acaprino/alfio-claude-plugins | 100 | MIT |
| acaprino/alfio-claude-plugins | 100 | MIT |
| acaprino/alfio-claude-plugins | 100 | MIT |
| acaprino/alfio-claude-plugins | 100 | MIT |
| acaprino/alfio-claude-plugins | 100 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 24ccbd4969fa (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100agentic-rag
Agent-driven RAG patterns. Self-RAG, Corrective RAG (CRAG) with web fallback, Adaptive RAG with routing classifier, ReAct with retrieval tool, multi-hop retrieval, plan-and-execute, LangGraph state machines for RAG. USE WHEN: user mentions "agentic RAG", "Self-RAG", "Corrective… - 100corrective-rag
Implement Corrective RAG (CRAG) and Self-RAG for reliable, self-healing retrieval systems. Use this skill when building reliable RAG, preventing hallucinations, implementing retrieval evaluation, or adding self-correction to RAG pipelines. Activate when: corrective RAG, CRAG,… - 98langgraph-rag
LangGraph state machines for RAG and agentic flows. Covers typed state, conditional edges for routing (answer/clarify/retrieve/rewrite), checkpointing with SqliteSaver/PostgresSaver, human-in-the-loop interrupts, multi-agent supervisor patterns, Self-RAG and CRAG as explicit… - 90agentic-rag
Use when building self-correcting retrieval systems for AI agents. Keywords: RAG, retrieval, Corrective RAG, Self-RAG, query decomposition, reranking, hallucination, grounding. - 95production-rag-checklist
Deploy RAG systems to production with proper architecture, monitoring, and operations. Use this skill when deploying RAG to production, scaling retrieval systems, implementing RAG monitoring, or building enterprise RAG infrastructure. Activate when: production RAG, RAG… - 100agentic-ai-dev
This skill provides patterns and templates for building production AI agents with Python 3.14, LangChain v1.2.8, LangGraph v1.0.7, and FastAPI 0.135.2. Use when creating AI agents, RAG systems, graph workflows, tools, memory systems, or agent tests.