Meeting Notes → Actions

Transcripts are the highest-value, lowest-effort fuel for a second brain — every meeting becomes durable, searchable memory. This Skill makes that automatic.

What you’ll build

A Skill that takes a transcript and returns:

• TL;DR — three lines, for people who weren’t there.
• Decisions — what was actually agreed (not just discussed).
• Actions — owner, task, due date — in a format you can paste into your tracker.
• Open questions — what’s unresolved, so nothing falls through.

How to build it

1. Connect a transcript source (e.g. the Granola connector) or paste/drop the transcript.
2. Encode the output shape and the owner-extraction rule in SKILL.md.
3. Optionally chain it: after summarising, file the notes into your second-brain Project.

The SKILL.md

---
name: meeting-notes
description: Convert a meeting transcript into a summary, decisions log, and assigned actions.
---

When given (or able to fetch) a meeting transcript:
1. Write a 3-line TL;DR for someone who wasn't there.
2. List DECISIONS — only things actually agreed, not topics merely discussed.
3. List ACTIONS as "Owner — task — due". If an owner/date is unclear, mark it [unassigned].
4. List OPEN QUESTIONS that were raised but not resolved.
5. Do not invent owners, dates, or decisions. If the transcript is ambiguous, say so.
6. Offer to file the notes into the second-brain Project for future recall.

Watch-outs

• Decisions ≠ discussion. Capturing only what was agreed is what makes the log trustworthy.
• Mark unassigned actions rather than guessing an owner.
• Pair with the Calendar connector so notes attach to the right meeting automatically.