How Coaches Can Use Claude Skills to Turn a Session Recording Into a Client Recap and Next-Step Plan

Warning: Only use this workflow if your client agreement and privacy setup allow it. If the session contains sensitive personal information, use an approved transcription and AI workflow or do not upload the session content.

If Claude Skills is new to you

Start with the Claude Skills explainer page in the site's Tools menu before you run this workflow. The short version is that Skills are reusable instruction bundles Claude can load for repeatable work. The public skills repository also makes good reference material when you want to copy the pattern into a private skill for your own team. For curated examples, see the Claude Skills tool hub and the Anthropic Workflows series.

Problem and who this is for

A strong coaching session creates momentum, but that momentum dies if the recap never gets sent. The challenge is that a session recording is too long to turn into a clean follow-up by hand every time. Claude Skills can help when you first turn the session into text, then run a repeatable recap format on top of it.

This workflow is for executive coaches, academic coaches, career coaches, and program mentors who want a consistent follow-up without rewriting the session from scratch.

Prerequisites

• Claude with Skills available.
• A transcript or strong same-day summary of the session. If you only have audio, create a transcript first with the recording or meeting tool you already use.
• A short note with the client's standing goals or current focus area.
• A decision on whether the recap is internal only, client-facing, or both.

How to gather the source material

1. If the session is already recorded, export the transcript from the tool that captured it, or create a rough transcript using your standard transcription workflow before opening Claude.
2. If no transcript exists, write a same-day summary while the session is fresh. Even a rough summary is better than waiting a week.
3. Save the transcript or summary as TXT, DOCX, or PDF.
4. Create one short file called client-goals.txt with the current focus areas, active commitments, and anything the client already agreed to before this session.
5. Remove any details you do not want in the final client-facing recap.

Numbered workflow steps

1) Separate session facts, reflections, and next-step commitments

The recap gets stronger when Claude first sorts the session into what was said, what matters, and what the client actually committed to. The internal-comms pattern is a good fit because it keeps the follow-up structured and concise.

{
  "task": "Extract a coaching recap structure from a session transcript or summary",
  "input": {
    "session_transcript_or_summary": "ATTACH OR PASTE",
    "client_goals": "PASTE client-goals.txt"
  },
  "rules": [
    "Use only what was said or clearly documented.",
    "Separate themes, commitments, and open questions.",
    "Mark any inferred action as [CHECK WITH CLIENT].",
    "Do not write the final email yet."
  ],
  "output": {
    "main_themes": "Major themes discussed",
    "client_commitments": "Specific next actions the client agreed to",
    "coach_observations": "Useful observations that belong in the recap",
    "open_questions": "Items still unresolved",
    "next_session_focus": "Likely focus for the next meeting"
  }
}

2) Review the extracted material before Claude writes the final deliverable

Review the commitments closely. This is where you remove anything that sounds like a coach suggestion rather than a client-owned action.

3) Draft the final deliverable

{
  "task": "Write a coaching session recap and next-step plan from verified session notes",
  "input": {
    "verified_session_structure": "PASTE THE REVIEWED OUTPUT FROM STEP 1",
    "audience": "client",
    "tone": "supportive, concrete, not overlong"
  },
  "rules": [
    "Keep the recap concise.",
    "Use headings for themes, commitments, and next focus.",
    "Do not over-interpret emotion or motivation.",
    "Keep client commitments in the client's own language when possible."
  ],
  "output_format": {
    "type": "client_recap"
  }
}

4) Save the output where you actually work

Keep the final deliverable in the same folder as the source package, or paste it into the system you already use. The value here is repeatability. Once your source files and section order are stable, the next run gets much faster.

Tool-specific instructions

Claude Skills is the right fit when you want every session follow-up to use the same structure without feeling robotic. The public internal-comms skill offers a solid pattern for short, reliable recap writing.

Quality checks

1. Every action item was truly discussed or agreed in the session.
2. The recap does not read like therapy notes, legal notes, or a full transcript.
3. The next-session focus follows from the actual conversation.
4. Private details that do not belong in a client-facing email are removed.

Common failure modes and fixes

The recap sounds too generic

Fix: require concrete commitments and one short quote or phrase from the session when helpful.

Claude invents action items

Fix: require every commitment to be traceable to the transcript or label it [CHECK WITH CLIENT].

The source is only audio

Fix: create a transcript or strong summary first. Do not skip that conversion step.

Sources Checked

• Anthropic Claude Help Center: What are Skills? (accessed 2026-03-23) https://support.claude.com/en/articles/12512176-what-are-skills
• Anthropic Claude Help Center: Use Skills in Claude (accessed 2026-03-23) https://support.claude.com/en/articles/12512180-use-skills-in-claude
• Anthropic Claude Help Center: Creating custom Skills (accessed 2026-03-23) https://support.claude.com/en/articles/12512198-creating-custom-skills
• GitHub: elliepetalmedia/skills README (accessed 2026-03-23) https://github.com/elliepetalmedia/skills
• GitHub: internal-comms skill in elliepetalmedia/skills (accessed 2026-03-23) https://github.com/elliepetalmedia/skills/tree/main/skills/internal-comms

Quarterly Refresh Flag

Review on 2026-06-21 to confirm any updates to Claude Skills, Claude Cowork, file handling, plan availability, and setup paths.