Analyzes meeting transcripts and recordings to uncover behavioral patterns, communication insights, and actionable feedback. Identifies when you avoid conflict, use filler words, dominate conversations, or miss opportunities to listen. Perfect for professionals seeking to improve their communication and leadership skills.
/plugin marketplace add davepoon/buildwithclaude/plugin install all-skills@buildwithclaudeThis skill inherits all available tools. When active, it can use any tool Claude has access to.
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:
Analyze Patterns
For each requested insight:
Conflict Avoidance:
Speaking Ratios:
Filler Words:
Active Listening:
Leadership & Facilitation:
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]
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]
Offer Follow-Up Options
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 formatThis skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.