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.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./meeting-insights-analyzer/SKILL.md

Quality

Content

77%

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

The body delivers concrete, well-sequenced analysis guidance with clear checkpoints and actionable output templates, but it is a long monolithic document that over-explains some basics and would benefit from splitting large template/example sections into reference files.

Suggestions

Move the full markdown output templates and worked examples into a reference file (e.g., references/OUTPUT_TEMPLATES.md), keeping only a concise template skeleton inline.

Trim explanations of concepts Claude already knows (e.g., how to count filler words or what paraphrasing is) to respect the token budget.

Add a one-level-deep reference pointer so the overview stays lean and detailed material is clearly signaled.

Dimension	Reasoning	Score
Conciseness	The ~324-line body is mostly efficient structured guidance, but the three full output-template blocks and worked examples add length that could be tightened, and some passages restate concepts Claude already knows (e.g., explaining filler-word counting).	2 / 3
Actionability	Concrete, specific guidance throughout — exact hedging phrases ('maybe', 'kind of', 'I think'), specific metrics (speaking ratio, questions per meeting, filler words per minute), and copy-ready output templates make the instructions actionable for an instruction-only skill.	3 / 3
Workflow Clarity	A clear six-step sequence (Discover → Clarify → Analyze → Provide Examples → Synthesize → Follow-Up) with explicit checkpoints — confirm file formats, check speaker labels/timestamps, confirm date range, and clarify goals before analysis.	3 / 3
Progressive Disclosure	The skill is a monolithic 324-line SKILL.md with no bundle files (references/, scripts/, assets/ absent) and no one-level-deep references; the large output templates and example sections are inline content that could be split into separate files rather than kept in the overview.	2 / 3
	Total	10 / 12 Passed

Description

72%

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 clearly communicates the skill's purpose and lists concrete capabilities with natural trigger terms, but it omits an explicit 'Use when...' trigger clause and uses second-person voice instead of the required third person.

Suggestions

Rewrite in third person ('Analyzes... Identifies when professionals avoid conflict...') to match required voice and lift specificity.

Add an explicit trigger clause such as 'Use when analyzing meeting transcripts, recordings, or communication patterns for personal development or performance reviews.'

Trim the marketing-style closer ('Perfect for professionals seeking to improve...') which adds fluff without trigger value.

Dimension	Reasoning	Score
Specificity	It lists several concrete actions ('Analyzes meeting transcripts and recordings', 'Identifies when you avoid conflict, use filler words, dominate conversations'), but the second-person phrasing ('when you avoid conflict', 'Perfect for professionals') violates the third-person-voice rule, reducing the score by 1 from an otherwise level-3 list of specific actions.	2 / 3
Completeness	The 'what' is clearly answered (analyzes transcripts for behavioral patterns), but there is no explicit 'Use when...' clause or trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Natural terms a user would say are well covered — 'meeting transcripts', 'filler words', 'avoid conflict', 'dominate conversations', 'communication and leadership skills' — giving good coverage of common phrasings.	3 / 3
Distinctiveness Conflict Risk	The behavioral analysis of meeting transcripts is a distinct niche with specific triggers ('avoid conflict', 'filler words', speaking ratios) unlikely to collide with other skills.	3 / 3
	Total	10 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Prat011/awesome-llm-skills
Path: meeting-insights-analyzer/SKILL.md
Commit: 35e1ea2

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