meeting-notes

Meeting Notes

Purpose

This skill receives meeting notes in any structure and creates a structured summary with action items following an example.

Workflow

1. Read the input notes.
2. Create a structured summary following the output format below.
3. Invoke the /write-logs skill to log input, decisions, and output:

component: meeting-notes
type: skill
entries:
  - level: DEBUG
    message: "[RAW INPUT] <the raw input notes>"
  - level: INFO
    flag: --decision
    message: "Considered: <what you evaluated>. Chose: <approach>. Why: <reason>"
  - level: DEBUG
    message: "[OUTPUT] <the formatted summary>"

4. Return the structured summary as the final output.

---

Output format

1. Meeting title — pulled from the notes or inferred from the agenda
2. Attendees — listed as bullet points
3. Key discussion points — 2-4 sentences per topic, no more
4. Decisions — what was decided, stated as facts (e.g., "Team will use Postgres"). If no decisions were made, write "None."
5. Action items — table format:

Owner	Action	Due date
@name	What they agreed to do	YYYY-MM-DD

Rules

• Every action item MUST have an owner and a due date. If the notes don't specify, flag it as "TBD" — do not guess.
• Keep the summary under 300 words. If the meeting was long, prioritize decisions and action items over discussion points.
• Use the attendees' first names, not full names.
• Always include the Decisions section, even if empty.

Examples

Good action item

| @Sarah | Finalize vendor shortlist | 2026-04-18 |

Bad action item

| Team | Look into options | Soon |

---

Report

Return an estimation for how much time was saved using this skill vs hand-writing these notes.