Meeting Insights Analyzer

Name: Meeting Insights Analyzer
Author: aiskillstore

aiskillstore/marketplace

1 installs
404 repo stars
Updated August 5, 2026
aiskillstore/marketplace

This is a copy of meeting-insights-analyzer by composiohq - installs and ranking accrue to the original listing.

meeting-insights-analyzer is a Claude Code skill that analyzes meeting transcripts to reveal communication patterns and give coaching feedback.

About

meeting-insights-analyzer is a Claude Code skill that reviews meeting transcripts to surface communication and leadership patterns. A user points it at a folder of transcripts and it identifies behaviors like conflict avoidance, filler words, and speaking ratios, then returns timestamped examples and coaching feedback. It can compare patterns across multiple meetings to track improvement over time.

Analyzes meeting transcripts (.txt, .md, .vtt, .srt, .docx) for communication patterns
Detects conflict avoidance, filler words, speaking ratios, and active listening
Returns timestamped examples with what happened, why it matters, and how to improve

Meeting Insights Analyzer by the numbers

1 all-time installs (skills.sh)
Data as of Aug 5, 2026 (Skillselion catalog sync)

At a glance

meeting-insights-analyzer capabilities & compatibility

Capabilities: transcript analysis · communication analysis · meeting summary
Use cases: transcription · data analysis
Pricing: Free

From the docs

What meeting-insights-analyzer says it does

Analyzes meeting transcripts and recordings to uncover behavioral patterns, communication insights, and actionable feedback.

SKILL.md

Scan the folder for transcript files (.txt, .md, .vtt, .srt, .docx)

SKILL.md

npx skills add https://github.com/aiskillstore/marketplace --skill meeting-insights-analyzer

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/aiskillstore/marketplace/meeting-insights-analyzer.svg)](https://skillselion.com/skills/aiskillstore/marketplace/meeting-insights-analyzer)

Installs	1
repo stars	★ 404
Last updated	August 5, 2026
Repository	aiskillstore/marketplace ↗

What it does

Analyze meeting transcripts to get feedback on your communication and facilitation patterns.

Who is it for?

Professionals wanting evidence-based feedback on their communication and facilitation across meetings.

Skip if: Producing formal meeting minutes or action-item lists (that is a different meeting skill).

When should I use this skill?

You want to analyze how you communicate across a set of meeting transcripts.

What you get

A timestamped, example-backed summary of your communication strengths and growth areas.

Meeting insights summary
Timestamped behavior examples
Speaking statistics

By the numbers

Reads 5 transcript formats (.txt, .md, .vtt, .srt, .docx)

Files

SKILL.mdMarkdownGitHub ↗

Meeting Insights Analyzer

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

What This Skill Does

1. Pattern Recognition: Identifies recurring behaviors across meetings like:

Conflict avoidance or indirect communication
Speaking ratios and turn-taking
Question-asking vs. statement-making patterns
Active listening indicators
Decision-making approaches

2. Communication Analysis: Evaluates communication effectiveness:

Clarity and directness
Use of filler words and hedging language
Tone and sentiment patterns
Meeting control and facilitation

3. Actionable Feedback: Provides specific, timestamped examples with:

What happened
Why it matters
How to improve

4. Trend Tracking: Compares patterns over time when analyzing multiple meetings

How to Use

Basic Setup

1. Download your meeting transcripts to a folder (e.g., ~/meetings/) 2. Navigate to that folder in Claude Code 3. 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:
1. Identify when I interrupted others
2. Calculate my speaking ratio
3. Find moments I avoided giving direct feedback
4. Track my use of filler words
5. Show examples of good active listening

Instructions

When a user requests meeting analysis:

1. 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

2. 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

3. 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

4. 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]

5. 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]

6. 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

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

Example 2: Leadership Facilitation

User: "Analyze my team meetings and tell me about my facilitation style."

Output: Provides insights on:

How much you speak vs. team members (60% vs. 40%)
Whether you ask questions or make statements (3:1 ratio)
How you handle disagreements (tendency to resolve too quickly)
Who speaks least and whether you draw them in
Examples of good and missed facilitation moments

Example 3: Personal Development Tracking

User: "Compare my meetings from Q1 vs. Q2 to see if I've improved my listening skills."

Output: Creates a comparative analysis showing:

Decrease in interruptions (8 per meeting → 3 per meeting)
Increase in clarifying questions (2 → 7 per meeting)
Improvement in building on others' ideas
Specific examples showing the difference
Remaining areas for growth

Setup Tips

Getting Meeting Transcripts

