Summarize zoom recordings

Zoom meeting summary is an Agent Skill: a written method your AI applies on demand, in Zealos or in any client that reads SKILL.md.

A useful Zoom summary is not a compression of the transcript: it is the commitments, the decisions and the unresolved risks, written for someone who was not on the call.

What is in this skill

namecall-recap-format
descriptionThe structure of a good call recap: commitments, owners, dates, risks. Use when summarising a recorded call or meeting, or writing a follow-up that has to survive being forwarded.
allowed-toolsnone — this skill adds judgement, not reach
compatibilityZealos, Claude Code, Cursor, Codex and any client that reads SKILL.md
licenseFree to use and edit

How it works

  1. 1Lead with what was decided, or state plainly that nothing was. That single line is the most useful sentence in any summary.
  2. 2Extract commitments with owners and the dates that were actually spoken, marking any date you inferred as inferred.
  3. 3Record concerns that were raised and not resolved, even when the tone stayed friendly — an unresolved concern does not become resolved by politeness.
  4. 4Stay under two hundred words. A longer summary is padding, and padding is what stops people reading the next one.

The skill itself

---
name: call-recap-format
description: The structure of a good call recap: commitments, owners, dates, risks. Use when summarising a recorded call or meeting, or writing a follow-up that has to survive being forwarded.
---

# Call recap format

A recap is read by someone who was not on the call. Write for them.

## Structure

**One line up top:** what was decided, or that nothing was.

**Commitments** — the only section that always matters.
Each line: *who* · *what* · *by when*. Both sides. If a date was not said,
write "no date agreed" rather than inventing one.

**What we learned** — new facts only. Not a transcript. Three bullets is plenty.

**Risks and open questions** — what could kill this, and what we still do not
know. If a concern was raised and not resolved, it goes here even if the tone
was friendly.

**Next step** — one action, one owner, one date.

## Rules

- Quote the customer where the exact words matter (pricing, scope, timing).
- Separate what they said from what you concluded. Mark inferences as inferences.
- Do not soften bad news. A recap that reads better than the call did is worse
  than useless.
- If the call had no commitments, say that. It is the most important thing on
  the page.

## Length

Under 200 words. If it is longer, the call did not have that much in it and you
are padding.

Who uses it

Account executive

A colleague can pick up your deal from the summaries alone, which is what makes handover something other than a two-hour call.

Customer success

The QBR summary captures the complaint that was raised in passing at minute forty, rather than only the agenda items.

Founder

You can read what happened across six calls you did not attend in the time it used to take to watch one.

Frequently asked questions

How is this different from Zoom's own summary?

Zoom summarises the conversation. This defines what your team needs out of a call — commitments, owners, dates, unresolved risks — which is a different and shorter document.

Does it work with other recorders?

Yes. Avoma, Fathom and Gong all sync transcripts, and the skill describes the output rather than the source.

Can it log to the CRM too?

If the agent has CRM tools. Pair it with a field-conventions skill so the write follows your rules.

Related skills

Summarize calls and update the CRM

Post-call automation turns a recorded conversation into the three things that outlive it: the commitments each side made, the fields that changed, and the follow-up that has to go out today.

MeetingsCRMZoom/call-recap-format

Brief yourself before every call

A pre-call brief is worth writing only if it changes what you ask: who is in the room, what they are measured on, what happened last time, and the one question you cannot afford to leave without answering.

CoachingMeetingsAccounts/discovery-questions

Write a follow up that gets a reply

A follow-up gets a reply when it opens with the specific commitment made on the call, stays under 120 words, and asks for exactly one thing the recipient can answer in a sentence.

EmailGmailMeetings/email-rules

Score your sales calls automatically

Automatic call scoring is only fair if the rubric is visible: score the observable things — whether a next step was agreed, whether questions were about the past — and leave judgement to a human.

CoachingMeetingsZoom/discovery-questions

Run your after call workflow automatically

After-call work is the twenty minutes nobody books: the CRM update, the recap, the follow-up, the task for the thing you promised — and it is the first work to disappear on a busy day.

MeetingsCRMEmail/call-recap-format

Post a daily standup to slack

An automated standup is only read if it is short and specific: what moved, what is blocked, and what nobody has touched — with the last category being the one that justifies posting at all.

SlackMeetings/call-recap-format

Skills, in your workspace

Write it once. Every agent follows it.

Twelve built-in skills ship with every workspace, and you can draft your own with AI or import any public SKILL.md from GitHub.

7-day free trial. Set up in minutes. Cancel anytime.