Meeting Insights Complete

A specialized skill for analyzing meeting transcripts to extract communication insights — covering speaking pattern analysis, action item extraction, decision tracking, sentiment analysis, and communication effectiveness metrics across meeting recordings.

When to Use This Skill

Choose Meeting Insights Complete when you need to:

• Analyze your communication patterns across multiple meetings
• Extract action items and decisions from meeting transcripts
• Identify speaking time distribution and participation balance
• Track decision-making patterns and follow-through rates
• Get coaching insights on presentation and facilitation skills

Consider alternatives when:

• You need live meeting transcription (use a transcription tool)
• You need meeting scheduling (use a calendar skill)
• You need presentation design (use a slides skill)

Quick Start

Copy
# Analyze a meeting transcript
claude "Analyze this meeting transcript for communication insights. Identify action items, decisions made, speaking time balance, and areas for improvement. [paste transcript]"

Copy
# Meeting Insights: Product Roadmap Review
**Date**: 2024-12-15 | **Duration**: 45 minutes
**Participants**: Alice (PM), Bob (Eng), Carol (Design), Dave (Data)

## Speaking Time Distribution
| Participant | Time    | Percentage | Role           |
|------------|---------|------------|----------------|
| Alice      | 18 min  | 40%        | Facilitator    |
| Bob        | 12 min  | 27%        | Primary contrib|
| Carol      | 9 min   | 20%        | Active         |
| Dave       | 6 min   | 13%        | Minimal        |

**Observation**: Dave spoke significantly less than others.
Consider directly soliciting input: "Dave, what does the
data tell us about this feature's usage?"

## Decisions Made
1. ✅ Ship auth redesign in Sprint 24 (owner: Bob)
2. ✅ Postpone mobile redesign to Q1 (owner: Alice)
3. ⚠️ Evaluate new analytics vendor (no owner assigned)

## Action Items
| Action                          | Owner | Due Date  | Status |
|--------------------------------|-------|-----------|--------|
| Write auth redesign RFC        | Bob   | Dec 20    | New    |
| Share Q1 roadmap draft         | Alice | Dec 18    | New    |
| Set up analytics vendor demos  | ???   | ???       | ⚠️ Unassigned |

## Communication Insights
- **Positive**: Clear agenda followed, decisions documented
- **Improve**: 2 action items lack owners or deadlines
- **Improve**: Dave's expertise in data wasn't leveraged
  for the analytics vendor decision

Core Concepts

Analysis Dimensions

Dimension	What It Measures	Insight Type
Speaking Balance	Time/word distribution per person	Participation equity
Decision Quality	Clarity of decisions, owner, deadline	Meeting effectiveness
Action Tracking	Items extracted with owners/dates	Follow-through
Topic Coverage	Time spent per agenda item	Meeting efficiency
Communication Style	Tone, clarity, collaboration level	Personal development

Pattern Recognition

Copy
## Communication Patterns to Track

### Facilitation Patterns
- **Inclusive**: "What does everyone think?"
  vs. "Alice, what's your take?"
  (Named solicitation is more effective)

- **Decision Making**: "Let's decide now"
  vs. "Let's take this offline"
  (Offline = often forgotten)

- **Time Management**: Time spent per topic
  vs. planned time (drift detection)

### Individual Patterns
- **Talking vs. Listening ratio**: Target 30/70 for facilitators
- **Question frequency**: More questions = better leadership
- **Interruption patterns**: Who interrupts whom?
- **Agreement signaling**: "That makes sense" without adding value

### Team Patterns
- **Groupthink indicators**: Too-quick unanimous agreement
- **Conflict avoidance**: Hard topics deferred repeatedly
- **Decision velocity**: Average time from discussion to decision

Action Item Extraction

Copy
## Identifying Action Items in Transcripts

### Explicit Actions
"Bob, can you write the RFC by Friday?"
→ Action: Write RFC | Owner: Bob | Due: Friday

### Implicit Actions
"We should probably look into that analytics tool."
→ Action: Evaluate analytics tool | Owner: ??? | Due: ???
(Flag as incomplete — needs owner and deadline)

### Distinguishing Actions from Discussions
"We talked about improving onboarding" = Discussion (no action)
"Alice will draft the new onboarding flow" = Action

### Action Completeness Checklist
Every action item needs:
- [ ] Specific deliverable (what exactly?)
- [ ] Owner (single person, not "the team")
- [ ] Deadline (specific date, not "soon")
- [ ] Success criteria (how do we know it's done?)

Configuration

Parameter	Description	Example
transcript	Meeting transcript text or file	Raw text or file path
analysis_depth	Level of analysis detail	"quick" / "detailed"
focus_areas	Specific insights to extract	["actions", "decisions"]
participant_list	Known participants for attribution	["Alice", "Bob"]
meeting_type	Type of meeting for context	"standup" / "roadmap"

Best Practices

1. Track decision follow-through across meetings — Extract decisions from each meeting and check in the next meeting whether they were executed. A team that makes 10 decisions per meeting but follows through on 3 has a follow-through problem, not a productivity problem.

2. Monitor speaking time distribution over multiple meetings — One meeting's imbalance might be situational. If the same person dominates speaking time across 5 consecutive meetings, it's a facilitation issue that needs intervention.

3. Flag action items without owners immediately — "We should look into X" without an owner never gets done. During analysis, highlight every action item that's missing an owner or deadline. Present these to the meeting facilitator as a specific improvement area.

4. Compare meeting duration to decision output — A 60-minute meeting that produces 1 decision is less efficient than a 30-minute meeting that produces 3 decisions. Track the decisions-per-minute ratio over time as a team health metric.

5. Use insights for coaching, not surveillance — Meeting analysis should help individuals improve their communication skills, not create a surveillance system. Share insights privately with individuals and aggregate data with teams.

Common Issues

Transcript quality is too poor for accurate analysis — Background noise, overlapping speech, and poor microphone placement produce unreliable transcripts. Recommend audio quality improvements: dedicated microphones, quiet rooms, and speaker identification at the start of meetings.

Action items are extracted but never tracked — Extracting action items is pointless without a follow-up system. Feed extracted actions into a project management tool (Linear, Jira, Asana) where they're assigned, dated, and tracked. Meeting notes that exist only in meeting notes get forgotten.

Analysis focuses on quantity over quality — Measuring who talked the most doesn't reveal who contributed the most. A 2-minute insight from a quiet participant can be more valuable than 15 minutes of repetition from a dominant speaker. Combine quantitative metrics with qualitative assessment.