From Granola (free with Lenny's newsletter subscription):

Granola auto-transcribes your meetings
Export transcripts to a folder: [Instructions on how]
Point Claude Code to that folder

From Zoom:

Enable cloud recording with transcription
Download VTT or SRT files after meetings
Store in a dedicated folder

From Google Meet:

Use Google Docs auto-transcription
Save transcript docs to a folder
Download as .txt files or give Claude Code access

From Fireflies.ai, Otter.ai, etc.:

Export transcripts in bulk
Store in a local folder
Run analysis on the folder

Best Practices

1. Consistent naming: Use YYYY-MM-DD - Meeting Name.txt format 2. Regular analysis: Review monthly or quarterly for trends 3. Specific queries: Ask about one behavior at a time for depth 4. Privacy: Keep sensitive meeting data local 5. Action-oriented: Focus on one improvement area at a time

Common Analysis Requests

"When do I avoid difficult conversations?"
"How often do I interrupt others?"
"What's my speaking vs. listening ratio?"
"Do I ask good questions?"
"How do I handle disagreement?"
"Am I inclusive of all voices?"
"Do I use too many filler words?"
"How clear are my action items?"
"Do I stay on agenda or get sidetracked?"
"How has my communication changed over time?"

Related Use Cases

Creating a personal development plan from insights
Preparing performance review materials with examples
Coaching direct reports on their communication
Analyzing customer calls for sales or support patterns
Studying negotiation tactics and outcomes

{
  "schema_version": "2.0",
  "meta": {
    "generated_at": "2026-01-16T13:21:58.071Z",
    "slug": "89jobrien-meeting-insights-analyzer",
    "source_url": "https://github.com/89jobrien/steve/tree/main/steve/skills/meeting-insights-analyzer",
    "source_ref": "main",
    "model": "claude",
    "analysis_version": "3.0.0",
    "source_type": "community",
    "content_hash": "82435fd87eaa06bba0267988313bf19e12f45079b7a8ac9bccc4e9c64ec20b6e",
    "tree_hash": "52a7c4fa9c5402cdb983f98961aee17a4bf63e548f0c1ddff63aef9b4d7734ca"
  },
  "skill": {
    "name": "meeting-insights-analyzer",
    "description": "Analyzes meeting transcripts and recordings to uncover behavioral patterns, communication insights, and actionable feedback. Identifies when you avoid conflict, use filler words, dominate conversations, or miss opportunities to listen. Perfect for professionals seeking to improve their communication and leadership skills.",
    "summary": "Analyzes meeting transcripts and recordings to uncover behavioral patterns, communication insights, ...",
    "icon": "💬",
    "version": "1.0.1",
    "author": "Joseph OBrien",
    "license": "proprietary",
    "category": "communication",
    "tags": [
      "meetings",
      "communication",
      "productivity",
      "leadership",
      "feedback"
    ],
    "supported_tools": [
      "claude",
      "codex",
      "claude-code"
    ],
    "risk_factors": [
      "network",
      "external_commands"
    ]
  },
  "security_audit": {
    "risk_level": "safe",
    "is_blocked": false,
    "safe_to_publish": true,
    "summary": "This is a pure prompt-based documentation skill. It contains NO executable code, NO network calls, NO external commands, and NO environment variable access. All 33 static findings are false positives: the scanner misidentified markdown code block delimiters (```) as shell backticks, GitHub URLs and JSON hash values as cryptographic threats, and common words like 'identify'/'discover' as reconnaissance terms. The skill only provides behavioral guidance for AI-powered meeting transcript analysis.",
    "risk_factor_evidence": [
      {
        "factor": "network",
        "evidence": [
          {
            "file": "skill-report.json",
            "line_start": 6,
            "line_end": 6
          }
        ]
      },
      {
        "factor": "external_commands",
        "evidence": [
          {
            "file": "SKILL.md",
            "line_start": 55,
            "line_end": 55
          },
          {
            "file": "SKILL.md",
            "line_start": 61,
            "line_end": 63
          },
          {
            "file": "SKILL.md",
            "line_start": 63,
            "line_end": 65
          },
          {
            "file": "SKILL.md",
            "line_start": 65,
            "line_end": 67
          },
          {
            "file": "SKILL.md",
            "line_start": 67,
            "line_end": 69
          },
          {
            "file": "SKILL.md",
            "line_start": 69,
            "line_end": 71
          },
          {
            "file": "SKILL.md",
            "line_start": 71,
            "line_end": 75
          },
          {
            "file": "SKILL.md",
            "line_start": 75,
            "line_end": 82
          },
          {
            "file": "SKILL.md",
            "line_start": 82,
            "line_end": 142
          },
          {
            "file": "SKILL.md",
            "line_start": 142,
            "line_end": 163
          },
          {
            "file": "SKILL.md",
            "line_start": 163,
            "line_end": 169
          },
          {
            "file": "SKILL.md",
            "line_start": 169,
            "line_end": 208
          },
          {
            "file": "SKILL.md",
            "line_start": 208,
            "line_end": 225
          },
          {
            "file": "SKILL.md",
            "line_start": 225,
            "line_end": 261
          },
          {
            "file": "SKILL.md",
            "line_start": 261,
            "line_end": 317
          }
        ]
      }
    ],
    "critical_findings": [],
    "high_findings": [],
    "medium_findings": [],
    "low_findings": [],
    "dangerous_patterns": [],
    "files_scanned": 2,
    "total_lines": 519,
    "audit_model": "claude",
    "audited_at": "2026-01-16T13:21:58.070Z"
  },
  "content": {
    "user_title": "Analyze Meeting Transcripts for Communication Patterns",
    "value_statement": "Meeting transcripts contain valuable insights about your communication style that most people never discover. This skill identifies patterns in conflict avoidance, speaking habits, listening skills, and leadership behavior to help you become a more effective communicator.",
    "seo_keywords": [
      "meeting analysis",
      "communication skills",
      "meeting transcripts",
      "leadership development",
      "conflict avoidance",
      "active listening",
      "Claude",
      "Codex",
      "Claude Code"
    ],
    "actual_capabilities": [
      "Identifies conflict avoidance patterns with specific transcript examples",
      "Calculates speaking ratios and turn-taking statistics",
      "Detects filler words and hedging language usage",
      "Evaluates active listening and question-asking behavior",
      "Tracks communication trends across multiple meetings",
      "Provides timestamped improvement recommendations"
    ],
    "limitations": [
      "Requires pre-transcribed meeting files in readable formats",
      "Cannot access live meeting audio or video streams",
      "Analysis quality depends on transcript accuracy and speaker labels"
    ],
    "use_cases": [
      {
        "target_user": "Team Leaders",
        "title": "Improve Meeting Facilitation",
        "description": "Identify how inclusive your meetings are and discover ways to draw out quieter team members."
      },
      {
        "target_user": "Professionals",
        "title": "Prepare for Performance Reviews",
        "description": "Gather concrete examples of your communication strengths with timestamped evidence."
      },
      {
        "target_user": "Managers",
        "title": "Coach Direct Reports",
        "description": "Help team members understand their communication patterns with specific feedback."
      }
    ],
    "prompt_templates": [
      {
        "title": "Basic Conflict Check",
        "scenario": "Find avoidance patterns",
        "prompt": "Analyze all meetings in this folder and tell me when I avoided difficult conversations."
      },
      {
        "title": "Speaking Balance",
        "scenario": "Measure participation",
        "prompt": "Look at my meetings from the past month and calculate my speaking ratio compared to others."
      },
      {
        "title": "Listening Assessment",
        "scenario": "Evaluate active listening",
        "prompt": "Analyze these transcripts and identify moments of active listening versus missed opportunities."
      },
      {
        "title": "Quarterly Comparison",
        "scenario": "Track improvement over time",
        "prompt": "Compare my communication patterns between meetings from Q1 and Q2. Show trends."
      }
    ],
    "output_examples": [
      {
        "input": "Analyze all my meetings and tell me when I avoided conflict.",
        "output": [
          "Found 23 instances across 15 meetings of indirect communication or tension avoidance.",
          "Pattern: Hedging on critical feedback (8 times across 7 meetings).",
          "Example from 1:1 with Sarah at 00:14:32: 'So I was thinking... maybe we could potentially consider looking at the timeline again?'",
          "Recommendation: Name issues directly and remove hedging words like 'maybe' and 'potentially'."
        ]
      },
      {
        "input": "Tell me about my facilitation style in team meetings.",
        "output": [
          "You speak 60% of the time while team members speak 40%.",
          "Your question-to-statement ratio is 1:3, indicating directive leadership.",
          "You resolve disagreements quickly (avg 2 min) which may suppress team input.",
          "You draw in quieter members 3 times per meeting on average."
        ]
      }
    ],
    "best_practices": [
      "Use consistent file naming like 'YYYY-MM-DD - Meeting Name.txt' for easy organization.",
      "Ask about one behavior at a time for deeper, more actionable insights.",
      "Review patterns monthly or quarterly to track meaningful improvement over time."
    ],
    "anti_patterns": [
      "Analyzing meetings without speaker labels, which reduces pattern accuracy.",
      "Asking for everything at once instead of focusing on specific improvement areas.",
      "Ignoring improvement suggestions and not tracking progress on changed behaviors."
    ],
    "faq": [
      {
        "question": "What file formats does this skill support?",
        "answer": "Works with .txt, .md, .vtt, .srt, and .docx transcript files that have speaker labels."
      },
      {
        "question": "How many meetings can I analyze at once?",
        "answer": "No hard limit. Can process dozens of meetings though very large datasets take longer."
      },
      {
        "question": "Can I integrate this with transcription services?",
        "answer": "Export transcripts from Granola, Zoom, Google Meet, Otter.ai, or Fireflies.ai to a local folder."
      },
      {
        "question": "Is my meeting data kept private?",
        "answer": "Yes. All analysis happens locally on your machine. No data is sent to external servers."
      },
      {
        "question": "Why is my analysis missing patterns?",
        "answer": "Ensure transcripts have clear speaker labels and timestamps. Low-quality transcripts reduce accuracy."
      },
      {
        "question": "How is this different from other meeting tools?",
        "answer": "Provides deep behavioral analysis focused on personal communication patterns and growth."
      }
    ]
  },
  "file_structure": [
    {
      "name": "SKILL.md",
      "type": "file",
      "path": "SKILL.md",
      "lines": 343
    }
  ]
}