meeting-insights-analyzer

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.

1.12x

Quality

61%

Does it follow best practices?

Impact

96%

1.12x

Average score across 3 eval scenarios

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/meeting-insights-analyzer/SKILL.md

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-sequenced and offers genuinely actionable, concrete guidance with strong output templates and a worked example. Its main weaknesses are redundancy-driven verbosity, a monolithic single-file structure with no progressive disclosure, and missing validation checkpoints for what is effectively a batch analysis operation.

Suggestions

Trim the redundant restatement sections ('When to Use This Skill', 'What This Skill Does', 'Common Analysis Requests', 'Related Use Cases') since they overlap heavily with the description and the Instructions section.

Add an explicit validation/verification checkpoint in the workflow for batch processing (e.g. confirm each transcript has speaker labels and parsed timestamps before counting metrics, and report files that were skipped and why).

Move the long output templates and the full worked examples into referenced files (e.g. references/output-templates.md, references/examples.md) so SKILL.md stays a lean overview with one-level-deep, clearly signaled references.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient guidance rather than explanations of known concepts, but it is padded with redundancy — 'When to Use', 'What This Skill Does', 'Common Analysis Requests', and 'Related Use Cases' all restate the description, and the full example outputs duplicate the synthesis template from Instructions.	2 / 3
Actionability	As an instruction-only skill it provides concrete detection heuristics (specific hedging words, a filler-word list, metrics like speaking ratio), explicit output templates, and a worked example with real quotes; per the scoring notes, absence of code is not penalized when guidance is this actionable.	3 / 3
Workflow Clarity	A clear 6-step numbered sequence (Discover, Clarify, Analyze, Examples, Synthesize, Follow-Up) with an input-verification step 1 exists, but analyzing a folder of meetings is a batch operation with no explicit validation/verification checkpoint during processing, which the guideline caps at 2.	2 / 3
Progressive Disclosure	It is a single monolithic ~320-line file with clear section headers (not a wall of text) but no bundle files or references, and long templates and example outputs are inline that could be split into separate referenced files.	2 / 3
	Total	9 / 12 Passed

Description

57%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description conveys a clear, specific niche and lists concrete behaviors it detects, but it lacks an explicit 'Use when…' trigger clause, relies on second-person voice, and misses some natural user phrasings. Adding an explicit trigger and natural-language variations would raise completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when…' clause naming the situations that should trigger this skill (e.g. 'Use when analyzing meeting transcripts or recordings for communication and leadership feedback').

Rephrase second-person constructions ('when you avoid conflict') in third person ('Identifies conflict avoidance, filler words, conversation dominance, and missed listening opportunities') to align with the required voice.

Include more natural user phrasings as trigger terms, such as 'meeting notes', 'speaking style', 'facilitation', and 'communication coaching'.

Dimension	Reasoning	Score
Specificity	Lists several concrete detection actions ('avoid conflict, use filler words, dominate conversations, or miss opportunities to listen'), which approaches the top anchor, but the second-person phrasing 'when you avoid conflict' triggers the rubric's voice penalty, reducing it by one level.	2 / 3
Completeness	It clearly states what the skill does, but the 'when' is only implied via 'Perfect for professionals seeking…' with no explicit 'Use when…' trigger clause, which the guideline caps at 2.	2 / 3
Trigger Term Quality	Terms like 'meeting transcripts', 'filler words', and 'conflict' are reasonably natural, but coverage lacks common variations users would actually say (e.g. 'meeting notes', 'my speaking style', 'how I come across in meetings').	2 / 3
Distinctiveness Conflict Risk	Behavioral analysis of meeting transcripts is a clear, distinct niche with specific triggers that are unlikely to fire for unrelated skills.	3 / 3
	Total	9 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/meeting-insights-analyzer/SKILL.md
Commit: b79ed72

Reviewed: about 11 hours ago

Table of Contents

Discovery Implementation Validation

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.