agentleFS
TakaGotoTakaGoto/rag-learning-academy/.claude/skills/challenge/SKILL.md

challenge

Skill24 starsChanged 19 days agoMITView on GitHub

Take on a hands-on RAG challenge

34 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use prove-it, ingest and 8 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.
  • Neko-Catpital-LabsSkill

    prove-it

    Shared evidence rule for investigating, diagnosing, debugging, proving, or explaining what happened or why for any problem or situation: do not assert something is fixed, working, passing, merged, or running unless you personally observed it this turn and can show what you saw; do not assert it was caused by X until a repro and controlled isolation prove that cause.

    Also in 3 projects that use this

  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 4 projects that use this

  • GoogleSkill

    critique

    Expertise in auditing and fixing repository scripts and GitHub Actions workflows to ensure technical robustness and security.

    Also in 3 projects that use this

  • genomewalkerSkill

    learn

    Learn from web sources, generate SKILL.md, and store key patterns in soul memory. Trigger keywords: learn, skill-gen, web-learn, documentation, tutorial.

    Also in 4 projects that use this

  • Hugging FaceSkill

    implement

    Make tests pass. Invoke after /write-tests produces failing tests.

    Also in 5 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 30 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the user specifies a difficulty or topic (e.g., /challenge advanced or /challenge multilingual), filter accordingly.

    line 16
  2. Distinctive:

    Conversational RAG: Add conversation history to a RAG pipeline so follow-up questions work correctly (e.g., "What about the second one?").

    line 25
  3. Distinctive:

    Test queries and expected behavior

    line 48
  4. Distinctive:

    Do not build the solution for them.

    line 63
  5. Distinctive:

    When the learner says they are done, evaluate their solution:

    line 67
  6. Distinctive:

    Run the test queries and check the results

    line 71
  7. Distinctive:

    Keep time expectations reasonable: beginner (1-2 hours), intermediate (2-4 hours), advanced (4-8 hours)

    line 104

“Common” is measured: kept by at least 6 in 10 of the 30 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.

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

Challenge: Real-World RAG Challenges

Scope: This skill presents open-ended, multi-component challenges that require design decisions. For step-by-step guided construction of individual components, use /build.

Present the learner with a realistic RAG challenge that tests their skills across multiple components. Challenges are more open-ended than /build exercises — they require design decisions, not just implementation.

Language awareness: See .claude/LANGUAGE_AWARENESS.md.

Step 1: Select a Challenge

If the user specifies a difficulty or topic (e.g., /challenge advanced or /challenge multilingual), filter accordingly. Otherwise, recommend a challenge based on their progress.

Beginner Challenges

  1. FAQ Bot: Build a RAG system that answers questions from a FAQ document (provided). Must handle exact and paraphrased questions.
  2. Recipe Finder: Index a collection of recipes and build a retriever that finds recipes by ingredients, cuisine, or dietary restrictions.
  3. Book Q&A: Load a public-domain book, chunk it, and build a system that can answer questions about characters, plot, and themes.

Intermediate Challenges

  1. Multi-Document Synthesis: Build a RAG system that can answer questions requiring information from multiple documents. Test with a set of related articles.
  2. Conversational RAG: Add conversation history to a RAG pipeline so follow-up questions work correctly (e.g., "What about the second one?").
  3. Metadata-Filtered Search: Build a RAG system for product documentation where users can filter by product version, category, and date.
  4. Citation Generator: Build a RAG system that not only answers questions but provides exact source citations with page/paragraph references.

Advanced Challenges

  1. Multilingual RAG: Build a system that handles documents in multiple languages and queries in any of those languages.
  2. Legal Document Analyst: Build a RAG system for legal contracts that can answer questions about specific clauses, compare terms across contracts, and flag potential issues.
  3. Code Documentation Assistant: Build a RAG system over a codebase that can answer questions about architecture, find relevant functions, and explain code patterns.
  4. Real-Time RAG: Build a system that handles a continuously updating corpus (e.g., news articles) with minimal re-indexing latency.

Step 2: Present the Challenge

For the selected challenge, provide:

Challenge Brief

  • Objective: What the learner needs to build (1-2 sentences)
  • Requirements: Specific functional requirements (bulleted list)
  • Constraints: Any limitations (e.g., must use open-source models, latency under 2 seconds)
  • Evaluation criteria: How the solution will be judged

Provided Resources

  • Sample data or instructions for obtaining data
  • Suggested directory structure
  • Test queries and expected behavior

Show a deliverable example in the learner's chosen language with proper types, documentation, and structure.

Hints (available on request)

Prepare a set of progressive hints — do not reveal them unless the learner asks. Start with high-level guidance and get more specific.

Step 3: Support During the Challenge

While the learner works, be available to:

  • Answer clarifying questions about the requirements
  • Provide hints if they get stuck (but encourage them to try first)
  • Help debug specific technical issues
  • Discuss design trade-offs when they face a decision

Do not build the solution for them. Guide them to find the answer.

Step 4: Evaluate the Solution

When the learner says they are done, evaluate their solution:

Functionality Check

  • Does it meet all the stated requirements?
  • Run the test queries and check the results

Design Review

  • Is the architecture well-suited to the challenge?
  • Were chunking, embedding, and retrieval choices appropriate?
  • Is the prompt template effective?

Quality Assessment

Rate the solution on:

  • Correctness: Does it produce accurate answers? (1-5)
  • Robustness: Does it handle edge cases? (1-5)
  • Code quality: Is the code clean and well-organized? (1-5)
  • Design decisions: Were trade-offs made thoughtfully? (1-5)

Feedback

Provide specific feedback on what was done well and what could be improved. Suggest one stretch goal for extra credit.

Step 5: Track and Celebrate

Save the challenge completion to progress/challenges.md with the date, challenge name, difficulty, and score. If this is their first challenge at a given difficulty level, acknowledge the milestone.

Suggest 2-3 relevant next steps using slash commands:

  • /code-review — get expert feedback on the solution you just built
  • /evaluate — measure the quality of your challenge solution with RAG metrics
  • /roadmap — check your overall progress and see what to tackle next

Guidelines

  • Challenges should feel achievable but require real thought and effort
  • The learner should make design decisions, not just follow steps
  • Accept multiple valid approaches — there is rarely one right answer
  • Be encouraging throughout — challenges are meant to stretch, not discourage
  • Keep time expectations reasonable: beginner (1-2 hours), intermediate (2-4 hours), advanced (4-8 hours)

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.