---
name: meeting-transcript-synthesizer
description: Turn a raw meeting or call transcript into a clean, structured digest: summary, decisions, open questions, and themes. Use this skill whenever a user pastes or uploads a transcript, meeting recording notes, or a call dump and wants it summarized or organized, or says 'here is the transcript', 'clean up these notes', or 'what came out of this meeting'. Trigger whenever a long unstructured conversation capture needs to become something readable and useful.
---

# Meeting Transcript Synthesizer

## What this does and why it matters
Meetings generate value that evaporates the moment they end, because the record is a wall of raw transcript no one rereads. This skill compresses a transcript into a digest a reader absorbs in under a minute, while preserving the detail someone would need to act, so decisions and context survive the meeting.

## Inputs to gather
1. The transcript or raw notes.
2. The meeting purpose and, if not obvious, the participants.

## Method

### 1. Read fully before writing
Understand the whole conversation and its purpose before summarizing, so the summary reflects the meeting, not just the loudest part.

### 2. Write a summary that stands alone
Three to five sentences a person who missed the meeting could rely on. This is the most-used output, so make it genuinely sufficient.

### 3. Extract decisions as decisions
Separate what was decided from what was merely discussed. A decision buried in discussion gets lost and re-litigated.

### 4. Capture open questions
The unresolved points, so they are not forgotten between meetings.

### 5. Summarize the themes
The topics covered, each with one line of substance, so the digest is navigable.

### 6. Note commitments
Who said they would do what, where named. For a full accountable task list with owners and dates, hand off to the transcript-to-action-items skill.

## Output format
ALWAYS use:

# [Meeting Name] | [Date if known]
## Summary
## Decisions
## Open questions
## Key topics
## Notable quotes (optional, only if a verbatim line carries weight)

## Anti-patterns to avoid
- Inventing attendees, dates, or decisions the transcript does not support.
- Guessing who said what when the transcript is ambiguous (attribute to "a participant").
- A summary too vague to be useful to someone who missed the meeting.
- Long verbatim quotes instead of synthesis.

## Example
A messy 40-minute product call becomes a five-line summary, three clearly stated decisions, two open questions, and four topic lines, with one notable quote from the client preserved.