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

64%

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

63%Weight 40%Scale 1-5

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

The body provides concrete, actionable analysis guidance and a clearly sequenced workflow with useful output templates, but is padded with redundant sections and inlines content that would benefit from reference files. No bundle files exist, so progressive disclosure relies entirely on in-file structure.

Suggestions

Remove or merge redundant sections — 'What This Skill Does' duplicates the intro, and 'Common Analysis Requests' overlaps 'When to Use' — to tighten the body.

Move the per-platform transcript setup guides (Granola/Zoom/Google Meet/Fireflies) and the long mock example outputs into reference files linked one level deep from SKILL.md.

Trim the full Example 1 mock transcript block to a concise illustration that preserves the output structure without the lengthy quoted dialogue.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with actionable content, but several sections are redundant or padded: 'What This Skill Does' restates the intro/description, 'When to Use', 'Common Analysis Requests', and 'Related Use Cases' overlap heavily, and the full mock example output (Example 1) is very long.	3 / 5
Actionability	Concrete, actionable guidance for an instruction-only skill: specific file formats to scan (.txt, .md, .vtt, .srt, .docx), specific hedging/filler words to look for ('maybe', 'kind of', 'um', 'uh'), and copy-ready output templates with minor gaps in method detail (e.g., how to compute speaking ratio).	4 / 5
Workflow Clarity	Clear six-step sequence (Discover → Clarify → Analyze → Examples → Synthesize → Follow-Up) with the data-discovery and goal-clarification steps acting as implicit gating checkpoints; this is read-only analysis so the destructive/batch cap does not apply, though explicit validation feedback loops are absent.	4 / 5
Progressive Disclosure	Well-organized section headers aid navigation, but at ~320 lines with no bundle files, content that could be split (per-platform transcript setup guides, full mock example outputs, output templates) is inlined in SKILL.md with no one-level-deep references.	3 / 5
	Total	14 / 20 Passed

Description

66%Weight 40%Scale 1-5

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 names a clear domain with several concrete, specific actions and natural keywords, but lacks an explicit 'Use when...' trigger clause, relying on an audience tagline instead. Distinctiveness is good with minor overlap risk.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g., 'Use when analyzing meeting transcripts or recordings for communication patterns, facilitation style, or speaking habits.'

Include natural trigger synonyms and file extensions users would actually say (e.g., '.vtt', '.srt', 'meeting notes', 'analyze my meetings').

Replace the audience tagline with concrete trigger conditions rather than describing who it is 'perfect for'.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Identifies when you avoid conflict, use filler words, dominate conversations, or miss opportunities to listen') rather than vague language, though 'behavioral patterns, communication insights' is somewhat abstract, leaving minor gaps versus comprehensive coverage.	4 / 5
Completeness	Has a clear 'what' (analyzes transcripts to uncover patterns and feedback) but no explicit 'Use when...' trigger clause; the 'when' is only weakly implied via the audience tagline 'Perfect for professionals seeking to improve...', which caps completeness at 3.	3 / 5
Trigger Term Quality	Good natural keyword coverage ('meeting transcripts', 'conflict', 'filler words', 'communication', 'leadership skills'), but missing common synonyms and file extensions users might say (e.g., '.vtt', '.srt', 'meeting notes').	4 / 5
Distinctiveness Conflict Risk	Mostly distinct niche (meeting communication/behavioral analysis) with specific triggers like conflict avoidance and filler-word counting, though broad terms like 'communication insights' and 'leadership skills' carry minor overlap risk with generic coaching skills.	4 / 5
	Total	15 / 20 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: a9fa86d

Reviewed: about 19 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.