meeting-noteslisted
Install: claude install-skill Kuan-AI-com/agent-skills
# Meeting notes
## Before writing
- Find the meeting date (transcript header, file name, or ask). You need it to turn "next Friday" into a date. Without it, keep the relative phrase in quotes.
- Identify speakers. If the transcript uses "Speaker 1/2" or labels are unreliable, keep those labels; never guess who said something.
- Transcripts from speech recognition mangle names, product names and numbers. When something looks misheard, keep it and mark it `[?]`.
## Output (exactly these sections, in this order)
**Summary**: up to 3 sentences: purpose of the meeting and what came out of it.
**Decisions**: only what was clearly agreed ("let's go with X", "agreed", no objection after a proposal by the person who owns it). A suggestion nobody confirmed is not a decision: put it in Open questions as "Proposed: ...".
**Action items**
| Task | Owner | Due | Source |
|---|---|---|---|
| Send revised quote to ACME | Maria | 2026-11-14 (said "Friday") | ~12:40 |
- Task starts with a verb and is specific enough to do without the transcript.
- Owner: the person who committed ("I'll do it") or was explicitly assigned. Otherwise `unassigned`.
- Due: only if said. Otherwise `no date`. Never invent one.
- Source: timestamp or a short quote, so it can be checked.
**Open questions**: raised but not resolved, with who raised them.
**Numbers and commitments** (only if any): prices, dates, quantities, promises to customers, quoted exactly.
## Rules
- Nothing that is not in the source. No