Authorization notice. AI Engineer Notebooks is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Who it is forA backend engineer assigned a first document Q&A feature who needs to show it works before it ships.
The problemA plain model call invents answers about your documents, and a demo that looks right often fails on real questions.
The outcomeA working retrieve, augment, generate loop with a golden set of questions and a measured pass rate.
What you need first
- A Google account to open Colab notebooks
- A free Groq API key from console.groq.com (no credit card needed)
- The key saved as a Colab secret, as the setup notebook describes
- Basic Python and comfort reading API responses
Steps
- Open the setup notebook at 00-setup/00-environment.ipynb from the Colab badge and add your Groq key as a Colab secret.
- Run 03-rag/00-what-is-rag.ipynb to see the retrieve, augment, generate loop in about 15 lines.
- Work through 03-rag/01-embeddings-retrieval.ipynb until retrieval returns the right passages for your questions.
- Open 04-evals/01-golden-sets.ipynb and build a golden set of questions with expected answers for your RAG system.
- Run 03-rag/04-why-rag-fails.ipynb on any bad answers to find out whether retrieval or generation is the bottleneck.
Prompt for your agent
Using the repo calmrocks/ai-engineer-notebooks, work through 03-rag/00-what-is-rag.ipynb and 04-evals/01-golden-sets.ipynb against the documents in <placeholder folder>. Report the golden-set pass rate and list the three questions that failed. Verify that each failed answer is checked against the retrieved passages, not only the final text.
Caveat. The notebooks use the Groq API on Colab, so you will need your own free Groq key and a Google account before the first run.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page