meeting-insights-analyzer
tessl i github:ComposioHQ/awesome-claude-skills --skill meeting-insights-analyzerAnalyzes 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.
Validation
81%| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 Passed | |
Implementation
27%This skill is significantly over-engineered and verbose, explaining concepts Claude already understands (communication patterns, filler words, conflict avoidance indicators) rather than providing lean, actionable instructions. The output templates and examples are useful but should be in separate reference files. The skill would benefit from being reduced to ~50 lines focusing on the unique workflow and pointing to reference materials.
Suggestions
Reduce to a concise overview (~50 lines) and move output templates, tool setup guides, and detailed examples to separate reference files (e.g., TEMPLATES.md, SETUP.md, EXAMPLES.md)
Remove explanations of concepts Claude already knows (what hedging language is, what filler words are, what active listening looks like) - just reference them by name
Add validation checkpoints: verify transcript parsing succeeded, confirm speaker identification accuracy, validate date range before proceeding with analysis
Replace descriptive pattern lists with a more actionable format - either concrete regex patterns for filler words or a structured checklist Claude can execute against
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300 lines. Explains obvious concepts Claude knows (what conflict avoidance looks like, what filler words are), includes extensive setup instructions for third-party tools, and repeats information across sections. The 'When to Use This Skill' and 'What This Skill Does' sections are largely redundant. | 1 / 3 |
Actionability | Provides detailed output templates and example formats which are helpful, but lacks executable code for parsing transcripts. The analysis instructions are descriptive patterns to look for rather than concrete algorithms or commands Claude can execute. | 2 / 3 |
Workflow Clarity | Has a numbered workflow (Discover → Clarify → Analyze → Provide Examples → Synthesize → Follow-up) but lacks validation checkpoints. No verification steps to confirm transcript parsing worked correctly or that speaker identification is accurate before proceeding with analysis. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline including lengthy output templates, setup instructions for multiple tools, and extensive examples. Content that should be in separate reference files (output templates, tool setup guides) bloats the main skill file. | 1 / 3 |
Total | 6 / 12 Passed |
Activation
60%The description excels at specificity with concrete examples of what it identifies (filler words, conflict avoidance, conversation dominance). However, it uses second person voice ('when you avoid conflict') which violates the third-person guideline, and lacks an explicit 'Use when...' clause to guide skill selection. The trigger terms are decent but could include more natural user phrases.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'analyze my meeting', 'review my call', 'meeting feedback', 'how did I do in the meeting'
Convert second person voice ('when you avoid conflict') to third person ('when speakers avoid conflict') to match style guidelines
Include common file/input variations users might mention: 'Zoom transcript', 'Teams recording', '.vtt files', 'call notes'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Analyzes meeting transcripts and recordings', 'uncover behavioral patterns, communication insights, and actionable feedback', 'Identifies when you avoid conflict, use filler words, dominate conversations, or miss opportunities to listen'. | 3 / 3 |
Completeness | Clearly answers 'what' (analyzes transcripts, identifies behavioral patterns) but lacks an explicit 'Use when...' clause. The 'Perfect for professionals...' is a target audience statement, not a trigger condition. | 2 / 3 |
Trigger Term Quality | Contains some relevant keywords like 'meeting transcripts', 'recordings', 'communication', 'leadership skills', but missing common variations users might say like 'meeting notes', 'call recording', 'feedback on my meeting', or file extensions. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to meeting analysis and communication feedback, but 'communication insights' and 'behavioral patterns' could overlap with general coaching or feedback skills. The meeting transcript focus helps but isn't strongly distinguished. | 2 / 3 |
Total | 9 / 12 Passed |
Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.