---
name: meeting-summarizer
description: "Summarize meeting content into structured notes with decisions and action items."
whenToUse: "User provides meeting transcript or notes to summarize"
---

# Skill: Meeting Summarizer

## Description
Summarize meeting content into structured notes with decisions, action items, and follow-ups. Works with meeting transcripts, chat logs, email threads, or verbal descriptions.

## When to Use
- User provides meeting transcript or notes to summarize
- User says "帮我整理会议纪要" or "summarize this meeting"
- User pastes a long chat/email thread and wants key points
- After reading Teams/Outlook content that contains meeting discussions

## Workflow

### 1. Input Sources
- Meeting transcript (text pasted by user)
- Teams chat history (read via `teams_read_messages`)
- Email thread (read via `outlook_read_content`)
- User's verbal description of what happened

### 2. Output Structure
```markdown
# Meeting Summary: [Meeting Name]
**Date:** [Date] | **Duration:** [if known]
**Attendees:** [List]

## Key Decisions
1. **[Decision]** — [Brief rationale]
2. **[Decision]** — [Brief rationale]

## Discussion Highlights
- [Topic 1]: [Key points, different viewpoints, conclusion]
- [Topic 2]: [Key points, different viewpoints, conclusion]

## Action Items
| # | Owner | Action | Due Date | Status |
|---|-------|--------|----------|--------|
| 1 | [Name] | [Task] | [Date] | Pending |
| 2 | [Name] | [Task] | [Date] | Pending |

## Open Questions
- [Question needing resolution] — Owner: [Name]

## Next Meeting
- [Date/time if scheduled]
- [Topics to cover]
```

### 3. Processing Rules
- **Decisions**: Extract only clearly agreed-upon outcomes, not suggestions
- **Action items**: Must have an owner and ideally a due date
- **Be concise**: Meeting was 1 hour? Summary should be < 1 page
- **Separate facts from opinions**: Note where there was disagreement
- **Prioritize**: Lead with decisions and actions, not discussion play-by-play
- **Language**: Match the language of the original content. If mixed, use the dominant language

### 4. For Long Transcripts
- First pass: Identify speakers and topic changes
- Second pass: Extract decisions and action items
- Third pass: Summarize discussion points
- Final: Organize into template

### 5. Distribution
After user approves:
- Send via email (`outlook_compose_email` or REST API with attachment)
- Post to Teams chat/channel (`teams_send_message`)
- Save as PDF (use create-pdf-report skill)
