CtrlK
BlogDocsLog inGet started
Tessl Logo

meeting-note-summarizer

Turn meeting notes or transcripts into factual summaries, decisions, questions, and action items. Use when a user wants a concise recap or needs explicit owners and deadlines extracted without filling in missing details.

68

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 content is highly actionable with concrete output formats, defined unknown markers, and two strong worked examples that model ambiguity handling. The main gains would come from tightening the repeated ASCII-box renderings and considering a reference file for the meeting-type formats.

Suggestions

Reduce token cost by rendering the ASCII output box once and having the worked examples show only the filled content or a condensed form, rather than re-drawing the full template twice.

Move the four meeting-type format tables into a separate references file (e.g. MEETING_TYPES.md) and link to it from the body, improving progressive disclosure for a ~240-line skill.

Trim the 'What It Does' section since it substantially restates the frontmatter description.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows and is mostly purposeful, but the ASCII output box is rendered three times (template plus two full worked examples) and 'What It Does' overlaps the frontmatter description, giving minor trims. It is efficient rather than lean.

4 / 5

Actionability

For an instruction-only skill it gives fully concrete, copy-ready guidance: an explicit output template, category definitions with example phrases, defined unknown markers, and two complete input-to-output examples that demonstrate tentative-vs-decided handling. The common cases are covered specifically.

5 / 5

Workflow Clarity

The six steps (Receive → Classify → Extract → Structure → Flag Missed Items → TL;DR) are clearly sequenced, and Step 5 with its ⚠️ checklist acts as an explicit validation checkpoint. There is no formal validate-fix-retry loop, but the non-destructive task does not require one.

4 / 5

Progressive Disclosure

With no bundle files the skill is a single self-contained document, but it is organized into clear, well-signaled sections (Output Structure, Meeting Types, Trigger Phrases, Step-by-Step, Examples, Pro Tips) with content appropriately placed. Minor gaps exist since the meeting-type tables and full examples could optionally split into a reference file.

4 / 5

Total

17

/

20

Passed

Description

83%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 is strong: it explicitly answers both what and when with concrete trigger phrases and mostly natural keywords. The main improvement would be adding the synonym 'minutes' and sharpening distinctiveness from adjacent summarization skills.

DimensionReasoningScore

Specificity

The description lists several concrete outputs — 'factual summaries, decisions, questions, and action items' plus 'owners and deadlines extracted' — giving multiple specific actions with only minor coverage gaps. It stops short of the fully comprehensive, distinct-operations bar of a 5.

4 / 5

Completeness

It clearly states what the skill does ('Turn meeting notes or transcripts into...') and gives an explicit 'Use when a user wants a concise recap or needs explicit owners and deadlines extracted' trigger clause, satisfying both what and when with concrete triggers.

5 / 5

Trigger Term Quality

It includes natural user phrasing such as 'meeting notes', 'transcripts', 'concise recap', 'action items', and 'owners and deadlines', giving good keyword coverage. A common synonym like 'meeting minutes' is missing, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The meeting-summarization niche is clear with distinct triggers and low conflict risk overall. Minor overlap remains with closely related skills such as a daily standup summarizer, so it is mostly distinct rather than minimal-risk.

4 / 5

Total

17

/

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
iflytek/skillhub
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.