Meeting Intelligence System skill
Analyze meeting transcripts to extract decisions, action items, blockers, sentiment, and generate follow-up emails.
by OneWave-AI·MIT license·GitHub ↗
★ 306 Stars on the repo·Checked
npx degit OneWave-AI/claude-skills/meeting-intelligence#main ~/.claude/skills/meeting-intelligenceFiles of Meeting Intelligence System
Files 1 file
Show the full text150 lines
Meeting Intelligence System
Transform meeting transcripts into actionable insights, decisions, and follow-ups.
When to Use This Skill
Activate when the user:
- Provides a meeting transcript or recording
- Asks to "analyze this meeting"
- Needs action items extracted from notes
- Wants to generate meeting minutes
- Asks for decisions made in a meeting
- Needs a follow-up email created
- Mentions meeting notes or transcripts
Instructions
Extract Meeting Metadata
- Identify meeting title/topic
- Note participants (if mentioned)
- Determine meeting date/time (if available)
- Identify meeting type (standup, planning, retrospective, etc.)
Identify Decisions Made
- Extract all explicit decisions
- Note who made each decision (if clear)
- Include rationale for decisions (if stated)
- Flag tentative decisions vs. final decisions
- Note decisions that need follow-up approval
Extract Action Items
- List all tasks assigned or volunteered
- Identify owner for each action item
- Note deadlines or timeframes mentioned
- Flag action items without clear owners
- Prioritize action items (if priority discussed)
- Note dependencies between action items
Identify Blockers and Risks
- Extract mentioned blockers
- Note risks or concerns raised
- Identify unresolved issues
- Flag items needing escalation
- Note resource constraints mentioned
Analyze Discussion Sentiment
- Gauge overall meeting tone (productive, tense, confused, aligned)
- Identify areas of agreement and disagreement
- Note team morale indicators
- Flag conflict or tension points
Extract Key Topics Discussed
- Summarize main discussion points
- Note questions raised
- Identify topics needing follow-up
- Highlight important context or background
Generate Follow-Up Communications
- Create meeting minutes/summary
- Draft action item tracking email
- Suggest calendar invites for follow-ups
- Recommend next steps
Output Format
# Meeting Summary: [Title]
**Date**: [Date] | **Participants**: [Names]
## Executive Summary
[2-3 sentence overview of meeting purpose and outcome]
## Decisions Made
1. **[Decision]**
- Owner: [Name]
- Rationale: [Why]
- Status: Final / Needs approval
## Action Items
| Priority | Action | Owner | Deadline | Status |
|----------|--------|-------|----------|--------|
| High | [Task] | [Name] | [Date] | Not started |
| Medium | [Task] | [Name] | [Date] | Not started |
## Blockers & Risks
1. **[Blocker]** - [Impact] - Needs: [Action]
2. **[Risk]** - [Mitigation plan]
## Key Discussion Points
- [Topic 1]: [Summary]
- [Topic 2]: [Summary]
## Open Questions
1. [Question] - Owner: [Who will answer]
## Sentiment Analysis
- **Overall Tone**: [productive/tense/etc.]
- **Team Alignment**: [high/medium/low]
- **Concerns Raised**: [Summary]
## Follow-Up Email Draft
Subject: Action Items from [Meeting Title] - [Date]
Hi team,
Thanks for joining today's [meeting type]. Here are our key outcomes:
**Decisions:**
- [Decision 1]
**Your Action Items:**
[Name]: [Task] by [Date]
**Blockers:**
- [Blocker] - please [action]
Next meeting: [Date/Time]
Best,
[Your name]
Examples
User: "Analyze this standup transcript" Response: Extract blockers mentioned → List action items per person → Flag impediments → Note team velocity concerns → Generate summary with focus on blockers
User: "Create action items from this product planning meeting" Response: Identify all decisions (feature prioritization) → Extract action items (design mockups, tech spec) → Assign owners → Set deadlines → Create tracking table → Draft follow-up email
Best Practices
- Be specific with action items (not vague "look into X")
- Always try to identify owners (flag if unclear)
- Differentiate between decisions and proposals
- Preserve important context for decisions
- Flag action items without deadlines
- Note commitments made by each participant
- Include relevant quotes for controversial decisions
- Use clear, scannable formatting
- Prioritize action items by urgency
- Flag dependencies between tasks
- Generate professional, actionable follow-up emails
| 1 | |
| 2 | name meeting-intelligence |
| 3 | description Analyze meeting transcripts to extract decisions, action items, blockers, sentiment, and generate follow-up emails. Use when user provides meeting notes, transcripts, or recordings and needs structured summaries or action tracking. |
| 4 | |
| 5 | |
| 6 | # Meeting Intelligence System |
| 7 | |
| 8 | Transform meeting transcripts into actionable insights, decisions, and follow-ups. |
| 9 | |
| 10 | ## When to Use This Skill |
| 11 | |
| 12 | Activate when the user: |
| 13 | Provides a meeting transcript or recording |
| 14 | Asks to "analyze this meeting" |
| 15 | Needs action items extracted from notes |
| 16 | Wants to generate meeting minutes |
| 17 | Asks for decisions made in a meeting |
| 18 | Needs a follow-up email created |
| 19 | Mentions meeting notes or transcripts |
| 20 | |
| 21 | ## Instructions |
| 22 | |
| 23 | **Extract Meeting Metadata** |
| 24 | Identify meeting title/topic |
| 25 | Note participants (if mentioned) |
| 26 | Determine meeting date/time (if available) |
| 27 | Identify meeting type (standup, planning, retrospective, etc.) |
| 28 | |
| 29 | **Identify Decisions Made** |
| 30 | Extract all explicit decisions |
| 31 | Note who made each decision (if clear) |
| 32 | Include rationale for decisions (if stated) |
| 33 | Flag tentative decisions vs. final decisions |
| 34 | Note decisions that need follow-up approval |
| 35 | |
| 36 | **Extract Action Items** |
| 37 | List all tasks assigned or volunteered |
| 38 | Identify owner for each action item |
| 39 | Note deadlines or timeframes mentioned |
| 40 | Flag action items without clear owners |
| 41 | Prioritize action items (if priority discussed) |
| 42 | Note dependencies between action items |
| 43 | |
| 44 | **Identify Blockers and Risks** |
| 45 | Extract mentioned blockers |
| 46 | Note risks or concerns raised |
| 47 | Identify unresolved issues |
| 48 | Flag items needing escalation |
| 49 | Note resource constraints mentioned |
| 50 | |
| 51 | **Analyze Discussion Sentiment** |
| 52 | Gauge overall meeting tone (productive, tense, confused, aligned) |
| 53 | Identify areas of agreement and disagreement |
| 54 | Note team morale indicators |
| 55 | Flag conflict or tension points |
| 56 | |
| 57 | **Extract Key Topics Discussed** |
| 58 | Summarize main discussion points |
| 59 | Note questions raised |
| 60 | Identify topics needing follow-up |
| 61 | Highlight important context or background |
| 62 | |
| 63 | **Generate Follow-Up Communications** |
| 64 | Create meeting minutes/summary |
| 65 | Draft action item tracking email |
| 66 | Suggest calendar invites for follow-ups |
| 67 | Recommend next steps |
| 68 | |
| 69 | ## Output Format |
| 70 | |
| 71 | |
| 72 | # Meeting Summary: [Title] |
| 73 | **Date**: [Date] | **Participants**: [Names] |
| 74 | |
| 75 | ## Executive Summary |
| 76 | [2-3 sentence overview of meeting purpose and outcome] |
| 77 | |
| 78 | ## Decisions Made |
| 79 | 1. **[Decision]** |
| 80 | - Owner: [Name] |
| 81 | - Rationale: [Why] |
| 82 | - Status: Final / Needs approval |
| 83 | |
| 84 | ## Action Items |
| 85 | | Priority | Action | Owner | Deadline | Status | |
| 86 | |----------|--------|-------|----------|--------| |
| 87 | | High | [Task] | [Name] | [Date] | Not started | |
| 88 | | Medium | [Task] | [Name] | [Date] | Not started | |
| 89 | |
| 90 | ## Blockers & Risks |
| 91 | 1. **[Blocker]** - [Impact] - Needs: [Action] |
| 92 | 2. **[Risk]** - [Mitigation plan] |
| 93 | |
| 94 | ## Key Discussion Points |
| 95 | - [Topic 1]: [Summary] |
| 96 | - [Topic 2]: [Summary] |
| 97 | |
| 98 | ## Open Questions |
| 99 | 1. [Question] - Owner: [Who will answer] |
| 100 | |
| 101 | ## Sentiment Analysis |
| 102 | - **Overall Tone**: [productive/tense/etc.] |
| 103 | - **Team Alignment**: [high/medium/low] |
| 104 | - **Concerns Raised**: [Summary] |
| 105 | |
| 106 | ## Follow-Up Email Draft |
| 107 | |
| 108 | Subject: Action Items from [Meeting Title] - [Date] |
| 109 | |
| 110 | Hi team, |
| 111 | |
| 112 | Thanks for joining today's [meeting type]. Here are our key outcomes: |
| 113 | |
| 114 | **Decisions:** |
| 115 | - [Decision 1] |
| 116 | |
| 117 | **Your Action Items:** |
| 118 | [Name]: [Task] by [Date] |
| 119 | |
| 120 | **Blockers:** |
| 121 | - [Blocker] - please [action] |
| 122 | |
| 123 | Next meeting: [Date/Time] |
| 124 | |
| 125 | Best, |
| 126 | [Your name] |
| 127 | |
| 128 | |
| 129 | ## Examples |
| 130 | |
| 131 | **User**: "Analyze this standup transcript" |
| 132 | **Response**: Extract blockers mentioned → List action items per person → Flag impediments → Note team velocity concerns → Generate summary with focus on blockers |
| 133 | |
| 134 | **User**: "Create action items from this product planning meeting" |
| 135 | **Response**: Identify all decisions (feature prioritization) → Extract action items (design mockups, tech spec) → Assign owners → Set deadlines → Create tracking table → Draft follow-up email |
| 136 | |
| 137 | ## Best Practices |
| 138 | |
| 139 | Be specific with action items (not vague "look into X") |
| 140 | Always try to identify owners (flag if unclear) |
| 141 | Differentiate between decisions and proposals |
| 142 | Preserve important context for decisions |
| 143 | Flag action items without deadlines |
| 144 | Note commitments made by each participant |
| 145 | Include relevant quotes for controversial decisions |
| 146 | Use clear, scannable formatting |
| 147 | Prioritize action items by urgency |
| 148 | Flag dependencies between tasks |
| 149 | Generate professional, actionable follow-up emails |
| 150 |
Discussion
Browse more free Claude skills.