meeting
Installation
SKILL.md
Meeting
Core principle
A meeting summary is not a transcript. It's a decision log and a task list. The person reading it wasn't there — or was there but needs to act on it. Every line either records a decision, assigns work, or flags a risk. Nothing else earns a line.
Step 1: Understand what you have
Assess the input before writing anything:
- Transcript (full dialogue): extract signal, ignore filler
- Rough notes (bullets, shorthand, fragments): fill gaps with reasonable inference, flag anything uncertain
- Voice memo / stream of consciousness: restructure entirely, don't preserve the rambling order
Ask if unclear: "Is this a transcript, notes, or raw thoughts?" Then proceed.
Step 2: Identify the meeting type
The output shape changes by type: