
Meeting Insights Analyzer
Turn meeting transcripts into concrete feedback on how you communicate—conflict avoidance, talk ratio, listening—so you can improve as a founder or lead.
Overview
Meeting Insights Analyzer is an agent skill most often used in Grow (also Operate, Validate) that analyzes meeting transcripts for communication and leadership patterns with actionable feedback.
Install
npx skills add https://github.com/composiohq/awesome-claude-skills --skill meeting-insights-analyzerWhat is this skill?
- Recurring behavior detection: conflict avoidance, turn-taking, question vs statement ratio, listening cues
- Effectiveness review: clarity, filler words, hedging, tone and sentiment trends
- Use across multiple meetings to track improvement and prep performance reviews
- Supports coaching others on facilitation and leadership style from the same transcripts
Adoption & trust: 2.4k installs on skills.sh; 63.7k GitHub stars; 2/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You leave calls unsure whether you avoided conflict, dominated airtime, or missed chances to listen—and you lack concrete examples to improve.
Who is it for?
Founders and indie leads with regular transcripts who want data-backed communication coaching before reviews or hiring loops.
Skip if: Teams without transcripts or consent to analyze conversations, or users who only need scheduling, agendas, or raw summarization.
When should I use this skill?
You have meeting transcripts or recordings and want pattern recognition across communication, leadership, facilitation, filler words, or conflict avoidance.
What do I get? / Deliverables
You receive pattern-based insights and behavioral feedback tied to your transcripts so you can adjust facilitation and track communication habits over time.
- Behavioral pattern report
- Communication effectiveness notes
- Actionable feedback bullets for follow-up meetings
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Communication improvement compounds during Grow when you run more customer, investor, and team calls; lifecycle is the shelf for ongoing professional habits—not one-off build tasks. Lifecycle covers recurring rituals like 1:1s, reviews, and stakeholder meetings where pattern analysis pays off over weeks.
Where it fits
Compare last month’s sales calls to see if question-asking improved after pricing objections.
Review discovery interviews for indirect answers before locking MVP scope.
How it compares
Behavioral communication analytics from transcripts—not a calendar bot or generic meeting summary skill.
Common Questions / FAQ
Who is meeting-insights-analyzer for?
Solo builders and small-team professionals seeking to improve leadership, facilitation, and listening using their own meeting transcripts.
When should I use meeting-insights-analyzer?
In Grow when reviewing recurring customer or team calls; in Operate when coaching reports; in Validate when reflecting on discovery interviews before committing to a build direction.
Is meeting-insights-analyzer safe to install?
Transcripts may contain sensitive speech and PII—review the Security Audits panel on this Prism page and only analyze meetings you are permitted to process.
SKILL.md
READMESKILL.md - Meeting Insights Analyzer
# 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 o