meeting-insights-analyzer
Skill8 starsChanged 3 months agoApache-2.0View on GitHub
Analyzes meeting transcripts and recordings to uncover behavioral patterns, communication insights, and actionable feedback. This skill should be used when Cline needs to identify conflict avoidance, filler words, speaking patterns, leadership tendencies, or communication improvement opportunities from meeting transcripts for professional development and coaching.
We split this skill into the rules it gives an agent
10 rules. 5 are common, 4 are distinctive, and 1 is very specific to this project.
5
Common
Most of the 41 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 35
Ensure transcripts have speaker labels and timestamps for best results
- Common: line 67
Check if files contain speaker labels and timestamps
- Common: line 73
If not specified, ask what they want to learn:
- Common: line 88
Not addressing obvious problems
- Common: line 115
Follow-up and action item clarity
- Common: line 189
Create a personal communication development plan
- Very specific: line 206
Use consistent naming: YYYY-MM-DD - Meeting Name.txt
- Distinctive: line 226
Specific over general: Always provide concrete examples with quotes rather than vague observations
- Distinctive: line 228
Action-oriented: Every insight should come with a "Better Approach" suggestion
- Distinctive: line 230
Batch processing: When analyzing multiple meetings, process them together to identify cross-meeting patterns
“Common” is measured: kept by at least 6 in 10 of the 41 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Meeting Insights Analyzer
This skill transforms meeting transcripts into actionable insights about 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 leadership and facilitation style
- Identifying when you avoid difficult conversations
- Understanding 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
- Analyzing meeting effectiveness and group dynamics
What This Skill Does
- Pattern Recognition: Identifies recurring behaviors across meetings
- Communication Analysis: Evaluates effectiveness of communication
- Actionable Feedback: Provides specific, timestamped examples with improvement suggestions
- Trend Tracking: Compares patterns over time when analyzing multiple meetings
- Strengths & Growth: Highlights both what's working and areas for improvement
How to Use
Setup
- Download meeting transcripts to a folder (e.g.,
~/meetings/) - Supported formats:
.txt,.md,.vtt,.srt,.docx - Ensure transcripts have speaker labels and timestamps for best results
Quick Start
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 listeningProcess
Step 1: Discover Available Data
- Scan the folder for transcript files
- Check if files contain speaker labels and timestamps
- Confirm the date range of meetings
- Identify the user's name/identifier in transcripts
Step 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
Step 3: Analyze Patterns
Conflict Avoidance
Look for:
- Hedging language ("maybe", "kind of", "I think", "sort of")
- Indirect phrasing instead of direct requests
- Changing subject when tension arises
- Agreeing without commitment ("yeah, but...")
- Not addressing obvious problems
- Over-qualifying ("I was wondering if perhaps we might consider...")
Speaking Ratios
- Calculate percentage of meeting time spent speaking
- Count interruptions (by and of the user)
- Measure average speaking turn length
- Track question vs. statement ratios
- Note who speaks most/least in group settings
Filler Words
- Count "um", "uh", "like", "you know", "actually", "basically", "right"
- Note frequency per minute or per speaking turn
- Identify situations where frequency increases (nervous, uncertain, presenting)
Active Listening
- Questions that reference others' previous points
- Paraphrasing or summarizing others' ideas
- Building on others' contributions
- Asking clarifying questions
- Acknowledging before pivoting
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
Step 4: Provide Specific Examples
For each pattern found:
### [Pattern Name]
**Finding**: [One-sentence summary]
**Frequency**: [X times across Y meetings]
**Example**:
**[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]Step 5: Synthesize Insights
Generate a comprehensive summary:
# Meeting Insights Summary
**Analysis Period**: [Date range]
**Meetings Analyzed**: [X]
**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]
## 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]Step 6: Offer Follow-Up
- Track same metrics in future meetings
- Deep dive into specific meetings or patterns
- Create a personal communication development plan
- Generate a summary for performance reviews
- Compare to benchmarks over time
Getting Meeting Transcripts
| Source | How to Export |
| Granola | Auto-transcribes; export to text files |
| Zoom | Enable cloud recording with transcription; download VTT/SRT |
| Google Meet | Use Google Docs auto-transcription; save as .txt |
| Fireflies.ai | Export transcripts in bulk; store locally |
| Otter.ai | Export transcripts; save as .txt or .md |
| Microsoft Teams | Download transcript from meeting recording |
File Naming Convention
Use consistent naming: YYYY-MM-DD - Meeting Name.txt
Common Analysis Questions
- "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?"
Cline Workflow Notes
- Install location: Copy this skill directory to
.cline/skills/meeting-insights-analyzer/(project-level) or~/.cline/skills/meeting-insights-analyzer/(global) - Transcript quality matters: Results improve dramatically with speaker-labeled, timestamped transcripts
- Privacy first: Meeting data is sensitive — keep analysis local and don't expose private conversations
- Specific over general: Always provide concrete examples with quotes rather than vague observations
- Balanced feedback: Include both strengths and growth areas — not just problems
- Action-oriented: Every insight should come with a "Better Approach" suggestion
- Track over time: Encourage regular analysis (monthly) to measure improvement
- Batch processing: When analyzing multiple meetings, process them together to identify cross-meeting patterns
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
- Team communication health assessment
Other versions42 projects use a version of this.
Word for word · 0
None found.
Edited · 41
- ComposioHQ/awesome-claude-skills★ 75k42% same
- ComposioHQ/awesome-codex-skills★ 17k42% same
- composio-community/awesome-codex-skills★ 16k42% same
- Prat011/awesome-llm-skills★ 1.7k42% same
- Prorise-cool/Claude-Code-Multi-Agent★ 30442% same
- ImGoodBai/goodable★ 19542% same
- ArogyaReddy/ComposioHQ-awesome-claude-skills★ 4542% same
- frostant/awesome-claude-skills★ 4442% same
- ammosu/awesome-claude-skills-zh-TW★ 2742% same
- Hassaan146/claude-skills★ 1842% same
31 more not listed
Wrote their own version · 1
- bin1874/awesome-claude-skills-zh★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use email-draft-polish, codebase-migrate and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ComposioHQSkillemail-draft-polish
Draft, rewrite, or condense emails with target tone, length, and audience; use for cold outreach, replies, status updates, or escalations where clarity and brevity matter.
Also in 4 projects that use this
ComposioHQSkillcodebase-migrate
Run large codebase migrations and multi-file refactors. Uses the Composio CLI to coordinate issue tracking, batched PRs, and CI verification while the agent executes the transforms locally across hundreds of files.
Also in 4 projects that use this
petestewartSkilldatadog-logs
Query Datadog logs via the Logs Search API v2. Use when the user asks to "check the logs", "search logs", "find errors in Datadog", "look up logs for", "show me production logs", "check for errors", "search Datadog", or any request involving log search, error investigation, or production debugging that requires Datadog log data.
Also in 3 projects that use this
ammosuSkillvideo-downloader
Downloads videos from YouTube and other platforms for offline viewing, editing, or archival. Handles various formats and quality options.
Also in 9 projects that use this
- +7 more from ComposioHQ
In this repository49 other files it gives its agents.
- a-b-testingSkill
- api-devSkill
- article-extractorSkill
- audio-genSkill
- blog-writerSkill
- brainstormingSkill
- brand-guidelinesSkill
- canvas-designSkill
- changelog-generatorSkill
- code-refactorerSkill
- competitive-ads-extractorSkill
- content-research-writerSkill
- database-managerSkill
- docker-deploySkill
- docxSkill
- domain-name-brainstormerSkill
- email-campaignsSkill
- finishing-a-development-branchSkill
- game-devSkill
- git-pushingSkill
- git-workflowSkill
- godot-helperSkill
- image-enhancerSkill
- ios-simulator-skillSkill
- langsmith-fetchSkill
- lead-research-assistantSkill
- lean-ctxSkill
- mcp-builderSkill
- pdfSkill
- playwright-skillSkill
- pptxSkill
- react-nextjs-builderSkill
- review-implementingSkill
- seo-optimizerSkill
- ship-learn-nextSkill
- skill-creatorSkill
- skill-builderSkill
- social-media-managerSkill
- staff-engineer-reviewSkill
- tailored-resume-generatorSkill
- test-driven-developmentSkill
- test-fixingSkill
- twitter-algorithm-optimizerSkill
- using-git-worktreesSkill
- video-framesSkill
- webapp-testingSkill
- xlsxSkill
- youtube-transcriptSkill
- your-skill-nameSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

