CtrlK
BlogDocsLog inGet started
Tessl Logo

rag-architect

Use when the user asks to design a RAG pipeline, choose a chunking strategy or embedding model, pick a vector database, or evaluate retrieval quality (precision@k, recall@k, NDCG). Examples: 'design a RAG system for our docs', 'what chunk size should I use for this corpus', 'evaluate my retriever against ground truth'. NOT for general LLM cost tuning (use llm-cost-optimizer) or agent loops over retrieval (use agenthub).

77

Quality

98%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is rag-architect in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

96%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A high-quality, executable skill body: concise, actionable, and structured around a clear workflow with a verification loop. The only gap is that the referenced references/ and script files are not actually bundled, weakening progressive disclosure.

Suggestions

Bundle the referenced files under references/ (chunking_strategies_comparison.md, embedding_model_benchmark.md, rag_evaluation_framework.md) so the cited paths resolve.

Bundle the three scripts (chunking_optimizer.py, rag_pipeline_designer.py, retrieval_evaluator.py) under scripts/ and update the commands to reference their bundled paths, or note where they live.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: assumes Claude's knowledge of RAG/embeddings, gives commands and output schemas without padding, and every section (tier table, workflow, verification) earns its place.

5 / 5

Actionability

Fully executable, copy-paste-ready commands with flags and output filenames ('python3 chunking_optimizer.py /path/to/docs --extensions .md .txt -o chunking.json'), explicit required requirements-JSON keys, and an evaluator command with k-values.

5 / 5

Workflow Clarity

A numbered four-step pipeline with explicit chaining (corpus analysis → design → evaluation) and a verification loop with target floors, a one-variable change rule, and re-run guidance — a full validate/fix/retry feedback loop.

5 / 5

Progressive Disclosure

The body is a well-organized overview with clearly signaled one-level-deep references to references/*.md, but the referenced files (and the referenced scripts chunking_optimizer.py / rag_pipeline_designer.py / retrieval_evaluator.py) are not present in the bundle, so navigation does not fully resolve.

4 / 5

Total

19

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A tightly written, third-person description with concrete actions, natural trigger phrases, and explicit scope boundaries. It cleanly answers what the skill does and when to use it with minimal conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'design a RAG pipeline, choose a chunking strategy or embedding model, pick a vector database, or evaluate retrieval quality (precision@k, recall@k, NDCG)' — with comprehensive coverage of the skill's scope.

5 / 5

Completeness

Explicitly answers both what (design/tune/evaluate RAG pipelines) and when via a concrete 'Use when...' clause with example trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural user phrasing with synonyms and example quotes ('design a RAG system for our docs', 'what chunk size should I use', 'evaluate my retriever against ground truth') plus domain terms like chunking, embedding, vector database, retriever.

5 / 5

Distinctiveness Conflict Risk

Carves a clear niche and adds explicit negative boundaries — 'NOT for general LLM cost tuning (use llm-cost-optimizer) or agent loops over retrieval (use agenthub)' — minimizing wrong-skill triggers.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

16

Passed

Repository
alirezarezvani/claude-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.