| name | meeting-notes |
| description | Use this skill to process meeting transcripts (VTT/SRT format) to extract structured minutes, action items, and decisions. Trigger this whenever given a transcript file, or when asked to "create meeting documentation", "extract action items", or "summarize the meeting". This will also optionally integrate the findings into GitHub, Jira, or Slack. |
Meeting Notes Skill
Process Microsoft Teams meeting transcripts (VTT format) to extract meeting minutes, action items, and decisions.
Task Flow
- Transcript Parsing: Read VTT (WebVTT) format files. See references/formats.md for parsing logic.
- Analysis: Identify decisions, actions, and key discussions using NLP and pattern matching.
- Generation: Produce structured markdown meeting minutes. See references/examples.md for standard output format.
- Integration: Offer to update GitHub issues, Jira tickets, or Slack messages.
Output Structure
The primary output is markdown minutes containing:
- Meeting Header (title, date, attendees, duration)
- Executive Summary (1-2 sentence overview)
- Decisions (bulleted list with rationale and owners)
- Action Items (table format with owner, description, and due date)
- Key Discussion Points (organized by topic)
- Blockers & Follow-ups (open questions, escalations)
Reference Materials
- Formats & Logic: references/formats.md - VTT format details, parsing logic, and system integration commands.
- Examples: references/examples.md - Comprehensive before-and-after demonstration of a meeting processing workflow.
Features
- Automatic Detection: Identify speakers, decisions ("we agreed"), and actions ("@owner will").
- Confidence Scoring: Heuristic-based scoring for decision certainty and action clarity.
- System Integration: Automated
gh issue comment, jira issue create, and slack chat postMessage.
Related Skills & Tools
github-cli - For posting to GitHub issuesjira - For creating Jira ticketsslack-api - For posting to Slack channelsmarkdown - For formatting output
Troubleshooting
- Poor Transcript Quality: Manually provide speaker list in the first line of the VTT.
- False-Positives: Use the summary prompt to manually filter incorrect actions before integration.
- Large Meetings: Be concise in discussion summaries to avoid context bloat.
