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

If Claude Skills is new to you

Claude Skills are reusable folders that Claude can load when a task matches the Skill description. A custom Skill usually includes a Skill.md file with metadata, instructions, examples, and optional supporting files. Anthropic's current help says Skills are available on Free, Pro, Max, Team, and Enterprise plans when code execution is enabled.

For this workflow, you do not need a broad Skills setup guide first. You will create one private Skill, upload it in Claude under Customize > Skills, enable it, run a small trigger test, and then use it on a coaching transcript and goals note. The Claude Skills tool hub is useful further reading after this page's basic setup.

Problem and who this is for

A strong coaching session creates momentum, but that momentum fades 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. A custom Claude Skill helps by keeping your recap structure, commitment rules, tone, and next-step framing consistent.

This workflow is for executive coaches, academic coaches, career coaches, and program mentors who want a usable client recap and next-step plan from a session transcript. It is not a clinical note generator, legal record, or replacement for the coach's judgment.

What skill you will use in this workflow

You will build a private custom Skill called coaching-session-recap. The Skill tells Claude how to turn a session transcript and client goals note into a short recap, explicit client commitments, a next-step plan, and any coach follow-up items that were actually discussed.

This task is repetitive enough to deserve a Skill because many coaches want the same output shape after every session. The Skill can encode your recap sections, client-commitment rules, tone constraints, and guardrails against inventing promises. Before using it, prepare a transcript or same-day summary, a short client goals note, and your decision about whether the recap is client-facing or internal.

Prerequisites

• Claude with Skills available and code execution enabled.
• Client consent and an approved privacy setup for recording, transcription, and AI processing.
• A transcript or strong same-day summary of the session.
• A short note with the client's standing goals, current focus area, and active commitments.
• A decision on whether the recap is internal only, client-facing, or both.
• A final human review pass before the recap is saved or sent.

How to gather the source material

1. Confirm that the client agreement, consent language, and your privacy setup allow recording and AI-assisted recap drafting. If not, use handwritten or internal notes instead.
2. If the session is already recorded, export the transcript from the tool that captured it, or create a rough transcript using your approved transcription workflow before opening Claude.
3. If the workflow starts from a recorded call, interview, coaching session, or spoken source rather than clean digital text, Plaud can be a capture option. NotePin S is the better fit for coaching or on-the-go recording, while Note Pro is better for desk or room-based sessions.
4. If no transcript exists, write a same-day summary while the session is fresh. Even a rough summary is better than waiting a week.
5. Save the transcript or summary as TXT, DOCX, or PDF.
6. 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.
7. Remove sensitive details that do not belong in the final client-facing recap.

Build the custom skill for this workflow

Create a folder named coaching-session-recap. Inside it, create a file named Skill.md. Paste the starter content below into that file, then adjust it for your coaching niche, client language, recap style, and privacy rules.

After the folder is ready, zip the coaching-session-recap folder itself so the ZIP contains the skill folder at its root. Do not zip loose files by themselves. In Claude, go to Customize > Skills, upload the ZIP file, and enable the Skill. Then run the trigger test below before using it on a real client recap.

---
name: coaching-session-recap
description: Turn a coaching session transcript and client goals note into a recap, commitment list, and next-step plan without inventing decisions or promises.
---

# Coaching Session Recap

Use this skill when the user wants a structured coaching-session recap from a session transcript and a short note about the client's goals or coaching plan.

## What this skill should do
- Summarize what the client discussed in plain English.
- Extract any explicit commitments, decisions, or follow-up tasks.
- Draft a short next-step plan for the client.
- Keep tone supportive, clear, and non-clinical unless the coach explicitly wants another tone.

## Output shape
- Session recap
- Client commitments
- Next-step plan
- Coach follow-up items if present

## Guardrails
- Do not invent commitments or promises.
- Do not add diagnoses or therapeutic claims.
- Keep uncertainty visible if a commitment was implied but not explicit.
- Treat the output as a draft the coach reviews before sending.

## Examples
- Turn this coaching session transcript into a client recap and next-step plan.
- Use my coaching recap workflow on this session transcript and goals note.
- Draft the recap, commitments, and next steps without inventing follow-up promises.

Treat this as a starter template, not the final version. If your recaps always include a short opening note, a client-owned action list, or a next-session focus, add that wording to the Skill. If your work has compliance or privacy constraints, add those boundaries before using the Skill with real session material.

Skill-creator helper

Do not force a public Skill into this workflow. Anthropic's official skill-creator Skill can help draft or refine this private coaching recap Skill, especially the description, guardrails, and trigger examples. Keep your own client-specific structure and privacy language in the private Skill.

Why this should be a custom skill, not a one-off prompt

