Skip to content
cccskills
FreePublished on GitHub

meeting-insights-analyzer

Analyze meeting transcripts to identify communication patterns, behavioral insights, and actionable feedback for improving communication and leadership effectiveness.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md7.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Meeting Insights Analyzer

Use This Skill When

  • Analyzing your communication patterns across multiple meetings
  • Getting feedback on leadership and facilitation style
  • Identifying avoidance of difficult conversations
  • Understanding speaking habits and verbal patterns
  • Tracking communication improvement over time
  • Preparing performance review examples
  • Coaching team members on communication

When NOT to Use

  • Analyzing others without their knowledge (privacy/ethics)
  • Real-time meeting coaching (need full transcript first)
  • Transcription assistance (focus is analysis)
  • Non-meeting communication (emails, messages)

Context: Communication Insight Maturity

Undeveloped: No feedback on patterns; unaware of habits.

Target: Identify recurring behaviors, conflict-avoidance patterns, speaking ratios.

Optimized: Trend tracking over months, peer benchmarking, predictive coaching recommendations.

Core Principle

Communication patterns are visible in transcripts. Systematic analysis of what you say (and don't say) reveals habits and opportunities for growth that are invisible in the moment but clear in data.

Instructions

Step 1: Gather Meeting Transcripts

Collect transcripts from meetings:

  • Download from Zoom, Google Meet, or Otter.ai
  • Format: Plain text with speaker labels and timestamps
  • Time period: Multiple meetings for pattern analysis (3-10 meetings minimum)

Transcript format:

[00:00:15] Sarah: Thanks for joining everyone. Let's start with Q2 goals.
[00:00:45] John: We're on track for most deliverables...
[00:01:20] Sarah: Great, any blockers?
[00:01:30] John: Not really, I think we're good.
[00:02:00] Sarah: Okay, moving on...

Step 2: Analyze Communication Patterns

Identify key metrics:

PatternHow to DetectSignificance
Speaking Ratio% of total words spokenDo you dominate or hide?
Turn-TakingHow often you speak vs. othersCollaborative vs. unbalanced?
Filler Words"Um", "like", "you know", "uh"Confidence, preparation level
Hedging Language"I think", "maybe", "possibly"Decisiveness, confidence
Questions AskedHow often vs. statementsActive listening, curiosity
Conflict EngagementHow you handle disagreementAssertiveness, conflict-avoidance
InterruptionsInstances of talking over othersRespect, impatience

Example analysis:

## Communication Pattern Analysis: Sarah

### Speaking Ratio
- Sarah: 32% of words (160 words / 500 total)
- John: 45%
- Maria: 23%

**Interpretation**: Balanced but slightly withdrawn. Team average: 33%.

### Turn-Taking
- Sarah: 14 turns
- John: 18 turns  
- Maria: 9 turns

**Interpretation**: You participate but don't dominate. Good balance.

### Filler Words
- Sarah: 8 instances ("um" x5, "like" x2, "you know" x1)
- Density: 5% of spoken words
- Benchmark: 2-3% is confident

**Interpretation**: Slight nervousness or lack of preparation.

### Hedging Language
- "I think": 6 times
- "Maybe": 2 times
- "Possibly": 1 time
- Total: 9 hedge phrases

**Interpretation**: Lack of conviction. Could be more direct.

### Questions Asked
- Sarah: 7 questions
- John: 3 questions
- Maria: 2 questions

**Interpretation**: Good active listening. Encouraging others to contribute.

### Conflict Engagement
- When John disagreed, Sarah said: "That's interesting, maybe we could..."
- Pattern: Avoidance language, doesn't directly address disagreement
- Red flag: No direct responses to challenges

**Interpretation**: Avoiding conflict. Room to be more direct.

Step 3: Identify Recurring Behaviors

Compare multiple meetings:

## Pattern Trends (3-Month Analysis)

### Consistent Patterns
- [ ] Speaking ratio consistently 30-35% (stable)
- [ ] Filler words appearing 5-7% (concerning, not improving)
- [ ] Hedging language present in 8-12 phrases per meeting (consistent)
- [ ] Asking 5-8 questions per meeting (consistent strength)

### Emerging Patterns  
- [ ] Interruptions increasing (0 → 2 per meeting) — watch this
- [ ] Conflict avoidance worsening (John's 2nd disagreement, Sarah changed subject)

### Improving Patterns
- [ ] Turn-taking becoming more balanced (was 40%, now 32%)
- [ ] Questions improving in quality (more follow-ups, fewer yes/no)

Step 4: Provide Timestamped Examples

Reference specific moments:

## Specific Behavioral Examples

### Example 1: Conflict Avoidance
**Timestamp**: [04:23-04:45]
**Situation**: John challenged your proposal
**Your Response**: "Hmm, yeah, that's a valid point. Maybe we could table this?"
**Pattern**: Avoids directly addressing concern; uses "maybe" hedge
**Impact**: Issue remains unresolved; John feels dismissed
**Alternative**: "I hear your concern about cost. Here's why I think ROI justifies it..."

### Example 2: Filler Words
**Timestamp**: [01:15-01:30]
**Your Words**: "Um, so like, I think we should, um, focus on the Q2 roadmap"
**Pattern**: 4 filler words in 15 seconds (27% rate!)
**Impact**: Reduces authority and clarity
**Alternative**: (pause) "I recommend we focus on the Q2 roadmap."

### Example 3: Strong Listening (Positive)
**Timestamp**: [06:00-06:30]
**Your Questions**: "What's your concern there?" (follow-up) "How would that affect timeline?"
**Pattern**: Natural curiosity, making others feel heard
**Impact**: Team more engaged; Sarah builds relationship
**Strength**: Keep doing this!

Step 5: Generate Actionable Feedback

Create improvement plan:

## Communication Improvement Plan

### Priority 1: Reduce Hedging Language
**Current**: "I think maybe we could possibly..."
**Goal**: Direct statements 80% of time
**Action**: 
- Before speaking, remove hedge phrases
- Practice: "We should...", "The best approach is..."
- Weekly reflection: How many direct statements this week?

### Priority 2: Address Conflict Directly
**Current**: Avoidance, topic-switching
**Goal**: Engage with disagreements, explore options
**Action**:
- Pause when disagreed with; ask clarifying question
- Respond with: "I see your point. Here's my perspective..."
- Practice script: "Let's explore both options..."

### Priority 3: Reduce Filler Words
**Current**: 5-7% filler word density
**Goal**: <2% filler words
**Action**:
- Pause instead of saying "um" or "like"
- Record yourself; play back and count
- Practice: Speak more slowly, articulate deliberately

### Priority 4: Continue (Strength)
**Keep**: Asking thoughtful questions, good turn-taking
**Action**: Model this for others; maybe help quiet team members

Step 6: Track Improvement Over Time

Weekly/monthly check-ins:

## Improvement Tracking (Weekly)

| Week | Hedge Phrases | Filler Words | Conflict Direct? | Questions Asked |
|------|---------------|--------------|-----------------|-----------------|
| Week 1 | 9 | 7% | No | 7 |
| Week 2 | 7 | 6% | Sometimes | 8 |
| Week 3 | 5 | 4% | Yes (1x) | 9 |
| Goal | <3 | <2% | Yes (consistently) | 7+ |

**Progress**: Trending in right direction! Continue focusing on conflict.

Output

Deliver:

  1. Communication Pattern Analysis (speaking ratios, filler words, hedging)
  2. Recurring Behavior Identification (trends across multiple meetings)
  3. Timestamped Examples (specific moments with context)
  4. Actionable Feedback (ranked priorities with concrete actions)
  5. Improvement Tracking (metrics and progress over time)
  6. Strengths Reinforcement (things to continue doing)

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Automate 21risk tasks via Rube MCP (Composio). Always search tools first for current schemas.

The English summary is being prepared. Showing the original description.

manu14357/zskills16Updated Jul 24, 2026

Automate 2chat tasks via Rube MCP (Composio). Always search tools first for current schemas.

The English summary is being prepared. Showing the original description.

manu14357/zskills16Updated Jul 24, 2026

Automate Ably tasks via Rube MCP (Composio). Always search tools first for current schemas.

The English summary is being prepared. Showing the original description.

manu14357/zskills16Updated Jul 24, 2026

Automate Abstract tasks via Rube MCP (Composio). Always search tools first for current schemas.

The English summary is being prepared. Showing the original description.

manu14357/zskills16Updated Jul 24, 2026

Automate Abuselpdb tasks via Rube MCP (Composio). Always search tools first for current schemas.

The English summary is being prepared. Showing the original description.

manu14357/zskills16Updated Jul 24, 2026

Automate Abyssale tasks via Rube MCP (Composio). Always search tools first for current schemas.

The English summary is being prepared. Showing the original description.

manu14357/zskills16Updated Jul 24, 2026

See all skills by manu14357

Report a problem with this skill