Meeting Notes Claude Skill
Turn raw transcripts into a clean summary, key decisions, and action items with owners and dates.
A meeting-notes skill turns a messy transcript into notes people will actually read. This template gives Claude a fixed structure - a short summary, the key decisions, and action items with owners and due dates - so every meeting is documented the same way no matter who ran it. It separates decisions from discussion, attributes action items to specific people, and surfaces open questions that need follow-up. Define your format once and stop spending the first ten minutes after every call reconstructing what was agreed; paste the transcript and get a consistent, shareable record.
When to use this skill
- Converting a raw meeting transcript into structured notes.
- Capturing decisions and action items with clear owners.
- Standardizing how every meeting is documented across a team.
- Producing a shareable summary right after a call.
What it does
- Writes a concise summary of what was discussed.
- Separates and lists the key decisions made.
- Extracts action items with owners and due dates.
- Surfaces open questions and follow-ups.
The Meeting Notes Claude Skill SKILL.md
This is the complete, ready-to-use skill file. Copy it or download the .zip, then generate a customized version for your exact use case.
--- name: meeting-notes description: Turns raw meeting transcripts into structured notes - a concise summary, key decisions, action items with owners and due dates, and open questions. Use when the user shares a meeting transcript or notes, or asks to summarize a meeting. --- # Meeting Notes You convert a raw transcript into clean, structured notes a busy teammate can scan in 30 seconds. ## Output format **Summary** - 2–4 sentences on what the meeting covered and the outcome. **Decisions** - bullet list of decisions actually made (not topics discussed). If no decision was reached on something contentious, note it as unresolved. **Action items** - a table with: Owner, Action, Due date. Use the names mentioned in the transcript. If an owner or date is unclear, mark it `(unassigned)` or `(no date)` rather than guessing. **Open questions / follow-ups** - anything raised but not resolved. ## Rules - Distinguish decisions from discussion - only list something as a decision if the group actually committed to it. - Attribute action items to the specific person named; never invent an owner. - Keep it faithful to the transcript; don't add recommendations that weren't discussed. - Be concise. Cut filler, small talk, and repetition. ## Inputs to ask for (if missing) The transcript itself, and the list of attendees if names are ambiguous.
See the complete skill
You're viewing a preview. Sign up free to unlock the full SKILL.md — then copy it or download the ready-to-use .zip.
How to install this Claude Skill
- 1Download the skill and unzip the file.
- 2In Claude, go to Settings → Capabilities → Skills.
- 3Click Add Skill → Upload Skill.
- 4Drag and drop the .zip file to upload it.
- 5Once enabled, open the three-dot menu and choose “Try in chat.”
New to skills? Read the full guides on creating a Claude Skill and installing one.
Frequently asked questions
What does the Meeting Notes skill produce?
A consistent structure every time: a short summary, a list of decisions actually made, an action-item table with owners and due dates, and any open questions or follow-ups.
How does it handle unclear owners or dates?
It marks them as (unassigned) or (no date) rather than guessing, and it only attributes action items to people actually named in the transcript.
Does it work with raw, messy transcripts?
Yes - that's the point. Paste the raw transcript and it cuts the filler and small talk, separates decisions from discussion, and returns a clean, scannable record.
Related skills
Want a version tailored to you?
Describe your exact use case and generate a custom Claude Skill in seconds - free.
Generate your own