meeting-insights-analyzer by davila7/claude-code-templates
npx skills add https://github.com/davila7/claude-code-templates --skill meeting-insights-analyzer此技能可将您的会议转录稿转化为关于您沟通模式的可操作洞察,帮助您成为更高效的沟通者和领导者。
~/meetings/)广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
分析此文件夹中的所有会议,并告诉我我回避冲突的时刻。
查看我过去一个月的会议,并识别我的沟通模式。
比较我在这两个会议文件夹之间的引导风格。
分析此文件夹中的所有转录稿,并:
1. 识别我打断他人的时刻
2. 计算我的发言比例
3. 找出我回避给予直接反馈的时刻
4. 跟踪我使用填充词的情况
5. 展示良好积极倾听的示例
当用户请求会议分析时:
发现可用数据
明确分析目标 如果未指定,询问他们想了解什么:
分析模式 针对每个请求的洞察:
冲突回避:
发言比例:
填充词:
积极倾听:
领导力与引导:
提供具体示例 对于发现的每个模式,包含:
发现:[模式的一句话总结]
频率:[在 Y 次会议中出现了 X 次]
示例:
[会议名称/日期] - [时间戳]
发生了什么:
[来自转录稿的实际引用]
为何重要: [对影响或错失机会的解释]
更好的方法: [具体的替代措辞或行为]
[为 2-3 个最显著的示例重复此结构]
综合洞察 分析完所有模式后,提供:
分析周期:[日期范围] 分析的会议:[X 次会议] 总时长:[X 小时]
[相同结构]
[3-5 个改进沟通的具体行动]
提供后续选项
用户:"我下载了我所有的会议录音并放在一个文件夹里。告诉我所有我微妙地回避冲突的时刻。"
输出:
# 冲突回避模式
在 15 次会议中发现了 23 个您使用间接沟通或避免直接处理紧张局势的实例。
## 模式:对关键反馈使用模糊语言
**频率**:在 7 次会议中出现了 8 次
**示例 1:与 Sarah 的 1:1 会议** - 00:14:32
**发生了什么**:
> "所以,我在想……也许我们可以,比如,可能考虑再看一下时间线?我的意思是,如果你觉得这有道理的话。但你觉得怎么最好就怎么来!"
**为何重要**:
您需要指出 Sarah 的项目落后于计划,但模糊的语言("maybe", "potentially", "if you think")和最后的推诿("whatever you think")让她很容易忽视紧迫性。
**更好的方法**:
"Sarah,这个项目比计划晚了两周。我们需要今天讨论是什么阻碍了进展,并制定一个新的时间表。"
[更多示例……]
## 建议
1. **在第一句话中直接点明问题**
2. **移除模糊词语**,如 "maybe," "kind of," "sort of"
3. **提出具体问题**而不是暗示
4. **安排困难对话**而不是随意提起
用户:"分析我的团队会议,告诉我关于我的引导风格。"
输出:提供关于以下方面的洞察:
用户:"比较我 Q1 和 Q2 的会议,看看我的倾听技巧是否有所提高。"
输出:创建比较分析,显示:
来自 Granola(免费,需订阅 Lenny 的通讯):
来自 Zoom:
来自 Google Meet:
来自 Fireflies.ai, Otter.ai 等:
YYYY-MM-DD - 会议名称.txt 格式每周安装量
157
仓库
GitHub 星标数
23.4K
首次出现
2026年1月21日
安全审计
安装于
claude-code130
opencode128
cursor126
gemini-cli125
codex113
antigravity111
This skill transforms your meeting transcripts into actionable insights about your communication patterns, helping you become a more effective communicator and leader.
Pattern Recognition : Identifies recurring behaviors across meetings like:
Communication Analysis : Evaluates communication effectiveness:
Actionable Feedback : Provides specific, timestamped examples with:
Trend Tracking : Compares patterns over time when analyzing multiple meetings
~/meetings/)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.
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
When a user requests meeting analysis:
Discover Available Data
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
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
User : "Analyze my team meetings and tell me about my facilitation style."
Output : Provides insights on:
User : "Compare my meetings from Q1 vs. Q2 to see if I've improved my listening skills."
Output : Creates a comparative analysis showing:
From Granola (free with Lenny's newsletter subscription):
From Zoom :
From Google Meet :
From Fireflies.ai, Otter.ai, etc. :
YYYY-MM-DD - Meeting Name.txt formatWeekly Installs
157
Repository
GitHub Stars
23.4K
First Seen
Jan 21, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykFail
Installed on
claude-code130
opencode128
cursor126
gemini-cli125
codex113
antigravity111
AI 代码实施计划编写技能 | 自动化开发任务分解与 TDD 流程规划工具
47,700 周安装
Microsoft Store Developer CLI (msstore) 使用指南:自动化发布和管理商店应用
6,000 周安装
SwiftUI性能审计指南:检测、诊断与修复iOS应用卡顿掉帧问题
6,200 周安装
Python设计模式实战指南:KISS原则、单一职责、组合优于继承
6,200 周安装
FastAPI Python开发指南:高效后端API构建与最佳实践
6,300 周安装
前端代码审查工具 - 自动化检查TypeScript/JS代码质量、性能与业务逻辑
6,300 周安装
Tailwind CSS 高级布局教程:CSS Grid 网格布局实战技巧与响应式设计
6,300 周安装