agentleFS
hiteshbandhuhiteshbandhu/skills-i-use/skills/ai-engineer-talks/build-rag-search-stacks/SKILL.md

build-rag-search-stacks

Skill1 starsChanged 5 months agoMITView on GitHub

Runs checklists and workflows for designing, layering, evaluating, and operating production RAG and AI search — hybrid retrieval, agentic context tools, enterprise eval, web neural search, managed platforms, document agents. Use when the user builds retrieval for agents, picks vector vs lexical vs hybrid, designs eval for augmented AI, scales regulated RAG, compares search APIs, or says "RAG stack", "hybrid search", "agentic RAG", "vector benchmark".

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the decision tree below.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Build RAG and AI search stacks

Action playbook from thirteen AI Engineer talks. Do not summarize talks — pick a workflow and execute it.

Supporting files (read when needed):

  • workflows.md — workflows A–L (steps, deliverables, stop conditions)
  • source-index.md — src-NNN → talk learnings in ingest-into-skills

Optional deliverables: {SKILL_OUTPUT_DIR}/build-rag-search-stacks/ — see skills-i-use OUTPUT.md.


Step 0 — Pick workflow

Use the decision tree below. Open the matching section in workflows.md.

What is the user trying to do?
├─ Choose RAG vs long-context vs fine-tune           → A
├─ Design hybrid retrieval (lexical + vector + rerank) → B
├─ Vet vector DB / ANN vendor claims                 → C
├─ Ship regulated / legal / enterprise corpus RAG      → D
├─ Layer techniques without over-building              → E
├─ Build agent tools for multi-source context          → F
├─ Persist memory + tool scale for agents              → G
├─ Evaluate web / augmented AI search in production    → H
├─ Open-web research agent (long semantic queries)     → I
├─ Fast enterprise doc Q&A (tables, grounding)         → J
├─ Document-heavy knowledge work (Excel, SharePoint)   → K
└─ Vertical product KB (sales, onboarding assets)      → L

Stop summarizing once a workflow is identified — run its checklist.


Install

Copy this folder into your agent’s skills directory, for example:

cp -r skills/ai-engineer-talks/build-rag-search-stacks ~/.claude/skills/
cp -r skills/ai-engineer-talks/build-rag-search-stacks ~/.cursor/skills/
cp -r skills/ai-engineer-talks/build-rag-search-stacks ~/.codex/skills/

From skills-i-use or ingest-into-skills after sync.

Source corpus: ingest-into-skills playlists/rag-search-2025/.


Cross-cutting rules

RuleSource
Embeddings are the dominant lever in most stacks[src-009 @ 4:11]
AI search = concept retrieval + intent + filters + agent loops[src-009 @ 2:27]
Instruction-tuned / steerable embeddings for query shape[src-009 @ 10:37]
Agentic loop: decompose → search → LLM expand → search again[src-009 @ 7:25]
Contextual retrieval: enrich chunks with titles/global metadata[src-010 @ 8:29]
Multimodal: screenshot → multimodal embedding for slides/tables[src-010 @ 15:07]

Disputed steps: read talk in source-index.md.


Output to user

  1. Name the workflow (A–L) and what you are producing
  2. Save artifacts under ./skill-outputs/build-rag-search-stacks/ when the user wants files (diagrams, rubrics, checklists)
  3. Do not auto-commit

Invocation examples

@build-rag-search-stacks design hybrid retrieval for our legal corpus
help me evaluate web search APIs for agents
we need enterprise RAG — where do we start?

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.