Behind the Build: AI Edition
The Program Feedback Audit Builder is on its way
Check your inbox in the next few minutes, that's where your skill file will be waiting (peek in promotions if it's hiding).
Built by Gail Starr
See what worked, what didn't and what to improve next round
Turn the calls, emails and feedback from your course or cohort into a clear plan for next time, using a source-grounded Gemini Notebook and the same audit prompts I used on my own live program.
  • A short interview about your course, cohort or group program
  • The right calls, feedback, emails and program materials to add
  • Step-by-step setup for a source-grounded Gemini Notebook
  • The analysis prompts I used to audit my own live program
  • Studio ideas for reports, mind maps, infographics and slide decks
Why this works
Your feedback is already telling you what needs attention. The hard part is seeing the pattern when it's spread across weeks of calls, emails and individual comments. Gemini Notebook brings those separate pieces together while keeping the analysis grounded in the program sources you choose, not outside opinions.
Your participant information stays in your notebook The skill guides you without ever asking you to paste participant names, recordings, transcripts or feedback in here. Individual prompts use [name] for you to fill in privately inside your own notebook.
1
Download the .skill file from the email
Save it somewhere easy to find on your computer, like your Downloads folder.
2
Open Claude
You can install skills in both the desktop app and the browser version.
3
Go to Customize → Skills
In the top menu.
4
Click the + button, then select Create Skill
A dropdown will appear. Choose Upload Skill.
5
Upload the file you downloaded
Pick program-feedback-audit-builder.skill. Claude will confirm when it's installed and ready.
6
Type: run the Program Feedback Audit Builder
In any session, any time. It'll ask you about your program and start from there.
You'll need at least a free Google account for Gemini Notebook
Formerly called NotebookLM. That's where your actual audit runs. The skill just guides the setup, the source choices and the prompts, it never opens or reads your notebook itself.
Keep the notebook to one program only
Nothing outside the calls, feedback and materials from the program you're auditing, and skip Discover Sources. The skill will remind you, but it matters. Grounded findings depend on a closed set of your own program's evidence, not outside research.
To Your AI-Powered Success Always,
Gail.
gailstarrdigital.com