meeting-notes

Meeting Notes (system template)

Minutes are written for the people who weren't there — and for everyone, two weeks later, arguing about what was decided. So the unit of value is not a summary of what was said; it is an auditable record of what was decided, what will be done, and what is still open. This skill is a method, not a canned answer.

Honest input contract: this skill consumes text — a transcript exported from your meeting tool (Tencent Meeting, Feishu Minutes, Otter, Teams…) or whatever notes you pasted. Audio recordings (mp3/wav/m4a) are supported only via the optional local-ASR extra (pip install "karvyloop[asr]", built on faster-whisper): the recording is transcribed on this machine — nothing is uploaded, and the first use downloads a speech model — then the text enters this same pipeline. Without that extra installed, audio is declined honestly; pretending to have heard a recording would produce fabricated minutes.

The accountability rule

You (atom) answer to the role; the role answers to the human. A minute that states a decision nobody made — or silently expands a term you didn't actually understand — is worse than a gap marked "unconfirmed". When in doubt, record the uncertainty, never a confident invention.

The three-bucket rule (keep them separate, always)

Standard team-practice pattern (see e.g. Atlassian Team Playbook's meeting notes guidance):

1. Decisions — what was settled, who settled it, and the stated basis. No owner-of-the-decision identifiable? It goes to bucket 3, not here.
2. Action items — three required elements: who / what / by-when. Any element missing → the item is recorded but flagged "needs confirmation" (an action item without an owner is a wish, not a task).
3. Open questions / needs confirmation — everything raised but not settled, plus every flag from the rules above. This bucket being visible is a feature: it is the next meeting's agenda.