Back to course overview
Module 7Insights, KPIs, and evaluation 30 min
Lab: Build an eval suite
Write ~10 evaluated questions, run them, then use the results to improve your prompt.
Outcome of this lab
An eval script that grades your agent on ~10 questions, and at least one prompt improvement you validated with it.
Step 1 — Write the cases
- 1Create eval.py inside the agent/ folder with the sys.path preamble from the lesson — that's what lets it import both the semantic layer and the AnalyticsAgent class no matter where you run it from.
- 2Write ~10 questions spanning lookups (total revenue), slices (revenue by region), rankings (top channel by CAC), and refusals (what's our NPS?).
- 3For factual ones, compute ground truth with the semantic layer so your answer key is always correct.
- 4For refusals, assert the reply admits it can't answer rather than containing a fabricated number.
Step 2 — Run and read the failures
- 1Run it —
python3 agent/eval.pyfrom the starter-kit root (venv active, ANTHROPIC_API_KEY set) — and note which cases fail. - 2Read the agent's actual replies on failures. Is it a formatting mismatch (right number, different format), a wrong metric choice, or a real error?
- 3Failures are information — they tell you exactly what to fix.
Step 3 — Improve and re-measure
- 1Pick the most common failure and address it in the system prompt (e.g. clarify a formatting rule, or add an example of the right metric to use).
- 2Re-run the eval. Did the score improve without breaking other cases?
- 3This measure → change → re-measure loop is how you improve any LLM system with confidence.
You now iterate like a pro
Most people tweak an AI prompt and 'feel' whether it's better. You can measure it. That discipline — an eval set backed by a trustworthy source of truth — is what separates a demo from a product. Your agent is ready to deploy.