meeting-minutes

Use meeting minutes for other workflows that need structured execution, explicit assumptions, and clear output boundaries.

Quality

39%

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/Academic Writing/meeting-minutes/SKILL.md

Quality

Content

42%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 body is over-sectioned and padded with repeated boilerplate, but it does point to a real, executable script and provides concrete input/output schemas. Workflow and reference structure exist but are generic and loosely signaled.

Suggestions

Cut the repeated description and the generic process boilerplate (Output Requirements, Response Template, Input Validation) that Claude already knows; keep only skill-specific guidance.

Replace circular cross-references like 'See ## Features above for related details' with direct content or remove the filler sections entirely.

Add a concrete copy-paste example invoking scripts/main.py with a real transcript and show the expected JSON output, and link references/guidelines.md explicitly by filename.

Dimension	Reasoning	Score
Conciseness	The ~196-line body is noticeably verbose and padded: the frontmatter description is repeated verbatim in multiple sections, and generic boilerplate (Output Requirements, Response Template, Input Validation, Error Handling) restates process guidance Claude already knows.	2 / 5
Actionability	It points to a real executable script and gives concrete compile/run commands plus an Input Parameters table and Output Format JSON, but the Example Usage only runs --help and the run plan is abstract — no copy-paste invocation with a real transcript input is shown.	3 / 5
Workflow Clarity	The Workflow lists five sequenced steps with a stop-early validation and a fallback, but the checkpoints are generic and implicit rather than tied to concrete verification commands against the script's output.	3 / 5
Progressive Disclosure	A real references/guidelines.md and scripts/main.py exist and are mentioned, but the reference is signaled generically ('Reference material available in references/') rather than with a clear link, and confusing inline cross-references ('See ## Features above') clutter navigation.	3 / 5
	Total	11 / 20 Passed

Description

36%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 vague and oddly phrased, describing when meeting minutes might be used rather than what the skill does. It lacks concrete actions and a clear trigger clause, leaving its purpose ambiguous.

Suggestions

Lead with the concrete capability, e.g. 'Structures medical meeting transcripts into formal minutes with action items, decisions, and attendee tracking.'

Add an explicit 'Use when…' trigger naming natural terms users say, e.g. 'Use when processing meeting transcripts, clinical/research meeting notes, or producing FDA/ICH-compliant minutes.'

Drop the abstract qualifiers ('structured execution, explicit assumptions, clear output boundaries') in favor of concrete, domain-specific actions.

Dimension	Reasoning	Score
Specificity	The description names the domain ('meeting minutes') but lists no concrete actions — 'structured execution, explicit assumptions, and clear output boundaries' are abstract properties rather than capabilities like extracting action items or logging decisions.	2 / 5
Completeness	It offers only a vague, inverted 'when'-like clause ('for other workflows that need…') and no clear statement of what the skill does; the actual capability ('Structures medical meeting transcripts into formal minutes') appears only in the body, not the description.	2 / 5
Trigger Term Quality	'meeting minutes' is a natural term a user would say, but it is wrapped in the unnatural phrase 'Use meeting minutes for other workflows that need…' and lacks synonyms or variations like 'transcripts', 'action items', or 'notes'.	3 / 5
Distinctiveness Conflict Risk	'meeting minutes' is a recognizable niche, but the qualifying clause 'structured execution, explicit assumptions, and clear output boundaries' is generic enough to overlap with many structured-output skills.	3 / 5
	Total	10 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: aipoch/medical-research-skills
Path: scientific-skills/Academic Writing/meeting-minutes/SKILL.md
Commit: 63c61d3

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