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.

76

1.12x
Quality

64%

Does it follow best practices?

Impact

96%

1.12x

Average score across 3 eval scenarios

SecuritybySnyk

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
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.

A well-structured, actionable instruction skill with a clear workflow and concrete pattern indicators, held back by redundant sections and monolithic length. Moving example outputs and setup instructions into reference files and trimming overlapping sections would materially improve it.

Suggestions

Move the full output templates, the worked Example 1 output, and the tool-specific transcript-setup instructions into a references/ file (e.g. references/output-templates.md and references/transcript-sources.md), keeping SKILL.md a lean overview.

Consolidate the overlapping 'When to Use This Skill', 'What This Skill Does', and 'Common Analysis Requests' sections into one, removing the 'Related Use Cases' padding and the unfilled '[Instructions on how]' placeholder.

Add a light verification step to the workflow, e.g. confirming transcripts have speaker labels/timestamps before analysis and flagging files that lack them, to close the minor validation gap.

DimensionReasoningScore

Conciseness

The core Instructions section is tight and useful, but 'When to Use This Skill' overlaps 'Common Analysis Requests' and 'What This Skill Does', and the Setup Tips / Related Use Cases sections pad length (including an unfilled '[Instructions on how]' placeholder). This fits anchor 3 — mostly efficient but with unnecessary material that could be trimmed — rather than anchor 2, since nothing explains concepts Claude already knows.

3 / 5

Actionability

Gives concrete pattern indicators to search for ('maybe', 'kind of', 'yeah, but...'), copy-ready markdown output templates, and a fully worked example with a quoted transcript and a rewritten 'Better Approach'. Minor gaps (the placeholder text and vague 'Compare to industry benchmarks') keep it at anchor 4 rather than 5.

4 / 5

Workflow Clarity

A clear six-step sequence (Discover data → Clarify goals → Analyze patterns → Provide examples → Synthesize → Offer follow-up) with a clarification checkpoint ('If not specified, ask what they want to learn'). The analysis is read-only so the destructive/batch validation cap does not apply, but there are no explicit verification steps for data quality, matching anchor 4's 'minor validation gaps' rather than anchor 5.

4 / 5

Progressive Disclosure

The single file is well-sectioned, but at ~327 lines it inlines long worked templates and full example outputs that belong in reference files, and no references/ bundle exists. This matches anchor 3 ('content that should be separate is inline'); the under-50-lines exception for scoring 5 on sections alone does not apply, and it is not anchor 2 because structure and navigation within the file are good.

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.

A specific, third-person description with good natural trigger terms and a clear niche, weakened by the absence of an explicit 'Use when...' clause and some synonym/format coverage gaps. Adding an invocation trigger and transcript-file triggers would raise it to the top band.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions meeting transcripts, recordings, or wants feedback on their communication or facilitation style.'

Include transcript format keywords users actually have (.vtt, .srt, Zoom/Google Meet/Granola/Otter exports) to broaden natural trigger coverage.

Consider naming the additional analysis capabilities (speaking ratios, trend tracking over time) to close the coverage gap in the 'what' statement.

DimensionReasoningScore

Specificity

Lists several concrete actions in third person ('Analyzes meeting transcripts and recordings', 'Identifies when you avoid conflict, use filler words, dominate conversations, or miss opportunities to listen'), but coverage has gaps (no speaking-ratio, facilitation, or trend-tracking capabilities), matching anchor 4 rather than the comprehensive anchor 5.

4 / 5

Completeness

The 'what' is clear, but there is no explicit 'Use when...' trigger clause — only 'Perfect for professionals seeking to improve their communication and leadership skills', which describes an audience rather than when to invoke the skill. Per the guideline that a missing 'Use when...' clause caps completeness at 3, this matches anchor 3 ('when' only weakly implied) and not anchor 4.

3 / 5

Trigger Term Quality

Includes natural phrases users would say ('meeting transcripts', 'conflict', 'filler words', 'communication', 'leadership'), but misses common synonyms like 'calls' or 'facilitation' and transcript file extensions (.vtt, .srt), fitting anchor 4's 'good keyword coverage; a few natural terms missing' rather than anchor 5's comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

Meeting-transcript behavioral analysis is a distinct niche with specific triggers (conflict avoidance, filler words, speaking patterns), carrying only minor overlap risk with generic communication or coaching skills — anchor 4 rather than 5 because the closing audience sentence is broad.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
davepoon/buildwithclaude
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.