Facilitator Run-Sheets · Weeks 2–5

One page per week · print or save as PDF (⌘/Ctrl + P). ← Coach HQ

Facilitator Run-Sheet · Week 2 of 5

Building your first AI agent

≈ 2h 25m Deck: week-2 (press S for notes) · Notebook: Week 2 · DataFetcher · Energizer: The Human ReAct Loop

Before you start

ClockMinBlockSay / do — key cues
0:005Welcome"Last week AI talked; today it acts." Everyone into Colab + Coach HQ.
0:0515TheoryAgent anatomyPlan → Tools → Memory → Action · the ReAct loop (Reason+Act) · detective analogy.
0:2015TheoryKaggle ecosystemCompetitions · datasets · notebooks · public notebook = portfolio gold for internships.
0:3515⚡ EnergizerHuman ReAct LoopTeams of 4 act out the loop with tool cards. Round 1 guess → Round 2 loop. ✅ they feel chatbot vs agent
0:5020🛠️ PracticalEnvironment setupKaggle account · Colab orientation · imports (google-genai, pandas, requests) · key. ✅ setup test prints ✅
1:1040🛠️ PracticalDataFetcher buildTools (search_web mock + summarize_text) · the agent loop · task: latest AI-ed news → 3 bullets. ✅ agent calls tools, returns 3 bullets
1:5030🛠️ PracticalTitanic integrationpd.read_csv in one line · "average age by gender?" · preview Week 3. ✅ prints avg age by gender
2:205Wrap + homeworkExit: "4 parts of an agent?" Homework: explore a Getting-Started Kaggle comp + jot a project idea.

⏱ Behind?

Trim Titanic to a 15-min demo. Never cut the DataFetcher build — it's the payoff.

👀 Watch for

Key errors (stray space). If the agent answers with no tool call, re-run the config cell (system instruction dropped).
Facilitator Run-Sheet · Week 3 of 5

Data analysis agents & scoping

≈ 2h 22m Deck: week-3 · Notebook: Week 3 · DataExplainer · Energizer: Script or Agent?

Before you start

ClockMinBlockSay / do — key cues
0:005WelcomeRecap Week 2's agent loop. "Today: agents that reason over data — and you scope YOUR project."
0:0515TheoryDeterministic vs agenticScript = cheap/predictable; agent = flexible/pricier. Use the simplest thing that works.
0:2015TheorySMART scopingSpecific·Measurable·Achievable·Relevant·Time-bound · domains: edu assistant, sports analyzer, productivity.
0:3512⚡ EnergizerScript or Agent?Teams raise SCRIPT/AGENT paddle for task cards & defend. ✅ they justify with the trade-offs
0:4745🛠️ PracticalDataExplainer agent3 tools: describe_dataset · run_query · plot_chart. Challenges: women-first-class survival? · survival-by-class bar chart. ✅ agent answers + draws a chart
1:3245🛠️ PracticalProject design sprint1-min peer pitches · fill the charter (name/objective, 2-3 tools, data sources, outputs) · refinement circle. ✅ a finalized project plan each
2:175WrapExit: one sentence — "my project + its first tool." Next week = build it (hackathon).

⏱ Behind?

Shorten the DataExplainer challenges to one; protect the design sprint — a scoped project is the week's real output.

👀 Watch for

Over-ambitious project ideas — steer to SMART & small. plot_chart needs matplotlib imported.
Facilitator Run-Sheet · Week 4 of 5

Independent project (hackathon)

≈ 2h 23m Deck: week-4 · Notebook: Week 4 · Scaffold · Energizer: Bug Hunt

Before you start

ClockMinBlockSay / do — key cues
0:005Welcome"Today you build YOUR project on the scaffold. Build → debug → iterate."
0:0520TheoryDebugging agents3 failure types: hallucinations · tool errors · prompt issues · fixes: verify, validate inputs, tighten prompt, log every step.
0:2515⚡ EnergizerBug HuntTeams find & classify planted bugs in a transcript + one-line fixes. ✅ named the bug type for each
0:4030🏗️ Phase 1FoundationCore agent loop + first working tool + primary data source. ✅ one tool works end-to-end
1:1015Check-inPattern recognition2–3 students share progress · class solves one common integration challenge together.
1:2540🏗️ Phase 2ExpansionAdd a 2nd tool/data source · basic error handling (try/except + logging) · end-to-end workflow. ✅ 2 tools working
2:0515ClinicDebugging clinicPost top blockers · vote on 2 · script the fix together on the board.
2:203WrapHomework: reach MVP with 2 working tools. Office hours reminder.

⏱ Behind?

It's a hackathon — protect Phase 1 & 2 build time. Shorten the clinic, not the building.

👀 Watch for

Advanced kids → stretch goals (UI, multi-agent). Stuck kids → pre-built tool templates + pair programming.
Facilitator Run-Sheet · Week 5 of 5

Polishing & presentation

≈ 2h 25m Deck: week-5 · Notebook: Week 5 · Gradio & Publish · Energizer: 60-Second Hype

Before you start

ClockMinBlockSay / do — key cues
0:005Welcome"Today your project becomes a portfolio asset the world can see."
0:0520TheoryPathwaysFraming projects on résumés/college apps · skills companies seek (tool integration · decomposition · debugging) · internship search.
0:2515⚡ Energizer60-Second HypeRapid pitch warm-up + "I liked / I wondered." Round 1 silly product, Round 2 real project. ✅ everyone pitched once
0:4030✨ PracticalProduction polishComments & docs · a simple Gradio UI (or clean CLI) · peer testing in pairs. ✅ a UI a friend can use
1:1030📓 PracticalPublish to KaggleColab → Kaggle notebook · markdown storytelling · reproducible. ✅ a public notebook link
1:4040🎤 SlamPresentation slam3-min pitches (problem+design · demo · key learning) · "I liked / I wondered" · awards. ✅ everyone presented
2:205Wrap + awards 🏆Hand out award slips. Celebrate the 4 deliverables. "You're builders with a portfolio now."

⏱ Behind?

Keep the slam whole — it's the finale. Trim publishing to "start now, finish at home" if needed.

👀 Watch for

Gradio needs launch(share=True) for a public link. Keep pitches strictly to 3 min with a visible timer.