Podcast Research Folder
A structure for the work behind every episode. Guest research, episode briefs, question banks, post-show notes. Claude and ChatGPT prep interviews from real source material, not Wikipedia summaries.
Requires an AI connected to your Hjarni account via MCP.
Copy this URL and paste it into Claude or ChatGPT to install the template.
How to use
- 1 Share this page. Paste this URL into Claude or ChatGPT. Your AI reads the template definition and installs it.
- 2 Folders, tags, and instructions appear. Your AI creates the full structure in your Hjarni account, ready to use.
- 3 Start adding notes. The AI instructions guide your AI on where to put things and how to organize them.
The work behind every episode. Guest research, episode briefs, question banks, post-show notes.
Asking Claude to "prep an interview" produces a Wikipedia summary. Asking Claude to "prep an interview using my notes on this guest's last three essays" produces questions that earn the recording.
An episode brief format
Every brief follows the same shape: angle, three key questions, order.
# Episode <number>: <Topic>
Angle:
Three key questions:
Order:
Producer notes:
Sources keep the AI honest
The Sources folder is the antidote to invented quotes. Each note holds a real article, talk, or chapter, with key quotes and page numbers. When Claude drafts a question that references the guest's prior work, it cites the source note. If it cannot cite, it does not assert.
A workflow that earns the template's keep
- Book a guest. Write the Guest note. Save two or three Sources from their real work.
- Ask Claude or ChatGPT: "Draft an Episode Brief using my Guest and Source notes." Edit it.
- Record the episode.
- Write a Post-show note within 24 hours: what worked, what did not, carry-over.
A real example
You have a guest booked for next week. You ask Claude, "Draft three opening questions for this episode using my notes." Claude reads the Guest note, the Sources, and the Question Banks. It returns three questions, each anchored in a specific essay or talk. You pick one, rewrite one in your voice, drop one. The episode opens better than the average prep.
Common questions
Common questions
Does Hjarni do transcription or recording?
No. Hjarni stores the notes. Bring transcripts and recordings from whatever tool you already use.
Will the AI invent guest quotes?
Folder instructions tell each AI to never fabricate quotes and to cite by guest and year only when a Source note exists. If the source is missing, the AI asks.
Can my producer use the same folder?
Yes. Install in a team space so both your AIs read from the same guest research.
What if I record solo episodes?
Use the Episode Briefs and Sources folders. Skip Guests if you do not need it.
Related pages
Structure
Tags
Folders
For your AI
Share this page with your AI. It reads the definition below, creates the folders, instructions, tags, and starter notes in your account.
Show template definition
Install steps for AI agents:
- Check existing tags with
tags-list. Only create missing ones withtags-create. - Create containers top-down using
containers-create, noting the returned IDs. Useparent_idto build the hierarchy. - For each container with
llm_instructions, callinstructions-updatewithlevel: "container"and the container's ID. - Create any seed notes using
notes-create, placing them in the correct container by ID. Usecontainer_pathto resolve which container. - Discuss any customizations with the user before or after installing.
---
name: Podcast Research Folder
description: 'A structure for the work behind every episode. Guest research, episode
briefs, question banks, post-show notes. Claude and ChatGPT prep interviews from
real source material, not Wikipedia summaries.
'
tags:
- guest
- episode
- question
- post-show
- source
containers:
- name: Podcast Research Folder
description: Every episode's source material. Guest work, draft questions, post-show
notes.
llm_instructions: |
This is a podcast research system. The goal is to ground every episode in real source material from the guest's actual work.
- Before drafting interview questions, search the Guests and Sources folders. Cite the source by title and year when quoting a guest's prior work.
- Never invent quotes, episodes, dates, or facts about a guest. If the answer is not in the folder, say so plainly and ask the user for the source.
- When the user shares a new article, talk, paper, or interview from a guest, suggest saving it as a Source note linked to the Guest note.
- Treat Post-show notes as honest. Capture what worked and what did not, not just highlights.
- This is a research workspace, not a recording or publishing tool.
children:
- name: Guests
description: One note per current or past guest. Background, prior work, recurring
themes.
llm_instructions: |
Use this folder for guest backgrounds.
- One note per guest. Title is the guest's name.
- Include: Short biography, Main bodies of work, Recurring themes in their writing or talks, Why we are talking to them.
- When drafting questions, read this note first. Reference at least one specific piece from Main bodies of work.
- Tag every note with "guest".
- name: Episode Briefs
description: One note per episode. Angle, key questions, structure.
llm_instructions: |
Use this folder for the editorial plan for each episode.
- One note per episode. Title format: "Episode <number>: <topic>".
- Include: Angle, Three key questions, Order, Producer notes.
- Cross-link to the Guest note and to the Sources used.
- Tag every note with "episode".
- name: Question Banks
description: Recurring question patterns by theme. Reusable across guests.
llm_instructions: |
Use this folder for reusable interview patterns.
- One bank per theme. Title format: "Questions: <Theme>".
- Each question should include a one-line rationale for why it is interesting.
- Use these as raw material when drafting an Episode Brief. Pick three, edit them for the specific guest.
- Tag every note with "question".
- name: Sources
description: Direct material from a guest. Articles, talks, interviews, books.
llm_instructions: |
Use this folder for the source material itself.
- One note per source. Title format: "<Guest> <Year>: <Title>".
- Include: Citation, Summary in your words, Key quotes with timestamps or page numbers, Why it is interesting.
- Always cite by guest and year when referencing a source.
- Tag every note with "source".
- name: Post-show Notes
description: Honest notes from each episode. What worked, what did not.
llm_instructions: |
Use this folder for episode retrospectives.
- One note per episode. Title format: "Post-show <number>: <topic>".
- Include: What worked, What did not, Listener feedback, Guest feedback, Carry-over for next time.
- These notes are for the team. Be honest, not promotional.
- Tag every note with "post-show".
notes:
- title: 'PLACEHOLDER guest: shape of a guest note'
body: |
This is a placeholder guest note, not a real person. Replace the entire note with your first real guest before relying on it for prep.
## Short biography
Two or three sentences in your own words. Avoid attributing themes or claims to a real person until you have read their work directly.
## Main bodies of work
- List the specific pieces you have actually read or listened to. One bullet per piece.
## Recurring themes
- Only list themes you have seen the guest develop themselves, in writing or on the record. Do not paraphrase from secondhand summaries.
## Why we are talking to them
The angle the conversation is going to take, in one or two sentences.
Replace this entire placeholder before using the folder for real work.
tags:
- guest
container_path: Podcast Research Folder > Guests
- title: 'PLACEHOLDER episode brief: shape of a brief'
body: |
This is a placeholder episode brief. Replace it once you have a real guest note and at least one real source note linked.
## Angle
One or two sentences on the specific question this episode is going to answer. Tie it to the guest's actual work.
## Three key questions
1. A question that pulls a real story out of the guest, not a position statement.
2. A question that connects the guest's prior work to something current.
3. A question that turns the conversation forward into advice or prediction.
## Order
The intended arc of the episode in one or two lines.
## Producer notes
Reminders about pacing, references to save for the close, names to pronounce correctly.
Link to the real guest and source notes once they exist. Do not link to placeholder material.
Replace this entire placeholder before using the folder for real work.
tags:
- episode
container_path: Podcast Research Folder > Episode Briefs
- title: 'Questions: Community dynamics'
body: |
A starter question bank. Replace with your real reusable questions.
## "What marks the moment a community moves from early to stable?"
Rationale: surfaces the structural shift, not just the headcount.
## "Who in your work has the title but not the influence?"
Rationale: invites a real story rather than an abstract answer.
## "What would you do differently if you were starting that community today?"
Rationale: turns the historical lens forward.
## "What is the smallest event that changed the trajectory?"
Rationale: pulls a concrete moment out instead of a sweeping narrative.
This is a starter note. Replace it with your real question patterns.
tags:
- question
container_path: Podcast Research Folder > Question Banks
- title: 'PLACEHOLDER source: shape of a source note'
body: |
This is a placeholder source note, not a real piece of work. Replace it once you have a real article, talk, or book from a real guest.
## Citation
Last-name, F. (Year). Title. Publisher or platform.
## Summary
One paragraph in your own words. Do not paraphrase from a secondhand summary of the source.
## Key quotes
- Only include quotes you have personally verified, with a page number or timestamp.
- Do not invent quotes to flesh out the note.
## Why it is interesting
The single reason this source matters for the conversation you are planning.
Replace this entire placeholder before using the folder for real work.
tags:
- source
container_path: Podcast Research Folder > Sources
- title: 'PLACEHOLDER post-show: shape of a retrospective'
body: |
This is a placeholder post-show note. Replace with a real one after your first recorded episode.
## What worked
One or two specific moments that landed. Be concrete.
## What did not
Where the conversation stalled or stayed on the surface. Be honest, not promotional.
## Listener feedback
Direct quotes or themes from listener replies, once you have them.
## Guest feedback
What the guest said after recording. Note any follow-up commitments.
## Carry-over for next time
The one specific thing to do differently on the next episode.
Replace this entire placeholder before using the folder for real work.
tags:
- post-show
container_path: Podcast Research Folder > Post-show Notes