CHRISTINE Your Best Sessions Shouldn't Vanish When the Call Ends
Call Replay turns any recorded session into a structured replay your team, clients, or members can learn from later — every insight kept, every participant protected. On the first run, it interviews you to wire itself to your recorder, your library, and your language.
← Back to the Skills LibraryInstalled in under a minute. No tech skills required.
You don't need to know how to code, and you don't need to set anything up. There are two blocks below. If you can copy and paste, you can install this.
Paste the instruction
Copy the first block and paste it into a brand-new Claude conversation. Don't hit send yet — it's the note that tells Claude what to do.
Paste the skill underneath, then send
Copy the full skill block and paste it right below the instruction. Send it. Claude builds the skill, personalizes it to your business, and confirms when it's ready.
Install the skill below for me. Keep the skill text exactly as written, then personalize its defaults from what you already know about me — my business, my voice, my priorities, and the places I keep my notes and files. Confirm when it's installed and show me exactly how to run it.
--- name: call-replay description: Turn any recorded coaching call, mastermind, or client session into a structured Call Replay your people can learn from later. On first run the skill interviews you to wire in your recorder, your library, and your language, then runs your version every time after. Use whenever you say "call replay," "run call replay," "replay this session," "process this call," or drop a recording and want the session captured. --- # Call Replay — Session Intelligence Capture Turn a recorded session into a structured Call Replay that lives wherever you keep your best material. Every replay is universalized, extracted for the gold, and written so anyone on your team or in your program can learn from it later. This is the gold from the session, structured for compounding. ## First Run: Design Your Version The first time you run this skill, set it up. Ask me these questions one at a time, save my answers into this skill file as a CONFIG block, and use them on every run after this. If the answers are already saved, skip straight to the workflow. 1. What do you use to record your calls? (Zoom, Fathom, Otter, Fireflies, Grain, or a transcript you paste.) This tells me how to get the transcript. 2. Where do you want each replay saved? (A Notion database, a Google Doc, a folder, a client portal, or back to you in the chat.) This is where the finished replay lands. 3. What do you call these sessions, and who are the replays for? (Your program or cohort name, and whether the reader is your team, your clients, or your members.) This sets the framing and the "you" the replay speaks to. 4. Do your sessions follow recurring themes? If yes, name them and I tag each replay with one. If no, I skip theme tagging. 5. Whose voice should the replay be written in, and are there any names or words to avoid? This keeps every replay on-brand and safe to share. If I ever say "redesign call replay," run this interview again. ## Input - A recording link or ID from the recorder you named in setup (I pull the transcript) - A pasted transcript - "Pull my most recent session" (I find the latest recording from your recorder) ## Workflow ### Step 1: Get the Transcript Pull the transcript from the recorder you set up, or use the one you paste. If your recorder also gives a summary, read it as a cross-reference. ### Step 2: Tag the Theme (only if you set themes) If you named recurring themes in setup, read the session and propose the dominant one. If the session spans several, pick the one it mostly lived in. If you skipped themes, skip this step. ### Step 3: Extract and Structure Read the full transcript. Produce the Call Replay using the exact format below. 1. First pass: read the entire transcript end to end. Note the major teaching moments, frameworks, quotable lines, and live builds. 2. Second pass: extract into the seven sections. Go deep. If the session had 8 key insights, extract all 8. 3. Third pass: universalize. Strip names and identifiers, keep the signal. ### Step 4: Present for Review Show the full Call Replay in the conversation. Do not save it until you approve. ### Step 5: Save It After approval, save the replay to the destination you set up, with the header fields set and the seven body sections as the content. ## The Call Replay Format ### Header Session Title, The One Big Idea (1-2 sentences), Theme (only if you use themes), Recording Link, Date Captured. ### Body (seven sections) 1. What Got Built. What came out of the session live: created, decided, installed, or shipped. Name the outputs. 2. Key Insights. Original ideas or frameworks worth stopping for. Bold headline, then 2-3 sentences. Go deep, extract all of them. 3. Quotable Moments. Exact phrases that carry weight on their own. Use the real words. Drop the attribution if the speaker was a participant. 4. Frameworks. Structured thinking and named methodologies. Bold name, numbered steps. Preserve names coined in the session. 5. Mindset Shifts. Where someone saw something differently, in from/to form. 6. Tactical Recommendations. Specific actions and tools discussed. Bold action, brief why. 7. Implementation Path. 3-5 honest moves someone could make this week, ordered by priority. If the session was a multi-week build, cover the first real step. ## Universalization Rules Every Call Replay is written for anyone who reads it later, not only the people on the call. - Strip the coach's own name and attribution. Write "the coach" or drop it. - Strip product and system names. Use generic equivalents (the program, the methodology, the knowledge base). - Anonymize every participant. Never a name, company, or identifiable industry. Use "a member," "someone in the room," "one of the founders." - Honor the names and words you asked me to avoid in setup. - Keep the signal: universally valuable quotes, framework names coined in the session, and specific tools, numbers, and data points that serve the teaching. ## Quality Standards Preserve the raw signal, do not editorialize. Go deep on every section. Prioritize specific and actionable over generic motivation. Anonymize completely. No fluff. The Implementation Path stays honest. ## Voice and Tone Write in the voice you set up in first run. Direct, clear, specific, action-oriented, written to the reader as "you." Never use: delve, unlock, craft, foster, tapestry, embarking, unleash, unveil, realm, boasts, revolutionize, tenets. No semicolons, no em dashes, no contrastive framing. ## Session Close After saving, confirm with a short receipt: session, theme if used, date, and where it landed. Then offer to pull the session's strongest quotes or a content angle if useful.
From then on, just drop in a recording and say "Run call replay."
Want to go further than skills?
Skills like this are how Christine runs her own business every day. In the Heart-Led AI Signature Group Coaching, she teaches you the whole system — live, in plain English, at your pace.
Explore Signature CoachingOne header. Seven sections. Every session, same shape.
A Call Replay isn't a loose summary — it's a fixed format, so every session in your library reads the same way. Here's what comes back:
1 · What Got Built
What came out of the session live: created, decided, installed, or shipped — with the outputs named.
2 · Key Insights
The original ideas worth stopping for, each with a bold headline and 2–3 sentences. If the session had 8, you get all 8.
3 · Quotable Moments
The exact phrases that carry weight on their own — the real words, not a paraphrase.
4 · Frameworks
Named methodologies broken into numbered steps — including names coined live in the session, preserved.
5 · Mindset Shifts
The moments someone saw something differently, captured in clean from → to form.
6 · Tactical Recommendations
The specific actions and tools discussed — each with a brief why.
7 · Implementation Path — plus the header
3–5 honest moves someone could make this week, ordered by priority. It all sits under a header with the session title, the One Big Idea in a sentence or two, the recording link, and the date captured — so every replay is findable later.
And the people on the call?
Every replay is universalized before it's saved: the coach's name stripped, product and system names swapped for generic equivalents, and every participant fully anonymized — never a name, company, or identifiable industry. The signal stays; the people stay protected. And nothing saves at all until you've reviewed the full replay and said yes.
Keep stacking: pairs beautifully with The War Room
Call Replay keeps the session for your library — a structured record your people learn from later. The War Room turns one call into a branded, interactive deliverable built to make the client who lived it feel seen.
Get The War Room →Because the recording folder is where sessions go to be forgotten.
The call was brilliant. Then the recording landed in a folder nobody reopens. This skill exists so the gold from every session gets captured, structured, and put where your people can actually learn from it.
It's wired to your tools on day one
The first run is a short interview: your recorder, where replays save, what you call your sessions, and whose voice they're written in. After that, every run is your version — and saying “redesign call replay” reopens the interview anytime.
Three passes beat one skim
It reads the full transcript end to end before extracting, then extracts section by section, then universalizes. That's why an eight-insight session produces eight insights — not the two easiest ones.
A fixed structure makes sessions teachable
Seven sections turn a winding 60-minute conversation into something a new team member or client can learn from months later. One replay is a nice note; a library of them compounds.
Universalized means safe to share
Because names, companies, and identifying details are stripped by rule — including any words you flagged in setup — the replay can live in your program library or portal without a second thought. The teaching travels; the people don't.
Nothing saves without your yes
The full replay shows up in the conversation for your review first. Only after you approve does it save to your destination — and it confirms with a short receipt of exactly where it landed.