meeting-minutes-generator

Generates structured meeting minutes from text transcripts. Use when the user provides text content and wants a structured summary with a signature.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Other/meeting-minutes-generator/SKILL.md

Quality

Content

56%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 core workflow and output template are concrete and actionable, but the body is padded with generic boilerplate that adds little meeting-specific value and signals its reference file only vaguely.

Suggestions

Remove or collapse generic boilerplate sections (Output Contract, Failure Handling, Validation and Safety Rules, Quick Validation) that restate general skill discipline rather than meeting-minutes specifics.

Link the reference file explicitly where it is used, e.g. "See [references/prompts.md](references/prompts.md) for the generation prompt template," instead of a vague references/ mention.

Flesh out the Generation step with how the extracted fields map into the output template so the actionability gap closes.

Dimension	Reasoning	Score
Conciseness	Large generic boilerplate sections (Key Features, Implementation Details, Output Contract, Validation and Safety Rules, Failure Handling, Quick Validation) pad the body with guidance Claude already knows, e.g. "No local script validation step is required for this skill."	2 / 5
Actionability	The Workflow gives a concrete extraction list (participants, topics, decisions, action items, next steps) and the Output Format block is a copy-paste-ready template with specific fallbacks like "Not specified" and "None identified".	4 / 5
Workflow Clarity	Three sequenced steps (Input Analysis, Processing, Generation) clearly order the work for this simple, non-destructive task, with only minor thinness in the Generation step.	4 / 5
Progressive Disclosure	A references/ file exists and is mentioned generically ("Reference material available in references/") but is never linked specifically from the workflow, and generic meta-sections are inlined that could be separated.	3 / 5
	Total	13 / 20 Passed

Description

78%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 cleanly answers both 'what' and 'when' with an explicit trigger clause and concrete domain terms. It is held back from a perfect score by listing only one action and lacking synonym variants of its trigger terms.

Suggestions

Add 1-2 more concrete actions (e.g., extracts action items and decisions, formats participant lists) to broaden capability coverage.

Include common synonyms such as "meeting notes" or "transcription files" alongside "text transcripts" to improve trigger term recall.

Dimension	Reasoning	Score
Specificity	"Generates structured meeting minutes from text transcripts" names the domain and one concrete action but lists no additional capabilities, matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It explicitly states both what it does ("Generates structured meeting minutes from text transcripts") and when to use it ("Use when the user provides text content and wants a structured summary with a signature"), with a concrete trigger clause.	5 / 5
Trigger Term Quality	Phrases like "meeting minutes", "text transcripts", "text content", and "structured summary" give good natural keyword coverage, though common synonyms (e.g., meeting notes, transcription files) are missing.	4 / 5
Distinctiveness Conflict Risk	Meeting-minutes generation with a signature is a mostly distinct niche, with only minor overlap risk against general summarization skills.	4 / 5
	Total	16 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	14 / 16 Passed

Repository: aipoch/medical-research-skills
Path: scientific-skills/Other/meeting-minutes-generator/SKILL.md
Commit: f5ef65b

Reviewed: ~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.