Meeting Insights Analyzer

What This Skill Does

The Meeting Insights Analyzer skill transforms meeting transcripts into actionable insights about communication patterns. It helps users become more effective communicators and leaders by identifying recurring behaviors, evaluating communication effectiveness, and providing specific feedback. This skill is useful for managers, team leads, and anyone looking to improve their communication skills.

When to Use

• Analyze communication patterns across meetings.
• Get feedback on leadership and facilitation style.
• Identify conflict avoidance in conversations.
• Understand speaking habits and filler words.
• Track improvement in communication skills.
• Prepare for performance reviews with concrete examples.

Key Features

• Recognizes recurring behaviors across meetings.
• Evaluates communication effectiveness.
• Provides specific, timestamped examples.
• Tracks communication trends over time.
• Analyzes clarity and directness.
• Identifies use of filler words.

This skill transforms your meeting transcripts into actionable insights about your communication patterns, helping you become a more effective communicator and leader.

When to Use This Skill

Analyzing your communication patterns across multiple meetings Getting feedback on your leadership and facilitation style Identifying when you avoid difficult conversations Understanding your speaking habits and filler words Tracking improvement in communication skills over time Preparing for performance reviews with concrete examples Coaching team members on their communication style

How to Use

Basic Setup

Download your meeting transcripts to a folder (e.g., ~/meetings/) Navigate to that folder in Claude Code Ask for the analysis you want

Quick Start Examples

Analyze all meetings in this folder and tell me when I avoided conflict.

Look at my meetings from the past month and identify my communication patterns.

Compare my facilitation style between these two meeting folders.

Advanced Analysis

Analyze all transcripts in this folder and: Identify when I interrupted others Calculate my speaking ratio Find moments I avoided giving direct feedback Track my use of filler words Show examples of good active listening

Instructions

When a user requests meeting analysis:

Discover Available Data

• Scan the folder for transcript files (.txt, .md, .vtt, .srt, .docx)
• Check if files contain speaker labels and timestamps
• Confirm the date range of meetings
• Identify the user's name/identifier in transcripts

Clarify Analysis Goals

If not specified, ask what they want to learn:

• Specific behaviors (conflict avoidance, interruptions, filler words)
• Communication effectiveness (clarity, directness, listening)
• Meeting facilitation skills
• Speaking patterns and ratios
• Growth areas for improvement

Analyze Patterns

For each requested insight:

Conflict Avoidance:

• Look for hedging language ("maybe", "kind of", "I think")
• Indirect phrasing instead of direct requests
• Changing subject when tension arises
• Agreeing without commitment ("yeah, but...")
• Not addressing obvious problems

Speaking Ratios:

• Calculate percentage of meeting spent speaking
• Count interruptions (by and of the user)
• Measure average speaking turn length
• Track question vs. statement ratios

Filler Words:

• Count "um", "uh", "like", "you know", "actually", etc.
• Note frequency per minute or per speaking turn
• Identify situations where they increase (nervous, uncertain)

Active Listening:

• Questions that reference others' previous points
• Paraphrasing or summarizing others' ideas
• Building on others' contributions
• Asking clarifying questions

Leadership & Facilitation:

• Decision-making approach (directive vs. collaborative)
• How disagreements are handled
• Inclusion of quieter participants
• Time management and agenda control
• Follow-up and action item clarity

Provide Specific

Examples

For each pattern found, include:

[Pattern Name]

Finding: [One-sentence summary of the pattern]

Frequency: [X times across Y meetings]

Examples:

1. [Meeting Name/Date] - [Timestamp]

   What Happened:

   [Actual quote from transcript]

   Why This Matters: [Explanation of the impact or missed opportunity]

   Better Approach: [Specific alternative phrasing or behavior]

[Repeat for 2-3 strongest examples]

Synthesize Insights

After analyzing all patterns, provide:

Meeting Insights Summary

Analysis Period: [Date range] Meetings Analyzed: [X meetings] Total Duration: [X hours]

Key Patterns Identified

1. [Primary Pattern]

• Observed: [What you saw]
• Impact: [Why it matters]
• Recommendation: [How to improve]

2. [Second Pattern]

[Same structure]

Communication Strengths

1. [Strength 1 with example]
2. [Strength 2 with example]
3. [Strength 3 with example]

Growth Opportunities

1. [Area 1]: [Specific, actionable advice]
2. [Area 2]: [Specific, actionable advice]
3. [Area 3]: [Specific, actionable advice]

Speaking Statistics

• Average speaking time: [X% of meeting]
• Questions asked: [X per meeting average]
• Filler words: [X per minute]
• Interruptions: [X given / Y received per meeting]

Next Steps

[3-5 concrete actions to improve communication]

Offer Follow-Up Options

• Track these same metrics in future meetings
• Deep dive into specific meetings or patterns
• Compare to industry benchmarks
• Create a personal communication development plan
• Generate a summary for performance reviews

Examples

Example 1: Conflict Avoidance Analysis (Inspired by Dan Shipper)

User: "I download all of my meeting recordings and put them in a folder. Tell me all the times I've subtly avoided conflict."

Output:

Conflict Avoidance Patterns

Found 23 instances across 15 meetings where you used indirect communication or avoided addressing tensions directly.

Pattern: Hedging on Critical Feedback

Frequency: 8 times across 7 meetings

Example 1: 1:1 with Sarah - 00:14:32

What Happened:

"So, I was thinking... maybe we could, like, potentially consider looking at the timeline again? I mean, if you think that makes sense. But whatever you think is best!"

Why This Matters: You needed to address that Sarah's project was behind schedule, but the hedging language ("maybe", "potentially", "if you think") and the deflection at the end ("whatever you think") made it easy for her to miss the urgency.

Better Approach: "Sarah, the project is two weeks behind schedule. We need to discuss what's blocking progress and create a new timeline today."

[Additional examples...]

Recommendations

Name the issue directly in the first sentence Remove hedging words like "maybe," "kind of," "sort of" Ask specific questions instead of hinting Schedule difficult conversations instead of raising them casually