meeting-minutes

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

35%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill provides real bundle assets and executable commands, but the SKILL.md body is bloated with templated filler, redundant sections, and verbatim description repetition that dilute token efficiency and navigation. Inline time-sensitive lifecycle data (e.g. 'Next Review Date: 2026-03-06') further hurts conciseness.

Suggestions

Collapse the redundant Workflow / Example Usage / Implementation Details / Response Template sections into one concise sequenced workflow with an explicit validate-then-proceed checkpoint.

Remove templated filler such as 'See ## Features above' and the verbatim restatement of the description in 'When to Use'.

Move the Lifecycle Status, Risk Assessment, and Security Checklist tables into references/guidelines.md or a dedicated file, keeping SKILL.md a lean overview with clearly signaled links.

Dimension	Reasoning	Score
Conciseness	The body is heavily padded: it restates the description verbatim ('Use this skill when the task needs Use meeting minutes...'), repeats cross-references ('See ## Features above'), and duplicates overlapping sections (Workflow, Example Usage, Implementation Details, Response Template), wasting tokens on content Claude already understands.	1 / 3
Actionability	Concrete commands exist (`python -m py_compile scripts/main.py`, `python scripts/main.py`) and a real script is present, but the runnable example uses a hardcoded example transcript inside main.py rather than showing how a user passes their own input, leaving key usage details incomplete.	2 / 3
Workflow Clarity	A sequenced Workflow is present with an early scope-check and a fallback path, but validation checkpoints are implicit (no verify-then-proceed step for the script run), so the sequence has gaps per the rubric.	2 / 3
Progressive Disclosure	Bundle files (references/guidelines.md, scripts/main.py) exist and are referenced by path, but the body keeps large amounts of inline material that could live in references, and navigation is scattered across redundant sections rather than cleanly signaled one-level-deep links.	2 / 3
	Total	7 / 12 Passed

Description

50%

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 identifies the meeting-minutes domain but fails to state what the skill actually does, relying on abstract qualities rather than concrete actions or natural trigger phrases. It reads more like a usage rationale than a capability description.

Suggestions

Rewrite to lead with concrete actions, e.g. 'Structures medical meeting transcripts into formal minutes, extracting action items, decisions, and attendees.'

Add an explicit 'Use when...' clause with natural triggers such as 'meeting transcripts', 'clinical meeting notes', or 'convert meeting audio/text to minutes'.

Drop the abstract 'structured execution, explicit assumptions, clear output boundaries' framing — it is vague and conflicts with more purpose-built skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ('meeting minutes') but never lists concrete actions like 'extract action items' or 'log decisions'; instead it describes abstract qualities ('structured execution, explicit assumptions').	2 / 3
Completeness	It offers a weak implicit 'when' but no clear 'what does this skill do', and lacks an explicit 'Use when...' clause with concrete triggers, capping completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	'meeting minutes' is a natural trigger term, but the qualifier 'for other workflows that need structured execution, explicit assumptions' is technical and omits common variations a user would actually say.	2 / 3
Distinctiveness Conflict Risk	The 'meeting minutes' niche is somewhat specific, but the generic phrasing around 'structured execution' and 'clear output boundaries' could overlap with many other structured-output skills.	2 / 3
	Total	8 / 12 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
Commit: d924410

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