meeting-analyzer
Analyzes meeting transcripts and recordings to surface behavioral patterns, communication anti-patterns, and actionable coaching feedback. Use this skill whenever the user uploads or points to meeting transcripts (.txt, .md, .vtt, .srt, .docx), asks about their communication habits, wants feedback on how they run meetings, requests speaking ratio analysis, mentions filler words or conflict avoidance, or wants to compare their communication across time periods. Also trigger when users mention tools like Granola, Otter, Fireflies, or Zoom transcripts. Even if the user just says "look at my meeti
Profile →npx skills add alirezarezvani/claude-skills --skill meeting-analyzer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Meeting Insights Analyzer > Originally contributed by [maximcoding](https://github.com/maximcoding) — enhanced and integrated by the claude-skills team. Transform meeting transcripts into concrete, evidence-backed feedback on communication patterns, leadership behaviors, and interpersonal dynamics. ## Core Workflow ### 1. Ingest & Inventory Scan the target directory for transcript files (`.txt`, `.md`, `.vtt`, `.srt`, `.docx`, `.json`). For each file: - Extract meeting date from filename or content (expect `YYYY-MM-DD` prefix or embedded timestamps) - Identify speaker labels — look for patterns like `Speaker 1:`, `[John]:`, `John Smith 00:14:32`, VTT/SRT cue formatting - Detect the user's identity: ask if ambiguous, otherwise infer from the most frequent speaker or filename hints - Log: filename, date, duration (from timestamps), participant count, word count Print a brief inventory table so the user confirms scope before heavy analysis begins. ### 2. Normalize Transcripts Different tools produce wildly different formats. Normalize everything into a common internal structure before analysis: ``` { speaker: string, timestamp_sec: number | null, text: string }[] ``` Handling per fo
- Core Workflow
- 1. Ingest & Inventory
- 2. Normalize Transcripts
- 3. Analyze
- 4. Output the Report
- 5. Follow-Up Options
- Edge Cases
- Transcript Source Tips
- Anti-Patterns
- Related Skills
What does the meeting-analyzer skill do?
Analyzes meeting transcripts and recordings to surface behavioral patterns, communication anti-patterns, and actionable coaching feedback. Use this skill whenever the user uploads or points to meeting transcripts (.txt, .md, .vtt, .srt, .docx), asks about their communication habits, wants feedback on how they run meetings, requests speaking ratio analysis, mentions filler words or conflict avoidance, or wants to compare their communication across time periods. Also trigger when users mention tools like Granola, Otter, Fireflies, or Zoom transcripts. Even if the user just says "look at my meeti
How do I install it?
Run `npx skills add alirezarezvani/claude-skills --skill meeting-analyzer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.