Meeting Notes Summariser

When to Use It

• You have just come out of a meeting and need to turn rough notes or a transcript into something you can share with the team
• You were in back-to-back meetings and need to process notes quickly before the details fade
• You want a consistent format for meeting summaries across your team so everyone knows where to find decisions and actions
• You need to send a follow-up to attendees that clearly captures what was decided and who is doing what
• You are preparing for the next meeting and want a clean record of what was agreed last time

What It Does

Takes raw meeting notes, a transcript, or bullet points — however rough — and structures them into a clean summary with four sections: a short meeting summary paragraph, decisions made organised by topic, an action items table with owner and deadline columns, and a proposed agenda for the next meeting based on open items.

How to Use It

Option A — For Claude users (via Skills)

1. Open the skill file on GitHub ↗ and download SKILL.md
2. Place the file in your Claude skills folder — ~/.claude/skills/meeting-notes-summariser/SKILL.md for personal use, or .claude/skills/meeting-notes-summariser/SKILL.md inside your project directory for project use
3. The skill will be available automatically in your next Claude conversation

Note: This applies to personal and project use. Enterprise and plugin setups have separate configuration — check with your administrator.

Option B — Copy and paste the instruction

1. Copy the full instruction from the section below
2. Open a new conversation in your preferred AI tool and paste it in
3. Paste your meeting notes or transcript — include the meeting subject, date, and attendees if you have them
4. Review the output before sending — check that action items and owners are correct

The Instruction

Copy the full text below and paste it into a new conversation.

You are an expert note-taker and meeting facilitator. I will give you raw meeting notes, a transcript, or bullet points from a meeting. Structure them into a clean, shareable summary using the format below.

First, extract the following details if present in the notes:

Meeting Details
- Subject:
- Date:
- Time:
- Attendees:

If any of these are not mentioned, write "Not mentioned" in the relevant field.

Then produce four sections:

Section 1 — Meeting Summary
Write 2–3 sentences summarising what the meeting was about and what was accomplished. Focus on outcomes, not a blow-by-blow account of the discussion.

Section 2 — Decisions Made
List the key decisions made in the meeting. Group them by topic if there are multiple distinct themes. Use a subtitle for each topic group and bullet points for the decisions under it.

Section 3 — Action Items
Present all action items as a table with four columns:

| Action | Owner | Deadline | Status |
|--------|-------|----------|--------|

- Action: what needs to be done, written as a clear task
- Owner: the person or team responsible (use the name from the notes, or "TBC" if not assigned)
- Deadline: the agreed date, or "TBC" if not mentioned
- Status: set all items to "Open" unless the notes indicate otherwise

Section 4 — Next Meeting
If a next meeting date or time was mentioned, include it here. Then list 2–4 proposed agenda items based on open action items or unresolved topics from the notes.

Important rules:
- Only include information that is present in the notes. Do not invent decisions, actions, or owners.
- If the notes are ambiguous about who owns an action, write "TBC" and flag it with a note: "Flagged for review: owner unclear."
- If the notes are too sparse to produce a meaningful summary, say so and ask for more detail rather than padding the output.
- Keep the language plain and direct. Write for someone who was not in the meeting.

Guardrails & Accuracy Checks

Built into this skill

• You only uses information present in the notes — it will not invent decisions, actions, or owners
• Ambiguous ownership is flagged explicitly with “Flagged for review:” rather than assigned arbitrarily
• If the notes are too sparse to work with, You will ask for more detail rather than producing a thin output

Before you send the summary, check

• Are all action items assigned to the right person? Misattributed actions are the most common error
• Are the deadlines accurate — or were they inferred? Verify any marked “TBC” before distributing
• Does the meeting summary reflect what actually mattered in the meeting, not just what was said?
• Did You flag anything for review? Resolve those before sending
• Are there decisions in the notes that did not make it into Section 2?

Example Output

This is an illustration of what Claude will return. Your actual output will reflect the notes you provide.