Drop in a recorded coaching call, mastermind, or client session and get back a structured replay your people learn from later. On first run it wires into your recorder, your library, and your language, then runs your version every time after.
← All Claude SkillsYou run calls that are full of gold, and most of it disappears when the recording ends. This skill captures the gold into a structured replay anyone can learn from later. The first time you run it, it interviews you and designs itself into your world: your recorder, where you save things, what you call your sessions, and your voice. Every run after that, it just works. Copy the two blocks below and give them to your Claude.
Step 1. Copy the skill block below.
Step 2. Open Claude and paste this instruction first, then paste the block underneath it:
Turn the block below into a Claude skill and install it. Create the skill file exactly as written. Then personalize it with smart defaults from what you know about me: my business, my voice, my current priorities, and where I keep my work. Confirm when it is installed and tell me 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.
Claude reads the block, builds the skill file, and installs it. From then on, you just run the skill in any conversation. No folders to find, no code to write.
Every week you see what's working, build it live, and put it to work in your business.
Here's the shape of what this skill hands you when it runs. Copy it, use it, keep moving.
You don't need to hold any of this in your head. That's the skill's job. If you're curious what it's doing for you, here's the idea underneath it.
A great call is full of gold, and the moment the recording ends most of it starts to fade. The value was real. It just had nowhere to live. Call Replay gives it somewhere to live: seven sections anyone can read later and act on. A session becomes an asset.
The first time you run it, the skill interviews you and wires into your recorder, your library, your themes, and your voice. Every run after that just works.
What got built, key insights, quotable moments, frameworks, mindset shifts, tactical recommendations, and an honest implementation path. Every session read against all seven.
Names and identifiers come out, the signal stays. The replay reads for anyone on your team or in your program, well beyond the people who were on the call.
Each replay lands in the same place in the same shape, so your library grows into something searchable your people actually use.
Every replay ends with a few real moves someone could make this week, ordered by priority. Doable steps, grounded in what the session actually taught.
A Call Replay is a structured capture of the gold from a session, written so anyone can learn from it later without watching the recording. It pulls the session into seven sections: what got built, key insights, quotable moments, frameworks, mindset shifts, tactical recommendations, and an implementation path. A recording holds everything and asks you to sit through it. A replay holds the signal and hands it over ready to use.
The first time you run the skill it interviews you with five questions: what you record calls with, where you want replays saved, what you call your sessions and who they are for, whether you use recurring themes, and whose voice to write in. It saves your answers into the skill and uses them on every run after. Setup is a short conversation, so the skill fits your exact tools and language from the first run.
What Got Built, Key Insights, Quotable Moments, Frameworks, Mindset Shifts, Tactical Recommendations, and the Implementation Path. Each session gets read three times: once end to end, once to extract into the sections, and once to universalize so names and identifiers come out and the signal stays. The Implementation Path is honest, only the moves someone could make this week.