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.
93
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Critical
Do not install without reviewing
Quality
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 comprehensively covers what the skill does with specific capabilities and explicitly states when to use it with numbered trigger conditions. The description uses proper third-person voice throughout and includes natural user terminology. The only minor concern is the length, which while thorough, could potentially be trimmed without losing essential information.
| 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 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 and minutes specifically. The explicit triggers around transcripts, speaker identification, and meeting-specific terminology make it 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 well-crafted, highly actionable skill with excellent workflow clarity and progressive disclosure. The multi-turn generation strategy with parallel subagents is thoroughly documented with concrete implementation details. The main weakness is verbosity - the skill could be tightened by consolidating redundant explanations and reducing the extensive anti-patterns list.
Suggestions
Consolidate the repeated explanations of why multiple passes work (appears in Strategy A, Strategy B, and 'Why multiple complete passes work' sections) into a single concise rationale
Consider moving the extensive anti-patterns list to a separate reference file to reduce main skill length while preserving the valuable guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but verbose in places - includes some redundant explanations (e.g., explaining why multiple passes work multiple times, repeating the same concepts in different sections). The anti-patterns section is extensive but could be more concise. However, it avoids explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | Highly actionable with concrete workflows, specific file naming patterns, executable Mermaid diagram examples, exact quote formatting requirements, and copy-paste ready checklists. The Task tool usage is clearly specified with implementation details. | 3 / 3 |
Workflow Clarity | Excellent workflow clarity with explicit numbered steps, progress tracking checklist, clear validation checkpoints (speaker confirmation, filename confirmation, human review gates), and feedback loops for iteration. The multi-turn generation strategy includes explicit merge and review phases. | 3 / 3 |
Progressive Disclosure | Well-structured with clear hierarchy: Quick Start overview, Core Workflow with detailed steps, reference files table pointing to external templates/checklists. Content is appropriately split between main skill and reference files (meeting_minutes_template.md, completeness_review_checklist.md). | 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 | |
- Repository
- daymade/claude-code-skills
- Commit
392d34c
- 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.