Automate 21risk tasks via Rube MCP (Composio). Always search tools first for current schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze meeting transcripts to identify communication patterns, behavioral insights, and actionable feedback for improving communication and leadership effectiveness.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Undeveloped: No feedback on patterns; unaware of habits.
Target: Identify recurring behaviors, conflict-avoidance patterns, speaking ratios.
Optimized: Trend tracking over months, peer benchmarking, predictive coaching recommendations.
Communication patterns are visible in transcripts. Systematic analysis of what you say (and don't say) reveals habits and opportunities for growth that are invisible in the moment but clear in data.
Collect transcripts from meetings:
Transcript format:
[00:00:15] Sarah: Thanks for joining everyone. Let's start with Q2 goals.
[00:00:45] John: We're on track for most deliverables...
[00:01:20] Sarah: Great, any blockers?
[00:01:30] John: Not really, I think we're good.
[00:02:00] Sarah: Okay, moving on...
Identify key metrics:
| Pattern | How to Detect | Significance |
|---|---|---|
| Speaking Ratio | % of total words spoken | Do you dominate or hide? |
| Turn-Taking | How often you speak vs. others | Collaborative vs. unbalanced? |
| Filler Words | "Um", "like", "you know", "uh" | Confidence, preparation level |
| Hedging Language | "I think", "maybe", "possibly" | Decisiveness, confidence |
| Questions Asked | How often vs. statements | Active listening, curiosity |
| Conflict Engagement | How you handle disagreement | Assertiveness, conflict-avoidance |
| Interruptions | Instances of talking over others | Respect, impatience |
Example analysis:
## Communication Pattern Analysis: Sarah
### Speaking Ratio
- Sarah: 32% of words (160 words / 500 total)
- John: 45%
- Maria: 23%
**Interpretation**: Balanced but slightly withdrawn. Team average: 33%.
### Turn-Taking
- Sarah: 14 turns
- John: 18 turns
- Maria: 9 turns
**Interpretation**: You participate but don't dominate. Good balance.
### Filler Words
- Sarah: 8 instances ("um" x5, "like" x2, "you know" x1)
- Density: 5% of spoken words
- Benchmark: 2-3% is confident
**Interpretation**: Slight nervousness or lack of preparation.
### Hedging Language
- "I think": 6 times
- "Maybe": 2 times
- "Possibly": 1 time
- Total: 9 hedge phrases
**Interpretation**: Lack of conviction. Could be more direct.
### Questions Asked
- Sarah: 7 questions
- John: 3 questions
- Maria: 2 questions
**Interpretation**: Good active listening. Encouraging others to contribute.
### Conflict Engagement
- When John disagreed, Sarah said: "That's interesting, maybe we could..."
- Pattern: Avoidance language, doesn't directly address disagreement
- Red flag: No direct responses to challenges
**Interpretation**: Avoiding conflict. Room to be more direct.
Compare multiple meetings:
## Pattern Trends (3-Month Analysis)
### Consistent Patterns
- [ ] Speaking ratio consistently 30-35% (stable)
- [ ] Filler words appearing 5-7% (concerning, not improving)
- [ ] Hedging language present in 8-12 phrases per meeting (consistent)
- [ ] Asking 5-8 questions per meeting (consistent strength)
### Emerging Patterns
- [ ] Interruptions increasing (0 → 2 per meeting) — watch this
- [ ] Conflict avoidance worsening (John's 2nd disagreement, Sarah changed subject)
### Improving Patterns
- [ ] Turn-taking becoming more balanced (was 40%, now 32%)
- [ ] Questions improving in quality (more follow-ups, fewer yes/no)
Reference specific moments:
## Specific Behavioral Examples
### Example 1: Conflict Avoidance
**Timestamp**: [04:23-04:45]
**Situation**: John challenged your proposal
**Your Response**: "Hmm, yeah, that's a valid point. Maybe we could table this?"
**Pattern**: Avoids directly addressing concern; uses "maybe" hedge
**Impact**: Issue remains unresolved; John feels dismissed
**Alternative**: "I hear your concern about cost. Here's why I think ROI justifies it..."
### Example 2: Filler Words
**Timestamp**: [01:15-01:30]
**Your Words**: "Um, so like, I think we should, um, focus on the Q2 roadmap"
**Pattern**: 4 filler words in 15 seconds (27% rate!)
**Impact**: Reduces authority and clarity
**Alternative**: (pause) "I recommend we focus on the Q2 roadmap."
### Example 3: Strong Listening (Positive)
**Timestamp**: [06:00-06:30]
**Your Questions**: "What's your concern there?" (follow-up) "How would that affect timeline?"
**Pattern**: Natural curiosity, making others feel heard
**Impact**: Team more engaged; Sarah builds relationship
**Strength**: Keep doing this!
Create improvement plan:
## Communication Improvement Plan
### Priority 1: Reduce Hedging Language
**Current**: "I think maybe we could possibly..."
**Goal**: Direct statements 80% of time
**Action**:
- Before speaking, remove hedge phrases
- Practice: "We should...", "The best approach is..."
- Weekly reflection: How many direct statements this week?
### Priority 2: Address Conflict Directly
**Current**: Avoidance, topic-switching
**Goal**: Engage with disagreements, explore options
**Action**:
- Pause when disagreed with; ask clarifying question
- Respond with: "I see your point. Here's my perspective..."
- Practice script: "Let's explore both options..."
### Priority 3: Reduce Filler Words
**Current**: 5-7% filler word density
**Goal**: <2% filler words
**Action**:
- Pause instead of saying "um" or "like"
- Record yourself; play back and count
- Practice: Speak more slowly, articulate deliberately
### Priority 4: Continue (Strength)
**Keep**: Asking thoughtful questions, good turn-taking
**Action**: Model this for others; maybe help quiet team members
Weekly/monthly check-ins:
## Improvement Tracking (Weekly)
| Week | Hedge Phrases | Filler Words | Conflict Direct? | Questions Asked |
|------|---------------|--------------|-----------------|-----------------|
| Week 1 | 9 | 7% | No | 7 |
| Week 2 | 7 | 6% | Sometimes | 8 |
| Week 3 | 5 | 4% | Yes (1x) | 9 |
| Goal | <3 | <2% | Yes (consistently) | 7+ |
**Progress**: Trending in right direction! Continue focusing on conflict.
Deliver:
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Automate 21risk tasks via Rube MCP (Composio). Always search tools first for current schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Automate 2chat tasks via Rube MCP (Composio). Always search tools first for current schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Automate Ably tasks via Rube MCP (Composio). Always search tools first for current schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Automate Abstract tasks via Rube MCP (Composio). Always search tools first for current schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Automate Abuselpdb tasks via Rube MCP (Composio). Always search tools first for current schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Automate Abyssale tasks via Rube MCP (Composio). Always search tools first for current schemas.
日本語の概要は準備中です。原文の説明を表示しています。