CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

57

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./meeting-insights-analyzer/SKILL.md
SKILL.md
Quality
Evals
Security

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 skill delivers highly actionable, concrete analysis guidance with a clear sequenced workflow and input validation, but it is noticeably verbose with redundant use-case sections and inline material that could be offloaded to reference files. Tightening repetition and splitting templates/examples into separate files would improve both conciseness and progressive disclosure.

Suggestions

Collapse the overlapping 'When to Use This Skill', 'Common Analysis Requests', and 'Related Use Cases' sections into a single concise list to cut redundancy.

Move the two long markdown output templates and the three worked examples into separate reference files (e.g., TEMPLATES.md, EXAMPLES.md) referenced one level deep from SKILL.md.

Trim or remove Example 2 and Example 3 since Example 1 already demonstrates the output format and analysis depth concretely.

DimensionReasoningScore

Conciseness

At ~322 lines the body is noticeably verbose: 'When to Use This Skill', 'Common Analysis Requests', and 'Related Use Cases' overlap heavily, and three full worked examples plus two long markdown templates pad the file beyond what Claude needs.

2 / 5

Actionability

Guidance is fully executable for an instruction-only skill: specific signal phrases ('maybe', 'kind of', 'I think'), named filler words to count, copy-paste output templates, and worked examples with concrete 'Better Approach' rewrites covering common cases.

5 / 5

Workflow Clarity

A clear 6-step sequence (Discover Data, Clarify Goals, Analyze Patterns, Provide Examples, Synthesize, Follow-Up) with input validation in Step 1 and a goal-clarification feedback loop in Step 2; only minor validation gaps remain.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and no nested references, but the long inline output templates and three full worked examples could be split into one-level-deep reference files rather than living entirely in SKILL.md.

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 clearly conveys what the skill does with several concrete, behavior-specific actions, but lacks an explicit 'Use when...' trigger clause, leaving the activation guidance only weakly implied. It is mostly distinct from other skills with natural trigger terms, though some synonyms are missing.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g., 'Use when analyzing meeting transcripts, .vtt/.srt files, or when the user asks about their communication or facilitation habits').

Include file extensions and synonyms (transcripts, recordings, .vtt, .srt, meeting notes) to improve trigger-term coverage.

Tighten the abstract opening ('uncover behavioral patterns, communication insights, and actionable feedback') into concrete verbs to lift specificity toward 5.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Identifies when you avoid conflict, use filler words, dominate conversations, or miss opportunities to listen'), though the opening clause ('uncover behavioral patterns, communication insights, and actionable feedback') is somewhat abstract, leaving minor coverage gaps.

4 / 5

Completeness

The 'what' is clear, but 'when' is only weakly implied by 'Perfect for professionals seeking to improve their communication and leadership skills' with no explicit 'Use when...' clause, capping completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

Natural terms like 'meeting transcripts and recordings', 'filler words', 'conflict', and 'communication and leadership skills' are present, but common synonyms and explicit trigger phrasings are partly missing.

4 / 5

Distinctiveness Conflict Risk

The meeting-transcript behavioral-analysis niche is mostly distinct with clear triggers, with only minor overlap risk against general communication-coaching skills.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ComposioHQ/awesome-claude-skills
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.