meeting-insights-analyzer — Claude Code skill: meeting review
Reads your meeting transcripts and points out where you dodge conflict, lean on filler words, or talk over everyone else.
npx claude-code-templates@latest --skill productivity/meeting-insights-analyzerWhat meeting-insights-analyzer does
Point the skill at a folder of transcripts and it looks for habits that repeat across meetings. How much of each call you spend talking. How often you ask instead of assert. Where your phrasing goes soft. It also counts fillers such as “um”, “like” and “you know”, and flags the moments when they spike.
The skill ships as an instruction file for the agent. It scans the folder for .txt, .md, .vtt, .srt and .docx, checks whether speaker labels and timestamps are present, confirms the date range, and locates your name in the transcripts. If you have not said what you want out of the analysis, it asks first. Then it walks the patterns and backs each one with a timestamped example: what happened, why it matters, what to say instead.
Transcripts have to exist already — the skill does not transcribe audio. Speaker labels and timestamps matter just as much. Without them there is no speaking ratio to compute and no way to tie an example to a moment in the call. A flat wall of text with no speaker turns will stall the analysis at the first step.
What it helps with
- spot the moments you steer around a tense topic
- work out your share of talking time
- count interruptions you made and took
- track filler words and hedging phrases
- collect concrete examples for a performance review
Example prompts for the agent
- Look at last month's meetings and describe my communication patterns
- Compare how I ran these two sets of meetings
How to install meeting-insights-analyzer
1claude-code-templates
npx claude-code-templates@latest --skill productivity/meeting-insights-analyzer2Skills CLI (Vercel)
npx skills add davila7/claude-code-templates --skill meeting-insights-analyzer -a claude-code3Manually: put the files in place
~/.claude/skills/meeting-insights-analyzer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/meeting-insights-analyzer/
Manually: put the files in place
.agents/skills/meeting-insights-analyzer/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/meeting-insights-analyzer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install davila7/claude-code-templates meeting-insights-analyzer2Manually: put the files in place
.github/skills/meeting-insights-analyzer/SKILL.mdPlatform CLI
gemini skills install https://github.com/davila7/claude-code-templates --path cli-tool/components/skills/productivity/meeting-insights-analyzerManually: put the files in place
.devin/skills/meeting-insights-analyzer/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about meeting-insights-analyzer
How do I install meeting-insights-analyzer in Claude Code?
With the templates CLI: npx claude-code-templates@latest --skill productivity/meeting-insights-analyzer. Or via the skills CLI: npx skills add davila7/claude-code-templates --skill meeting-insights-analyzer -a claude-code.
What does meeting-insights-analyzer do?
It mines meeting transcripts for recurring behaviour: conflict avoidance, speaking ratios, questions versus statements, filler words, signs of active listening. Each pattern comes with timestamped examples and a better phrasing.
What do I need before running it?
Transcripts already saved to a folder, in .txt, .md, .vtt, .srt or .docx. They need speaker labels and timestamps, otherwise speaking ratios and moment-by-moment examples are off the table.