skills / business

summarize-meeting

what it does

Summarize a meeting transcript into structured notes with date, participants, topic, key decisions, summary points, and action items. Use when processing meeting recordings, creating meeting notes, writing meeting minutes, or recapping discussions.

Verified Before and after: 2 models 1 try per case View source Download .zip

Compare the answers

Answers from Claude Sonnet 5.5 and GPT-6.1 Sol · try 1 of 1

Same request, same model, once with the skill and once without. Read both and judge for yourself.

“Summarize this call and give me the action items.”

Source material given with the request

Onboarding redesign check-in, Oct 20 2026. Present: Grace Lund (design), Omar Haddad (PM), Tess Moreau (eng) Grace: Usability test results are in. 5 of 8 people got stuck on the workspace naming step. Omar: So we cut that step and auto-name the workspace. Agreed? Tess: Agreed, easy change. I'll ship it behind a flag by Oct 28. Grace: I'll update the Figma flow by Friday. Omar: Someone should also update the help center articles that show the old step. Tess: Yeah, definitely. Grace: Agreed. Omar: Okay, let's wrap.
with the skill
# Meeting Summary **Date & Time**: October 20, 2026 (start and end times not given) **Participants**: - Grace Lund (Design) - Omar Haddad (Product Manager) - Tess Moreau (Engineering) **Topic**: Onboarding redesign check-in **Summary** - **Test results**: The usability test results are in. 5 of 8 people got stuck on the workspace naming step. - **Fix**: We will remove the naming step and name the workspace automatically. - **Engineering**: Tess says this is an easy change. She will release it behind a flag (a switch that lets us turn the change on or off) by Oct 28. - **Design**: Grace will update the Figma flow (our design file) by Friday. - **Help center**: Some help articles still show the old naming step and need updating. Everyone agreed, but no one was named to do it. **Action Items**
Show the rest (19 more lines)
| Due Date | Owner | Action | |----------|-------|--------| | Fri, Oct 23, 2026 | Grace Lund | Update the Figma flow to remove the workspace naming step | | Oct 28, 2026 | Tess Moreau | Release the auto-naming change behind a flag | | **Not set** | **Not assigned** | Update the help center articles that show the old naming step | **Decisions Made** - We will cut the workspace naming step and auto-name workspaces instead. **Open Questions** - Who will update the help center articles, and by when? Tess said "definitely" and Grace said "agreed," but neither took it on. Omar may want to assign it so it doesn't get missed. - How will workspaces be auto-named (for example, from the user's name or email)? This wasn't discussed. - When will the flag be turned on for all users? Only the flag release date was set. --- **Notes:** - I assumed "Friday" means Oct 23, since the meeting was on Tuesday, Oct 20. - I can't save files here. If you want it saved, use the filename `Meeting-Summary-2026-10-20-Onboarding-Redesign-Check-in.md`.
without
## Summary **Onboarding redesign check-in, Oct 20, 2026** **Attendees:** Grace Lund (design), Omar Haddad (PM), Tess Moreau (eng) Usability testing showed that 5 of 8 participants got stuck on the workspace naming step. The team agreed to remove that step and auto-name new workspaces instead. ## Decisions - Cut the workspace naming step from onboarding and auto-name the workspace. ## Action Items | Owner | Task | Due | |---|---|---| | Tess Moreau | Ship the change behind a feature flag | Oct 28 | | Grace Lund | Update the Figma flow to remove the naming step | Friday (Oct 23) | | **Unassigned** | Update help center articles that show the old naming step | None set | ## Open Items / Flags - **The help center update has no owner or deadline.** Omar raised it, and Tess and Grace both agreed it should happen, but nobody took it. It's worth assigning explicitly, since it's likely to slip otherwise.
Show the rest (2 more lines)
- **Auto-naming logic wasn't discussed.** For example, whether it uses the user's name or email domain, and whether users can rename later. This may need a quick decision before Tess ships. - **Timing note:** the help center articles should ideally be updated to coincide with the flag rollout, not before it.

Answers are shown exactly as the model wrote them, from the first try, and nothing is picked by hand.

The models

2 models

Claude Sonnet 5.5

made by Anthropic

claude-sonnet-5-5 · revision not reported by the provider

1 try per case · tested 3 Nov 2026

GPT-6.1 Sol

made by OpenAI

gpt-6.1-sol · revision not reported by the provider

1 try per case · tested 3 Nov 2026

The tasks

written by Carte Blanche
customer-call-for-sales

“Summarize this customer call for the sales team. They weren't on it and aren't technical.”

reversed-release-date

“Can you write up notes from this meeting?”

standup-relative-dates

“Turn this standup into a short recap for Slack.”

unowned-task

“Summarize this call and give me the action items.”

unresolved-disagreement

“Write meeting notes for the people who couldn't make it.”

Install

Download the .zip and unzip it. Put its files, in a folder named summarize-meeting, here:

Claude Code~/.claude/skills/Every project. For one project only, use .claude/skills/ inside it.
Codex~/.agents/skills/Every project. For one repository only, use .agents/skills/ inside it.
Cursor~/.cursor/skills/Cursor also reads the Claude Code and Codex folders above.

Then start a new session and ask for what the skill does. Other agents that read SKILL.md have their own skills folder; check their docs.

Coming after launch: get skills from inside your agent, no download needed.