Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
alirezarezvani avatar

Rag Architect

  • 590 installs
  • 23.5k repo stars
  • Updated July 17, 2026
  • alirezarezvani/claude-skills

rag-architect is a Claude Code skill that helps developers design, implement, and optimize production-grade RAG pipelines including chunking, embeddings, vector search, and retrieval evaluation.

About

rag-architect is an AI engineering skill for developers building retrieval-augmented generation systems that need accurate, scalable knowledge retrieval. The skill spans the full RAG lifecycle: document ingestion, fixed-size and semantic chunking strategies, embedding model selection, vector database search, reranking, and retrieval evaluation frameworks. Developers reach for rag-architect when choosing chunk sizes, tuning retrieval quality, implementing vector search, or debugging poor LLM answers caused by bad context retrieval. It is suited to production chatbots, internal knowledge bases, and agent tools that must ground responses in private documents rather than model memory alone.

  • Comprehensive RAG pipeline design covering document processing through evaluation frameworks
  • Compares Fixed-Size, Token-based, Sentence-based, and Semantic chunking strategies with pros, cons, and use cases
  • Guides selection of embedding models, vector databases, and retrieval strategies for accuracy and scale
  • Includes optimization techniques, overlap strategies, and evaluation frameworks for production systems
  • Delivers complete architecture recommendations that feed directly into implementation

Rag Architect by the numbers

  • 590 all-time installs (skills.sh)
  • Ranked #1,583 of 16,565 AI & Agent Building skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/alirezarezvani/claude-skills --skill rag-architect

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs590
repo stars23.5k
Security audit3 / 3 scanners passed
Last updatedJuly 17, 2026
Repositoryalirezarezvani/claude-skills

How do you design production RAG retrieval pipelines?

Design, optimize, and implement production-grade RAG pipelines including chunking, embeddings, vector search, and retrieval evaluation.

Who is it for?

Backend and ML engineers implementing knowledge retrieval for LLM apps who need structured guidance on chunking, embeddings, and evaluation.

Skip if: Developers who only need a single-vector-store quickstart with no tuning, evaluation, or production retrieval optimization requirements.

When should I use this skill?

The user asks to design RAG pipelines, optimize retrieval, choose embedding models, implement vector search, or evaluate knowledge retrieval quality.

What you get

Chunking strategy specs, embedding and vector search architecture, reranking configuration, and retrieval evaluation benchmarks.

  • RAG architecture design
  • Chunking and retrieval strategy
  • Evaluation framework outline

Files

SKILL.mdMarkdownGitHub ↗

RAG Architect

Design, tune, and evaluate production RAG pipelines with three deterministic tools. Run the tools against the actual corpus and requirements — do not pick chunk sizes or databases by intuition.

Hard rules

1. Never present model names or vendor prices as current facts. Embedding models and vector-DB pricing rot in months. Recommend a tier (see table below), name a current-generation candidate, and tell the user to verify against the provider's live pricing page. 2. Every design ends with an evaluation run. A RAG design without retrieval_evaluator.py numbers is a hypothesis, not a deliverable. 3. Chunking is corpus-driven. Run chunking_optimizer.py on the real documents before choosing a strategy.

Embedding model tiers (pattern, not price list)

TierCurrent-generation examples (verify before use)When
Fast / self-hostedall-MiniLM-L6-v2, bge-smallCost-sensitive, small scale, real-time
Balanced openall-mpnet-base-v2, bge-large, e5-largeQuality without API dependency
Quality APItext-embedding-3-large, voyage-3-largeAccuracy-priority general retrieval
Codevoyage-code-3, CodeBERT-familyCode search corpora

Pricing discipline: build the cost model with a placeholder table — columns model | $/1M tokens (verify) | dims | as-of date — and have the user fill in live numbers. Same for vector DBs (Pinecone/Weaviate/Qdrant/Chroma/pgvector): the selection criteria (managed vs self-hosted, scale, filtering, existing Postgres) are durable; the dollar figures are not.

Workflow

All paths relative to this skill folder. Outputs chain: corpus analysis → design → evaluation.

1. Analyze the corpus and pick chunking

python3 chunking_optimizer.py /path/to/docs --extensions .md .txt -o chunking.json

Emits chunking.json with corpus_info, per-strategy strategy_results, a recommendation, and sample_chunks. Use recommendation.strategy and its config; show the user 2-3 sample_chunks so they can sanity-check boundaries.

2. Design the pipeline from requirements

Write a requirements JSON with these keys (all required): document_types[], document_count, avg_document_size (chars), queries_per_day, query_patterns[], latency_requirement, budget_monthly, accuracy_priority (0-1), cost_priority (0-1), maintenance_complexity.

python3 rag_pipeline_designer.py requirements.json -o design.json

Emits design.json with chunking, embedding, vector_db, retrieval, reranking, evaluation, total_cost, architecture_diagram (mermaid), and config_templates. Present the diagram; label every cost_monthly figure as an estimate to verify (rule 1).

3. Evaluate retrieval quality

Prepare queries.json (list of {id, text} or {"queries": [...]}) and ground_truth.json ({query_id: [relevant_doc_ids]}), then:

python3 retrieval_evaluator.py queries.json /path/to/docs ground_truth.json --k-values 3 5 10 -o eval.json

Reports precision@k, recall@k, MRR, NDCG@k, plus poor_precision_examples / poor_recall_examples for failure analysis.

4. Verification loop

The design is done only when:

1. eval.json meets targets — typical floors: precision@5 ≥ 0.8, recall@10 ≥ 0.85 (set per use case with the user). 2. If below target: inspect the poor-example lists, then change one variable (chunking strategy → re-run step 1; embedding tier; add reranking; hybrid retrieval) and re-run step 3. Repeat. 3. Every recommended model/price in the deliverable carries a "verify current pricing/model availability" note with an as-of date.

References

  • references/chunking_strategies_comparison.md — strategy trade-offs the optimizer implements
  • references/embedding_model_benchmark.md — benchmark methodology (dated snapshot; staleness warning at top)
  • references/rag_evaluation_framework.md — metric definitions (faithfulness, relevance, precision/recall/NDCG)

Related skills

How it compares

Pick rag-architect when retrieval design and evaluation matter; use lighter doc-fetch skills when the task is only pulling library READMEs into chat.

FAQ

What RAG topics does rag-architect cover?

rag-architect covers document processing and chunking, embedding model selection, vector search implementation, reranking considerations, and retrieval evaluation frameworks. The skill targets production-grade pipelines rather than toy demos.

When should a developer use rag-architect?

rag-architect fits when a developer must design or optimize RAG pipelines, choose embedding models, implement vector search, or build knowledge retrieval systems where retrieval accuracy directly affects LLM output quality.

Is Rag Architect safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

AI & Agent Buildingagentsllmautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.