meeting-minutes-taker
Transforms raw meeting transcripts into high-fidelity, structured meeting minutes with iterative review for completeness. This skill should be used when (1) a meeting transcript is provided and meeting minutes, notes, or summaries are requested, (2) multiple versions of meeting minutes need to be merged without losing content, (3) existing minutes need to be reviewed against the original transcript for missing items, (4) transcript has anonymous speakers like "Speaker 1/2/3" that need identification. Features include: speaker identification via feature analysis (word count, speaking style, topic focus) with context.md team directory mapping, intelligent file naming from content, integration with transcript-fixer for pre-processing, evidence-based recording with speaker quotes, Mermaid diagrams for architecture discussions, multi-turn parallel generation to avoid content loss, and iterative human-in-the-loop refinement.
Install with Tessl CLI
npx tessl i github:fernandezbaptiste/claude-code-skills --skill meeting-minutes-taker93
Does it follow best practices?
Validation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that thoroughly covers what the skill does and when to use it. It provides specific concrete actions, natural trigger terms, explicit use-case conditions, and a distinctive scope focused on meeting transcript processing. The description is comprehensive without being padded with fluff.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Transforms raw meeting transcripts into structured meeting minutes', 'speaker identification via feature analysis', 'intelligent file naming', 'evidence-based recording with speaker quotes', 'Mermaid diagrams for architecture discussions', and 'multi-turn parallel generation'. | 3 / 3 |
Completeness | Clearly answers both what (transforms transcripts into structured minutes with various features) AND when with explicit numbered triggers: '(1) a meeting transcript is provided and meeting minutes, notes, or summaries are requested, (2) multiple versions need merging, (3) existing minutes need review, (4) anonymous speakers need identification'. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'meeting transcript', 'meeting minutes', 'notes', 'summaries', 'Speaker 1/2/3', 'transcript'. These are terms users would naturally use when requesting this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche around meeting transcripts specifically. The combination of transcript processing, speaker identification, and meeting minutes generation creates a unique scope unlikely to conflict with general document or summarization skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive, well-structured skill with excellent actionability and workflow clarity. The multi-pass generation strategy with parallel subagents is clearly documented with specific implementation details. The main weakness is verbosity - some sections could be tightened, and there's repetition between the workflow descriptions and anti-patterns. The skill would benefit from trimming redundant explanations while preserving the concrete guidance.
Suggestions
Consolidate the 'Why multiple complete passes work' and 'Why isolated context matters' explanations into the anti-patterns section or remove them entirely - Claude can infer the reasoning from the instructions
Reduce redundancy between the Core Workflow checklist and the detailed step descriptions - consider making the checklist the single source of truth with brief inline notes rather than full section expansions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but verbose in places. It includes some redundant explanations (e.g., explaining why multiple passes work, why isolated context matters) and the anti-patterns section repeats concepts already covered. However, it avoids explaining basic concepts Claude knows. | 2 / 3 |
Actionability | Highly actionable with concrete checklists, specific file path conventions, executable Mermaid diagram examples, exact quote formatting patterns, and copy-paste ready templates. The Task tool usage is clearly specified with implementation details. | 3 / 3 |
Workflow Clarity | Excellent workflow clarity with numbered steps, explicit checkboxes for progress tracking, clear validation checkpoints (speaker confirmation, filename confirmation, quality assessment decision points), and feedback loops for iteration. The multi-turn generation strategy includes explicit merge and review phases. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections, a Quick Start overview, and appropriate references to external files (meeting_minutes_template.md, completeness_review_checklist.md, context_file_template.md). Content is organized logically from quick start to detailed workflows to patterns to anti-patterns. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (646 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- 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.