A one-off prompt can produce one recap, but coaching follow-up is recurring work. A Skill keeps the same sections, commitment rules, tone constraints, and no-invented-promises guardrail available every time. That lowers prompt rewriting and makes it easier to keep client recaps consistent without making them sound generic.

Skill trigger test

After enabling the Skill, test it with a short sample transcript or sanitized excerpt before the first production run. These prompts should cause Claude to use the coaching-session-recap Skill:

• Use my coaching recap workflow on this session transcript.
• Turn this recorded session into a client recap and next-step plan.
• Draft a recap with commitments and next steps, but do not invent promises.
• Use the coaching session recap Skill and mark implied commitments as uncertain.

If Claude does not appear to use the Skill, tighten the Skill description and test again with language that names coaching recap, session transcript, client commitments, and next-step plan.

Numbered workflow steps

1. Gather and clean the source material

Put the transcript or same-day summary, client-goals.txt, and any coach notes in one clean workspace. Remove details that do not belong in a client-facing recap. If the transcript includes small talk, unrelated personal details, or third-party information, trim that before asking Claude to draft anything.

Keep the transcript and goals note separate. The transcript is what happened in the session. The goals note is context for interpreting what matters.

2. Create or enable the custom Skill for this workflow

If this is your first run, build the coaching-session-recap folder, add the Skill.md file, zip the folder, upload it in Customize > Skills, and enable it. If you already built the Skill, confirm it is enabled before you start.

The Skill should encode recap structure, client commitments, next-step framing, and tone constraints. It should not encode promises you do not want Claude to make, such as guaranteed outcomes, therapeutic claims, or commitments the client did not actually make.

3. Run a quick trigger test

Use a sanitized excerpt or short sample transcript first. Try:

Use my coaching recap workflow on this session transcript. Draft a client recap, commitment list, and next-step plan. Do not invent promises.

Check that Claude uses the Skill structure, separates explicit commitments from implied ones, and keeps the tone supportive without sounding clinical. If the trigger test produces a generic summary, update the Skill description and examples before using it on a real client session.

4. Run the actual workflow with the Skill active

Attach or paste the full transcript or same-day summary, then add client-goals.txt. Ask Claude to use the coaching recap workflow and produce the recap sections from the Skill.

Use a prompt like:

Use the coaching-session-recap Skill on this transcript and goals note. Draft a client-facing recap with explicit commitments, next steps, and coach follow-up items only where the source supports them.

If the transcript is long, ask Claude to first identify the key session themes, commitments, and uncertain items, then draft the recap from that reviewed map.

5. Do a human review for accuracy, boundaries, and sensitive wording

Review the recap before saving or sending it. Confirm that every commitment was actually said or agreed, next steps are realistic, and coach follow-up items are not phrased as promises unless you intend to make them.

Also check sensitive phrasing. Remove diagnoses, therapeutic claims, overconfident interpretations of emotion, private details that do not belong in the recap, and anything that could pressure the client.

6. Save, send, or reuse the result

Paste the reviewed recap into your client notes, CRM, coaching portal, or email draft. Save the final version according to your privacy policy. After several runs, update the Skill with phrasing that consistently works, such as preferred section names, boundaries for client commitments, or the length of the next-step plan.

Tool-specific instructions

Use Claude Skills for the reusable parts of this workflow: recap structure, commitment extraction, next-step framing, tone, and guardrails against invented promises. The page-specific coaching-session-recap Skill should come first because coaching recaps depend heavily on your practice style and client agreement.

For broader setup context, see the Claude Skills hub. For help drafting or improving the private Skill, use Anthropic's official skill-creator as a helper, not as a replacement for your coaching recap Skill.

Quality checks

1. Every client commitment was truly discussed or agreed in the session.
2. Implied actions are marked as uncertain or moved into a question.
3. The recap does not read like therapy notes, legal notes, or a full transcript.
4. The next-step plan follows from the actual conversation.
5. Private details that do not belong in a client-facing recap are removed.
6. Coach follow-up items are phrased as real commitments only when you intend to own them.

Common failure modes and fixes

The recap sounds too generic

Fix: add your preferred recap headings, tone sample, and client-facing length target to the Skill.

Claude invents action items

Fix: add a stricter guardrail: "Every commitment must be traceable to the transcript or labeled [CHECK WITH CLIENT]."

The source is only audio

Fix: create a transcript or strong same-day summary first. Use Plaud, a meeting transcript, or your approved transcription process, but do not skip the conversion step.

The recap sounds too clinical

Fix: add tone rules to the Skill. For example: "Use coaching language, not therapy notes. Avoid diagnoses, treatment claims, or interpretations of mental state."

The Skill does not trigger

Fix: update the Skill description so it includes the exact phrases you use, such as "coaching recap," "session transcript," "client commitments," and "next-step plan." Then run the trigger test again.