Meeting Notes Skill — Development skill for Claude Code

meeting-notes-skill

A [Claude Code](https://claude.com/claude-code) skill that turns messy meeting notes or transcripts into a structured summary: decisions, action items with owners and due dates, open questions, and formal minutes with motions and votes.

The main rule is **never invent anything**. A missing owner becomes `TBD`. An unclear date, an uncertain name or a point nobody agreed on goes under **Open questions** instead of being guessed.

What you get

Every summary uses the same sections, in the same order:

• Header: title, date, time and place, attendees, purpose
• Summary: 3 sentences at most
• Decisions: only what was actually agreed, with exact figures and dates
• Action items: a table with task, owner and due date (TBD if not stated)
• Key discussion points: grouped by topic, with opinions attributed ("Marco thinks…", not stated as fact)
• Open questions / to confirm: anything unresolved, unclear or contradictory
• Next steps: the next meeting and anything else coming up that isn't a task

For formal meetings, such as a board or committee, these optional sections are added when the notes contain them:

• Motions and votes: mover, seconder, voting method, count and result
• Quorum and approval of the previous minutes
• Carried-over items: status, plus old and new dates if a deadline moved
• Closed sessions: only that one took place, its times, who attended and any vote result

Highlights

• No guessing. Missing owners and dates become TBD, an owner who is only implied becomes "Name (to confirm)", and an uncertain spelling becomes "Geoff (spelling to confirm)".
• Careful with dates. "Friday" stays "Friday". A calendar date is added only when the meeting's full date (day, month and year) is known: "Friday (13 Nov 2026)".
• Keeps the original language. Greek notes give a Greek summary, with the headings translated too.
• Neutral and factual. The past tense for what happened, active