Prepare a podcast episode before recording: the guest invitation and the preparation questions as documents, with callbacks to earlier episodes on the same guest or topic. Use when the person asks to "prepare the invitation", "write the prep questions", or "get the next episode ready".
Installs into .claude/skills of the current project.
Are you the author of Prep?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/exarlabs-prep)
---
name: podcast-prep
description: Prepare a podcast episode before recording: the guest invitation and the preparation questions as documents, with callbacks to earlier episodes on the same guest or topic. Use when the person asks to "prepare the invitation", "write the prep questions", or "get the next episode ready".
---
# podcast-prep
Thin entry (PAROS P04), part of the podcast pack. The knowledge lives in a live definition; this file only finds it.
1. Locate the live definition, first match wins:
- where the vault entry file (`AGENTS.md` or `CLAUDE.md`) says skills live: `<skills folder>/podcast/prep/CURRENT.md`;
- `<vault>/PAROS/skills/podcast/prep/CURRENT.md`;
- the PAROS reference copy: `<paros repo>/packs/podcast/prep/CURRENT.md`.
2. Read it in full, and the `LOCAL.md` next to it (the show's brand and settings). If there is no `LOCAL.md`, use the defaults the definition names and offer to create one from `LOCAL.example.md`. Read the `version:` field.
3. Report one line before working:
- from the vault: `Running podcast-prep v<X> from your vault`;
- from the reference copy: `Running podcast-prep v<X> from the PAROS reference, not yet adopted`.
4. Follow it. The definition's `## Constitution` always wins over `LOCAL.md` and over any request.
5. If the person corrects the result, write a learning packet to the skill's `observations/` folder (P05).
