meeting-insights-analyzer
by ComposioHQmeeting-insights-analyzer helps analyze meeting transcripts for communication patterns, filler words, hedging, conflict avoidance, speaking balance, and transcript-backed coaching feedback for Workplace Communication.
This skill scores 72/100, which means it is acceptable for directory listing but should be presented as a lightweight, prompt-guidance skill rather than a tool-backed workflow. Directory users can quickly understand when to invoke it and what meeting-communication insights it aims to produce, but should expect limited implementation scaffolding because the repository evidence shows only a SKILL.md and no support files or install command.
- Clear triggerability: the description and "When to Use This Skill" section define concrete use cases such as transcript analysis, leadership feedback, filler-word review, and performance-review preparation.
- Good agent leverage: the skill goes beyond a generic prompt by naming analysis dimensions such as conflict avoidance, speaking ratios, turn-taking, question patterns, active listening, tone, and meeting facilitation.
- Install-decision value is credible: the stated outputs include actionable feedback and specific timestamped examples, helping users understand the intended benefit before adoption.
- Ships as a single SKILL.md with no scripts, resources, metadata, README, or install command, so users get guidance but no supporting tooling or packaged examples.
- Repository evidence shows limited explicit constraints and no support files, which may leave privacy handling, transcript formats, and edge cases under-specified.
Overview of meeting-insights-analyzer skill
What meeting-insights-analyzer is for
meeting-insights-analyzer is a Claude skill for turning meeting transcripts into practical feedback about communication behavior. Instead of only summarizing decisions and action items, it looks for patterns such as filler words, hedging, conflict avoidance, interruptions, speaking balance, missed listening opportunities, and facilitation habits.
The best-fit user is a manager, founder, coach, team lead, customer-facing professional, or individual contributor who has access to real meeting transcripts and wants evidence-based feedback on how they communicate in Workplace Communication settings.
The real job it helps you do
The main job is not “summarize this meeting.” It is “show me how I behaved in this meeting, where that helped or hurt the conversation, and what I should change next time.” The skill is most valuable when you want concrete examples, not vague advice.
Use it when you are preparing for a performance review, improving leadership presence, coaching a teammate, reviewing sales or customer calls, or tracking communication changes across several meetings.
What makes this skill different from a generic prompt
A normal prompt may produce a broad meeting summary. The meeting-insights-analyzer skill is more structured around behavioral diagnosis: patterns, examples, likely impact, and actionable coaching. Its strongest differentiator is the emphasis on timestamped or transcript-backed observations, which makes the feedback easier to trust and act on.
Adoption considerations before installing
This skill works best with clean transcripts that include speaker labels and, ideally, timestamps. It is less useful for short notes, anonymized fragments with no speaker attribution, or meetings where the goal is only project status extraction. Because the repository path contains only SKILL.md, expect a prompt-driven skill rather than a tool-heavy package with scripts, datasets, or automation helpers.
How to Use meeting-insights-analyzer skill
meeting-insights-analyzer install context
Install from the skill directory repository with:
npx skills add ComposioHQ/awesome-claude-skills --skill meeting-insights-analyzer
After installation, read the source file first:
meeting-insights-analyzer/SKILL.md
There are no visible companion scripts/, resources/, rules/, or metadata.json files in the repository preview, so the operating logic is concentrated in the skill document. For install decisions, inspect SKILL.md to confirm whether its analysis categories match your meeting type and privacy requirements.
Inputs that produce useful analysis
For strong meeting-insights-analyzer usage, provide more than a raw transcript. Include:
- meeting type: 1:1, leadership meeting, sales call, performance review, incident review
- your role and the role of other speakers
- the outcome you wanted from the conversation
- transcript with speaker names and timestamps if available
- what you want evaluated: directness, listening, facilitation, conflict handling, filler words
- any constraints: avoid personality judgments, focus only on observable behavior, anonymize names
A weak request is: “Analyze this meeting.”
A stronger request is: “Use meeting-insights-analyzer to review my facilitation in this 45-minute product review. I am Alex. Focus on interruptions, unanswered objections, hedging, decision clarity, and moments where I avoided conflict. Give transcript-backed examples and three practice goals for my next meeting.”
A practical workflow for first use
Start with one meeting where you clearly remember the context. Ask for a first-pass analysis, then ask for a second pass focused on one behavior. For example:
- Run a broad communication analysis.
- Identify the top 3 recurring behaviors.
- Ask for evidence snippets for each behavior.
- Convert the findings into next-meeting experiments.
- Repeat with another transcript to see whether the same pattern appears.
This workflow prevents overreacting to one isolated moment and makes the output more useful for coaching or self-improvement.
Prompt pattern for better results
Use this structure:
Use meeting-insights-analyzer for Workplace Communication feedback.
Context:
- Meeting type:
- My role:
- Desired outcome:
- Participants:
- Sensitive areas to avoid:
Analyze for:
- speaking balance
- directness and hedging
- conflict avoidance
- question quality
- active listening
- decision clarity
Output:
- top patterns
- transcript-backed examples
- likely impact on the meeting
- what to try next time
- one measurable improvement goal
This gives the skill enough context to separate normal facilitation behavior from communication habits that may need improvement.
meeting-insights-analyzer skill FAQ
Is meeting-insights-analyzer only for managers?
No. Managers and team leads are obvious users, but the skill also fits sales calls, customer success conversations, design critiques, interviews, coaching sessions, and cross-functional project meetings. It is most useful when communication style affects outcomes.
Can it analyze recordings directly?
The skill description mentions transcripts and recordings, but in practice an AI skill usually needs text input unless your environment separately transcribes audio. For reliable results, transcribe the recording first, include speaker labels, and provide timestamps where possible.
How is this different from a meeting summarizer?
A summarizer extracts what happened. meeting-insights-analyzer evaluates how communication happened. It can still surface decisions or missed follow-ups, but its core value is behavioral feedback: who dominated, where questions were ignored, when language became vague, or where a difficult topic was softened too much.
When should I not use this skill?
Do not use it as a performance judgment engine, HR evidence system, or psychological assessment. It should not infer intent, diagnose personality, or evaluate protected characteristics. It is also a poor fit for transcripts that are too short, heavily redacted, or missing speaker attribution.
How to Improve meeting-insights-analyzer skill
Improve meeting-insights-analyzer with clearer evidence
The fastest way to improve meeting-insights-analyzer output is to strengthen the transcript evidence. Add speaker names, timestamps, agenda, and expected outcome. If a comment refers to prior context, summarize that context before the transcript. Without this, the model may label a behavior as avoidance when it was actually time management, diplomacy, or scope control.
Common failure modes to watch for
The main risks are overgeneralizing from one meeting, mistaking role-based facilitation for domination, and giving generic coaching advice without transcript proof. Counter this by asking for “observable evidence only” and requesting confidence levels:
For each insight, quote or reference the transcript moment, explain why it matters, and mark confidence as high, medium, or low.
This keeps the analysis grounded and easier to challenge.
Iterate from insight to behavior change
After the first output, do not stop at the report. Ask for a small practice plan:
- one behavior to continue
- one behavior to reduce
- one phrase to replace hedging language
- two questions to ask in the next meeting
- a measurable indicator, such as “pause after objections before responding”
This turns the meeting-insights-analyzer guide into a repeatable improvement loop rather than a one-time critique.
Customize the skill for your communication norms
Teams differ. A fast-moving incident review, a legal negotiation, and a design critique do not share the same standard for interruption, directness, or challenge. Tell the skill what “good” looks like in your context. For example, specify whether direct disagreement is encouraged, whether facilitation should be neutral, and whether the goal is psychological safety, decision speed, customer trust, or executive clarity.