Turn a call into a recap and a ready-to-send follow-up.
The decisions, the action items with owners and dates, the open questions, and a send-ready note.
Inside: The decisions, owned action items, and a drafted follow-up.
Install it in one line, or paste it in.
~/.claude/skills/ and runs automatically when it is relevant.Connect your context. Set it to your motion.
it reads the transcript automatically, no copy-paste.
pulls the account and deal context so the recap knows who is who.
drops the follow-up straight into a draft addressed to the room.
This was built for a B2B revenue team running customer and prospect calls. Set these to your stack:
Run any meeting type you like. The skill pulls decisions, owners, and open questions out of your own notes, so point it at your call, not anyone else's.
| Set this | What it is | Default / Example |
|---|---|---|
| MEETING source | where the call lives | a meeting toola transcriptyour notes |
| CRM | where the recap is logged | |
| EMAIL tool | where the follow-up is drafted | your mail clienta sequencing tool |
| OWNER format | how you name owners | first nameemail@handle |
| DUE default | when an undated action is due | before the next meeting (re-tune) |
| TONE | the voice of the follow-up | warm-professionalbriefformal |
| LOG target | where the summary is saved | the account or deal record |
Everything the skill does, in full.
Takes the mess of a call, notes, transcript, or your own scribbles, and turns it into four clean things: what was decided, who owns what by when, what is still open, and a follow-up note ready to send. It is the difference between a meeting that moves and a meeting that evaporates.
- 1Decisions
What the room actually agreed, stated plainly. A decision is a settled thing, not a topic that came up. If it was discussed but not decided, it belongs in open questions, not here. Do not manufacture agreement the notes do not show.
- 2Action items with owners
Every action gets an owner and a date. An action item with no owner is a wish, and one with no date never happens. If the notes name neither, flag it as unassigned rather than guessing who or when.
- 3Open questions
What is still unresolved, and what it is waiting on. This is the list that drives the next meeting. Naming an open question is how a deal or a project keeps moving between calls.
- 4The follow-up note
A note ready to send to the room: thanks, the decisions, the action items with owners, the open questions, and the next step. In your tone, short enough that people read it. This is the artifact that makes the meeting count.
- No decision that the notes do not support. A discussed topic is not a decision.
- Every action item has an owner and a date, or is clearly flagged unassigned.
- Owners are named, never "the team." An action everyone owns, no one owns.
- The follow-up is send-ready, not a rough draft the sender has to rebuild.
MEETING RECAP · Acme Corp · discovery call Decisions - Move to a 2-week trial on the two priority use cases. - Security review runs in parallel, not as a blocker. Action items - Send trial plan and success criteria owner: you by Wed - Loop in security for the review owner: Acme (Priya) by Fri - Book the mid-trial check-in owner: you by Thu Open questions - Who signs off on procurement? (waiting on Priya) - Budget confirmed for this quarter or next? Follow-up note (ready to send) Hi Priya, thanks for the time today. To recap: we agreed to a two-week trial on [use cases], with the security review running alongside. I will send the trial plan and success criteria by Wednesday and get a check-in on the calendar. Open on my side: who owns procurement sign-off. Talk soon.
The due default (before the next meeting) and the follow-up tone are defaults, not laws. They suited a fast B2B sales cycle. If your process runs on hard dates, set them explicitly. If your tone is more formal, change it. The logic does not change. The defaults are yours.
Where an operator takes this next.
The recap is step one. Here is where an operator takes it once the manual version proves out.
You built the recap once, now the follow-through gets tracked too.
Wire a scheduled Claude task to a meeting tool so the recap and send-ready email generate automatically within minutes of the call finishing.
Push owners and due dates into Salesforce or a task tool tied to the deal, so "send trial plan by Wed" shows up as a real task, not just a line in a doc.
Have a scheduled Claude task check unresolved open questions against the next meeting's notes and flag anything still open after two calls.
One skill is the on-ramp.
A single skill does one job. Chained into a playbook, or run as a full build, it becomes a system. Here is where this one plugs in.