Decisions and actions from a recording or Teams transcript, as Word.
Say it in your own words. For example:
Turns a meeting recording or transcript into finished minutes in Word: decisions, actions with owners and deadlines, and the points discussed.
Meeting minutes as a finished Word file from a recording or a transcript: a meeting recording (m4a, mp3, wav, mp4 …, transcribed on our servers), a Teams, Zoom or Meet transcript (.vtt, .srt, .docx) or notes as text. One run gives the transcript by speaker; the next writes the minutes: date, attendees, minute-taker, summary, numbered decisions, an action table (what, who, due), the points discussed and the next meeting, in Danish or English, optionally on the company's letterhead, as PDF too, and the actions as an Excel sheet to track. Use for: write minutes from this Teams transcript, referat af mødet ud fra optagelsen, action items with owners and deadlines from the meeting, turn my meeting notes into proper minutes, beslutningsreferat. Triggers: minutes, meeting notes, referat, mødereferat, beslutningsreferat, action items, handlingspunkter, Teams transcript, recording of the meeting.
source Percerno · licence MIT
python3 /skills/meeting-minutes/scripts/minutes.py <verb> …. Inputs in /work/in, results in
/work/out. Prints OK … or ERROR ….
minutes.py read /work/in/meeting.vtt prints the transcript as Speaker: text (Teams and
Zoom speaker names kept, timestamps dropped) and the JSON shape to write. Works for .vtt, .srt,
.docx, .txt, .md, .pdf and recordings (.m4a, .mp3, .wav, .mp4, …, transcribed on our
servers at about real time: a recording over 3 minutes goes through start_job; add --lang da
when you know the language).cat > /work/minutes.json <<'EOF'
{"title": "Styregruppemøde, projekt Atlas", "date": "2026-10-29", "time": "09:00–09:30", "place": "Teams",
"attendees": ["Anna Berg (formand)", "Jonas Holm"], "absent": ["Mette"], "author": "Jonas Holm",
"summary": "Two to four sentences.",
"topics": [{"title": "Go-live", "notes": ["one line per point"], "decisions": ["Go-live moves to 8 December"]}],
"actions": [{"what": "Update the project plan", "who": "Jonas Holm", "due": "2026-10-30"}],
"next_meeting": "Wednesday 12 November 10:00, Teams"}
EOF
python3 /skills/meeting-minutes/scripts/minutes.py write /work/minutes.json /work/out/minutes.docx --pdf /work/out/minutes.pdf --actions /work/out/actions.xlsx
Rules for the JSON:
- Only what was said. A decision is something the meeting agreed; an action is something a named
person said they or someone else will do. No owner said: leave who empty (the OK line flags it).
- Turn relative dates ("on Friday", "next week") into dates from the meeting date; if the meeting
date is unknown, keep the words.
- Notes are short, factual lines, not a retelling; leave out small talk.
- Write in the language of the meeting (labels follow it; --lang da|en forces them).
| Need | Add to write |
|---|---|
| On the company's letterhead (headers, footers, logo, fonts kept; its body is replaced) | --template /work/in/letterhead.docx |
| PDF too | --pdf /work/out/minutes.pdf |
| Actions as an Excel sheet to track (status column, filter) | --actions /work/out/actions.xlsx |
If the company has its own minutes FORM (fields to fill rather than a letterhead), fill it with fill-template instead. Give the person the links, and say which actions have no owner or date.
SKILL.mdgate.jsonscripts/minutes.pyWritten by Percerno, MIT licence.