CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

meeting-assistant

Extracts key meeting information in chronological order and outputs decisions and action items; use when you need meeting minutes, action tracking, or project sync notes from transcripts or raw notes.

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Other/meeting-assistant/SKILL.md
SKILL.md
Quality
Evals
Security

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 content (sections 1-5) is genuinely strong — a complete worked example, concrete extraction rules, and a clear processing sequence — but it is buried inside a duplicated layer of generic auto-generated boilerplate that roughly doubles the file's length. The bundle files exist but are orphaned, never linked or invoked by the actual workflow.

Suggestions

Delete the duplicated generic sections (the first "When to Use"/"Key Features"/"Dependencies"/"Example Usage" set and boilerplate like "Quick Validation"); keep only the concrete sections 1-5 plus a brief "When Not to Use".

Wire the bundle files into the workflow with explicit pointers, e.g. "For output structure, use assets/meeting_minutes_template.md" and "Before returning results, verify against references/evaluation-checklist.md".

Resolve the contradictory Dependencies sections (Python 3.10+ vs. no external packages) by keeping the single accurate statement that this is an instruction-only skill.

DimensionReasoningScore

Conciseness

The body duplicates entire section sets: two "When to Use", two "Key Features", two "Dependencies" (one claiming Python 3.10+, the other stating no external packages), and two "Example Usage" sections. The first set is generic filler ("Use this skill when the request matches its documented task boundary", "No packaged executable script was detected"), so roughly half the file is padding. Not 1 because sections 1-5 are lean and genuinely useful; not 3 because the duplication and boilerplate are too substantial to call "mostly efficient".

2 / 5

Actionability

The complete worked example (input transcript through expected markdown minutes) is copy-paste ready, and output rules give concrete defaults ("TBD" deadlines, "Unassigned" owners, masking rules). Not 5 because the processing workflow never explicitly directs use of the packaged assets/meeting_minutes_template.md, and the first "Example Usage" section carries no real executable guidance. Not 3 because the core guidance is concrete and complete rather than pseudocode-level.

4 / 5

Workflow Clarity

Section 5 lays out a clear 4-step sequence (material normalization, timeline parsing, information extraction, output structuring) with an end-of-run validation pass and a failure-handling section. Not 5 because validation is described only vaguely ("run a final validation pass") with no validate-fix-retry loop and no wiring of the packaged evaluation checklist into the workflow; not 3 because the sequence and final checkpoint are explicitly present and the skill is non-destructive.

4 / 5

Progressive Disclosure

The bundle genuinely contains references/evaluation-checklist.md, references/guide.md, and assets/meeting_minutes_template.md, but the body only gestures at them generically ("Reference material available in `references/`") inside boilerplate, with no links or "see X for Y" navigation from the workflow or validation sections where they would be used. This matches the anchor of references present but not clearly signaled; not 4 because the references are never concretely wired into navigation, and not 2 because the body does have real section structure and the files are listed rather than buried.

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.

A strong description: it explicitly states concrete capabilities and a clear, natural trigger clause covering multiple use phrasings. The main deductions are the second-person "you need" in the trigger clause (voice penalty) and slightly incomplete trigger synonym coverage.

Suggestions

Rewrite the trigger clause in third person to match the guideline, e.g. "use when the user asks for meeting minutes, action tracking, or project sync notes from transcripts or raw notes".

Add common trigger synonyms such as "meeting notes" or "meeting summary" to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

"Extracts key meeting information in chronological order and outputs decisions and action items" names the domain and several concrete actions (raw fit at 4, just short of the comprehensive 5 anchor which would cover disagreements/pending-item extraction). However, the trigger clause "use when you need" is second person, and the rubric mandates a 1-point specificity penalty for second-person voice, bringing this to 3.

3 / 5

Completeness

It explicitly answers both what ("Extracts key meeting information in chronological order and outputs decisions and action items") and when ("use when you need meeting minutes, action tracking, or project sync notes from transcripts or raw notes") with concrete trigger phrases, matching the top anchor. It is not 4 because the 'when' clause is already explicit and specific, not merely present.

5 / 5

Trigger Term Quality

"meeting minutes", "action tracking", "project sync notes", "transcripts", "raw notes" are natural phrases a user would say, giving good keyword coverage. Not 5 because common variations like "meeting notes", "meeting summary", or "action items" are missing; not 3 because coverage goes well beyond the single-generic-keyword level.

4 / 5

Distinctiveness Conflict Risk

The meeting-minutes niche is clear with distinct triggers, but "action tracking" and "project sync notes" broaden it into overlap territory with general task-management and note-summarization skills. Not 5 (minor overlap risk remains); not 3 because the core triggers are firmly niche-specific.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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-assistant/SKILL.md

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.