Turn a meeting's raw record — a video/audio transcript, the notes someone typed during the call, or both — into a short summary plus a clear list of next steps with owners. Use this whenever the user shares meeting notes or a transcript and wants to know what was decided and what happens next, OR asks for "action items", "next steps", "follow-ups", "takeaways", "who's doing what", "recap this meeting", or "what did we agree on". Trigger even when the user doesn't say the word "meeting" — a pasted transcript with speaker labels, or notes that read like a discussion, is enough of a signal.
This skill is for anyone who runs or attends meetings and needs a fast, reliable recap afterward — team leads, project managers, founders, and individual contributors who don't want action items to slip through the cracks. It solves the common problem of a meeting producing a messy transcript or scattered notes that no one turns into usable follow-through.
It's aimed at people who share meeting records with an AI assistant and want to instantly know what was decided and who owns what next, without manually combing through verbose transcripts or reconstructing terse bullet notes.
When given a transcript, human-typed notes, or both, the skill reads the input (reading uploaded files first if needed), separates signal from filler, and produces two sections: a short Summary that catches up anyone who missed the meeting in under a minute, and a Next Steps checklist where each item has an explicit owner. It uses the transcript as the source of truth for what was said and notes as a hint for what mattered.
It assigns owners only when clearly indicated, marking others as Unassigned rather than guessing, and appends deadlines only when explicitly stated. It avoids padding the list with vague aspirations or dropped ideas, and honestly reports when no action items emerged. By default it replies directly in chat, but generates a downloadable .docx or .md file when the user explicitly asks for one.
### Summary This was a weekly product sync focused on the upcoming Q3 launch. The team agreed to push the beta release back one week to allow more QA time, confirmed the pricing page redesign is on track, and resolved an open question about which analytics provider to use. - Beta release moved from July 8 to July 15 due to outstanding QA issues - Pricing page redesign approved; design handoff to engineering this week - Decided to go with Mixpanel over Amplitude for launch analytics - Marketing to hold the announcement email until beta is confirmed stable ### Next Steps - [ ] **Priya** — Finalize the QA test plan for the beta build (by Friday) - [ ] **Marcus** — Hand off the approved pricing page designs to engineering - [ ] **Unassigned** — Set up the Mixpanel account and event tracking - [ ] **Dana** — Draft the launch announcement email and hold for beta sign-off - [ ] **Priya** — Send the updated launch timeline to stakeholders (before the Q3 review)
Passed SkillBazaar's automated review. Checks that ran:
AI-reviewed 7/4/2026
skillbazaar install meeting-next-steps --agent claudeSign in (free) to install skills with the CLI.
Author
@avamartinez