build
Skill24 starsChanged 19 days agoMITView on GitHub
Build a RAG component hands-on with guided steps
168 other projects use a version of this.
Adopted by
Most recently taken up by
- realsenseai/librealsensetheir own version, first seen Nov 16, 2026
- mannobeats/hyper-tastetheir own version, first seen Nov 16, 2026
- jayden-dang/skillstheir own version, first seen Nov 16, 2026
- colinc86/glosstheir own version, first seen Nov 16, 2026
- wald21x6-ops/builder-kittheir own version, first seen Nov 16, 2026
- mategog/dev-teamtheir own version, first seen Nov 16, 2026
Used with
Projects with it also use backprop, finances and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
JuliusBrusseeSkillbackprop
Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.
Also in 4 projects that use this
GerardoRdz96Skillfinances
Use when Gera talks about his money — logging an expense ("I spent X on Y"), checking where he stands this pay-period, closing a period, planning debt payoff, onboarding his financial picture, or asking for budgeting/finance opinions. Servy's financial brain. Triggers — "I spent", "log this expense", "where am I this period", "close the period", "how's my budget", "debt plan", "should I pay off", "finances onboard", "/finances".
Also in 3 projects that use this
cpiprintSkillfavicon
Generate favicons from a source image
Also in 3 projects that use this
madeehahassanSkillGo-Live
Pre-launch checklist. Use before making any app public, sharing a link externally, or announcing a product launch. Adapts to Claude Code, claude.ai, and Cowork.
Also in 3 projects that use this
JuliusBrusseeSkilldeepen
Optional design-improvement pass for when you have spare usage to drain. Finds the shallowest modules in the code the spec touches, researches a deeper design, and proposes refactors that shrink interfaces and hide decisions — behavior held constant, tests green before and after. Proposes §I/§V/§T edits, never silent rewrites. Triggers when the user says "deepen this", "improve the design", "this module feels shallow", "pull complexity down", "use spare budget on the codebase", or invokes /ck:deepen. Leans on the codebase-design skill's deep-module vocabulary when present.
Also in 3 projects that use this
synaptiaiSkillgate
Create a BDSK review_gate artifact. Defines a checkpoint that controls whether generated output may proceed toward acceptance. Use when defining quality, security, or scope gates for execution plans.
Also in 5 projects that use this
Other versions168 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 168
- FalkorDB/FalkorDB★ 11ksame name
- realsenseai/librealsense★ 9.1ksame name
- microsoft/microsoft-ui-xaml★ 8.6ksame name
- NexaAI/nexa-sdk★ 8.5ksame name
- hathach/tinyusb★ 7.3ksame name
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
- parcadei/Continuous-Claude-v3★ 3.9ksame name
- pytorch/TensorRT★ 3ksame name
- oxsecurity/megalinter★ 2.7ksame name
158 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architectureSkill
- audit-contentSkill
- benchmarkSkill
- break-itSkill
- challengeSkill
- code-reviewSkill
- compareSkill
- debug-ragSkill
- evaluateSkill
- explainSkill
- fixSkill
- glossarySkill
- journalSkill
- lessonSkill
- paper-reviewSkill
- quizSkill
- recapSkill
- roadmapSkill
- sandboxSkill
- startSkill
- triageSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 154 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
If the user specifies a component (e.g., /build chunker), use that.
- Very specific: line 32
Check if a project workspace exists in projects/.
- Distinctive: line 35
Create the file structure for the component.
- Distinctive: line 47
Keep each stage small and focused.
- Distinctive: line 61
Run the tests and verify correctness
- Very specific: line 76
Update progress/module-tracker.md to note the completed build exercise.
- Distinctive: line 87
If they get stuck, give increasingly specific hints rather than the solution
- Distinctive: line 90
Use real-world data examples when possible, not just "lorem ipsum"
“Common” is measured: kept by at least 6 in 10 of the 154 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Build: Hands-On RAG Component Construction
Scope: This skill provides step-by-step guided construction of individual RAG components. For open-ended, multi-component challenges that require design decisions, use
/challenge.
Guide the learner through building a real RAG component from scratch. This is the core hands-on skill — learners write actual code with step-by-step guidance.
Language awareness: See
.claude/LANGUAGE_AWARENESS.md.
Step 1: Choose What to Build
If the user specifies a component (e.g., /build chunker), use that. Otherwise, present the available components based on their track progress:
| Component | Difficulty | Prerequisites |
| Document loader | Beginner | Programming basics in your chosen language |
| Text chunker | Beginner | Module 1 |
| Embedding pipeline | Intermediate | Modules 1-2 |
| Vector store setup | Intermediate | Modules 1-3 |
| Retriever | Intermediate | Modules 1-4 |
| RAG chain | Intermediate | Modules 1-5 |
| Re-ranker | Advanced | Modules 1-6 |
| Evaluation harness | Advanced | Modules 1-7 |
| Full RAG pipeline | Advanced | Modules 1-8 |
Step 2: Set Up the Project
- Check if a project workspace exists in
projects/. If not, help the learner create one. - Explain the dependencies needed and help install them.
- Reference templates in
.claude/docs/templates/if available. - Create the file structure for the component.
Step 3: Guided Implementation
Walk through the build in clear stages. For each stage:
- Explain the goal of this stage — what are we building and why?
- Show the interface — what inputs does this piece take, what does it output?
- Let the learner write the code — provide the function signature and docstring, let them fill in the implementation.
- Review their code — check for correctness, efficiency, and best practices.
- Suggest improvements — offer one or two ways to make it better (error handling, performance, configurability).
Keep each stage small and focused. A chunker build might look like:
- Stage 1: Read a document into text
- Stage 2: Implement fixed-size chunking
- Stage 3: Add overlap between chunks
- Stage 4: Handle edge cases (empty docs, very short docs)
- Stage 5: Add metadata to chunks
For example, provide a skeleton in the learner's chosen language with the function signature, docstring/comments, and placeholder logic. Use idiomatic patterns for the language.
Step 4: Test the Component
Help the learner write tests for their component:
- Provide sample input data
- Define expected outputs
- Run the tests and verify correctness
- Discuss edge cases they should think about
Step 5: Integration Check
Explain how this component fits into the larger RAG pipeline. Show how it connects to the previous and next components in the chain. If the learner has already built other components, help them wire this one in.
Step 6: Review and Reflect
Summarize what was built:
- What the component does
- Key design decisions made
- What they learned
- Ideas for extending it further
Update progress/module-tracker.md to note the completed build exercise.
Suggest 2-3 relevant next steps using slash commands:
/evaluate— measure the quality of what you just built with RAG metrics/code-review— get expert feedback on your implementation/challenge— take on an open-ended challenge that combines multiple components
Guidelines
- Let the learner do the actual coding — guide, do not just provide the answer
- If they get stuck, give increasingly specific hints rather than the solution
- Celebrate working code — even simple implementations are achievements
- Point out common pitfalls specific to each component (e.g., chunk overlap calculations, embedding dimension mismatches)
- Use real-world data examples when possible, not just "lorem ipsum"
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
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.

