AI WORKSHOP STUDIO · KYLE HOBSON

Run the 60-minute workshop

First session: Monday, September 14, 2026 · 10–11 a.m. America/Phoenix (17:00–18:00 UTC). Audience: Oppia research team and anyone in Oppia. Reuse the course and a fresh room with any organization. Larger follow-on session: date to be confirmed; October 5 is an optional planning suggestion, not a booking.

Before people arrive

Open the course and download the complete kit. Rehearse the skill in the exact app/account you will demonstrate. Check current UI labels against the linked official docs.
Choose Presenter on the entry screen and create a room. In Room settings, copy and save the private presenter link somewhere only you can access. Use Invite to copy the separate learner link for attendees. Returning presenters can resume a recent room on the same browser or paste their private presenter link. Rooms expire after 14 days.
Open the presentation tab. In Google Meet, select the presentation tab/window to share. Keep moderation on your own screen. No Meet plugin or polling subscription is required by this site.
Test a learner answer from a separate browser profile. Verify it stays off the presentation after approval. Click Broadcast approved answers to share it. Hide it again and check that it disappears. Check People to confirm that guest names and connection status appear only in your private workspace.
Prepare a plain chat fallback, a text editor and the offline handbook. Keep the worked example available if the model or network fails.

One activity at a time

Participants enter a code, optionally add a display name, and join without an account. They see a course welcome with learning goals and an agenda. A late joiner can read that welcome before selecting Join the current activity.
Use Start workshop, then Next activity. Choose an activity lets you jump to a course step or live question, or write a custom question. Participants follow your selection automatically. The opening sequence includes two AI basics screens before lesson 1. Show the course goals from the welcome, then give people time to find Agenda and Glossary. Give them a moment before advancing.
The shared presentation is independent. Show current activity sends a snapshot of that instruction or question to the audience. Next activity changes only participants’ pages; broadcast again when you want the shared screen to change.
In Responses, approve individual answers, then click Broadcast approved answers. New approvals stay private until you broadcast again. Hiding or editing a shared answer removes it; reapproving an edited answer still requires another broadcast. Clear screen gives the audience a quiet pause.
Use the text-view or pagination controls on the Presentation tab when needed. Long written answers are split into readable parts without dropping words. Word clouds group matching phrases and show response counts. Only shared answers are counted.
Participants can open Course agenda and Glossary throughout. They open Help, Files, or Notes within lessons when needed. Their notes stay private. An unsent live answer remains a draft in that browser tab when you change activities; returning to the question restores it.
If someone reloads, they reconnect to the current activity. A disconnected page can show the last received activity with a reconnecting notice. A learner can leave and browse independently at any time.

Timing and script

Include everyone

Say and display each instruction. Give a quiet minute to think before asking for responses. Participants can pass, type, speak, or pair.
Enable captions in your meeting tool if available. Read sample responses aloud. Use the presenter text-list option alongside word clouds.
Use the same fictional notes for everyone. Do not solicit personal or real participant data through public workshop answers.
For a larger group, ask a co-facilitator to handle setup and moderation using the private host link. The link grants full room control; share it only with that trusted facilitator.

When something goes wrong

Setup stalls: use browser chat or pair. At the time boundary continue the lesson.
Skill installation is unavailable: paste SKILL.md, run the tests, and record installation pending.
Model makes a false claim: ask which note supports it, then revise or delete the claim.
Live site or connection fails: ask people to keep answers in their workbook and use Meet chat or verbal sharing. Do not claim an answer was received without a receipt.
No one responds: give one minute of silent writing, offer a neutral sample answer, and invite a volunteer. Never seed a word cloud as if it came from attendees.
Time runs short: omit the optional visual tour and second shared-response discussion; use the supplied skill rather than authoring one from scratch. Retain the missing-input test and final source check. Reduce paired explanations to one minute total if necessary. Optional lessons remain independent study.

After the session

Export responses before deleting the room. Use Room settings to end the workshop and stop submissions, or delete the room to remove its answers and participant list. Review exit responses and decide which single lesson to improve. Progress and reaction polls are not proof of long-term learning.

One week later, optionally ask learners to share one checked artifact and what they changed. Use actual evidence of transfer, not just satisfaction.

Use with another organization

Create a fresh room with that organization’s name, keep the neutral fictional kit, and use the same lesson sequence. Replace the example only with material you have permission to use. The website runs independently of Google Meet and does not require a meeting integration.

Open Facilitator studio

Minute	Lesson	Facilitation
00–05	Welcome & AI basics	Say: “Today you will send and refine a prompt, check a brief against three notes, and test a reusable skill.” Open the agenda and show the six lessons (1 min). Explain generative AI and the need to check claims (1 min). Distinguish ChatGPT, Claude and Codex (1 min). Point out the persistent agenda, glossary and lesson support (1 min). Ask the arrival question and allow a quiet response (1 min). If everyone knows the terms, use that minute for practice rather than adding new topics.
05–14	Get set up	Show ChatGPT, New chat, message box and Send using the actual interface (2 min). Learners open the app or browser and the kit (2 min). Anyone blocked for three minutes moves to browser, partner or the worked example. Send the first prompt and follow-up (3 min). Check which control continues a conversation, confirm the setup rubric, and use the readiness poll to route support (2 min). This poll is a status check, not a scored learning question.
14–24	Write a useful prompt	Run a vague request using the fictional notes (2 min), demonstrate the bounded prompt (2 min), then let learners compare and revise a claim (4 min). Share one useful prompt change and discuss it (2 min). Use an existing draft if the model is slow.
24–33	Work with your files	Demonstrate attaching or selecting only the exercise files (2 min). Learners verify a passage and add one working preference (4 min). Check one source claim and discuss the access check (3 min).
33–47	Create and test a skill	Inspect SKILL.md (2 min), demonstrate the currently available creator and discovery route (3 min), and allow an installation or instruction-pasting attempt (3 min). Run the normal and missing-input tests (4 min). Review what failed and improve one boundary (2 min). Installation may remain pending; tested instructions are still useful.
47–53	Understand MCPs	Explain method versus access (2 min). Classify the three needs (2 min). Discuss the skill-versus-connector check (2 min). No account connection or server build is required during the core hour.
53–60	Check and take it with you	Inspect the brief against its sources (2 min). Explain one claim to a partner or in notes (2 min). Save/export and identify a next task (2 min). Exit response and close (1 min).