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.

“Can you write up notes from this meeting?”

Source material given with the request

Release sync, Tuesday Oct 27 2026, 10:00-10:30. Attendees: Hana Ito (PM), Sam Okafor (eng lead), Rui Costa (QA), Elif Demir (marketing) Hana: Plan is still to ship 3.2 this Friday, Oct 30. Sam: The export bug is fixed, merged last night. Rui: I found a crash on Android 12 when you rotate during export. Not fixed yet. Sam: That's maybe two days of work. Hana: Then Friday is too tight. Let's move the release to Tuesday Nov 3. Elif: Fine, I'll push the announcement email to Nov 3 as well. I'll update the schedule today. Sam: I'll have the Android fix in review by Thursday. Rui: I'll do a full regression pass Monday Nov 2. Hana: Open question from sales: do we ship the EU pricing page in 3.2 or 3.3? Nobody here can decide that, I'll ask Mona.
with the skill
## Meeting Summary **Date & Time**: Tuesday, October 27, 2026, 10:00–10:30 **Participants**: Hana Ito (PM), Sam Okafor (Engineering Lead), Rui Costa (QA), Elif Demir (Marketing) **Topic**: Version 3.2 release readiness and schedule ### Summary - **Release delayed**: We moved the 3.2 release from Friday, October 30, to Tuesday, November 3, to allow time to fix and test an Android crash. - **Export bug fixed**: The existing export bug was fixed and merged on October 26. - **Android crash still open**: Rui found a crash on Android 12 when the device is rotated during export. Sam estimates about two days of work. - **Marketing aligned**: The announcement email will move to November 3. - **Pricing page unresolved**: Sales asked whether the EU pricing page should ship in 3.2 or 3.3. Hana will ask Mona. ### Action Items | Due Date | Owner | Action | |----------|-------|--------| | October 27, 2026 | Elif Demir | Update the announcement email schedule to November 3. | | October 29, 2026 | Sam Okafor | Have the Android crash fix ready for review. |
Show the rest (15 more lines)
| November 2, 2026 | Rui Costa | Run a full regression test pass to check for problems across the product. | | Not specified | Hana Ito | Ask Mona whether the EU pricing page should ship in 3.2 or 3.3. | ### Decisions Made - Move the 3.2 release to Tuesday, November 3, 2026. - Move the announcement email to November 3, 2026. ### Open Questions - Should the EU pricing page ship in 3.2 or 3.3? Mona’s input is needed. --- **Suggested filename**: `Meeting-Summary-2026-10-27-Release-Sync.md`
without
# Release Sync — Meeting Notes **Date:** Tuesday, October 27, 2026, 10:00–10:30 **Attendees:** Hana Ito (PM), Sam Okafor (Engineering Lead), Rui Costa (QA), Elif Demir (Marketing) ## Decision - **Release 3.2 moved from Friday, October 30 to Tuesday, November 3** to allow time to fix an Android crash and complete regression testing. ## Status Updates - **Export bug:** Fixed and merged on October 26. - **Android 12 crash:** Rotating the device during export causes a crash. Not yet fixed; Sam estimates roughly two days of work. - **Marketing:** Announcement email will move to November 3 to align with the release. ## Action Items | Action | Owner | Due | |---|---|---| | Get the Android crash fix into review | Sam | Thursday, October 29 | | Complete a full regression pass | Rui | Monday, November 2 | | Update the announcement email schedule for November 3 | Elif | October 27 |
Show the rest (4 more lines)
| Ask Mona whether the EU pricing page should ship in 3.2 or 3.3 | Hana | Not specified | ## Open Question - **EU pricing page:** Should it ship in 3.2 or 3.3? No decision was made; Hana will consult Mona.

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.