assistant-skills/meeting-notes/SKILL.md
Connor Rhodes 451b9459d2 Restructure skills into folder format and add skill-creator
Each skill is now a folder with a SKILL.md inside. Added skill-creator
skill with full eval tooling. Updated skill index and cross-references.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-04-02 20:22:47 -05:00

54 lines
1.6 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
name: meeting-notes
description: Summarize raw meeting notes into a clean, formatted summary with decisions, action items, and follow-ups.
triggers:
- summarize meeting
- meeting notes
- what happened in the meeting
- meeting summary
---
# Meeting Notes
Take raw, unstructured meeting notes and produce a clean summary.
## When to Use
Use this skill when someone provides rough notes, a transcript, or bullet points from a meeting and wants them organized into a readable summary.
## Instructions
1. Read the raw notes provided.
2. Identify: meeting title (or infer from content), date (if mentioned), and attendees (if mentioned).
3. Produce a formatted summary with these sections:
### Output Format
**Meeting:** [Title]
**Date:** [Date if known]
**Attendees:** [Names if known]
**Summary**
[24 sentence overview of what the meeting covered]
**Key Decisions**
[Bullet list of decisions made — who decided what]
**Action Items**
[Bullet list — each item includes: what needs to be done, who owns it, and any deadline mentioned]
**Follow-Up Items**
[Anything that needs future attention but isn't an immediate action]
## Rules
- Keep the summary under 300 words unless the meeting was unusually long.
- Use bullet points for decisions, action items, and follow-ups.
- Bold the names of people assigned to action items.
- Use professional but clear language. Active voice.
- If information is missing (no date, no attendees), skip that field rather than guessing.
- Never invent details that weren't in the original notes.
---
*Started with the Robot Assistant Field Guide Starter Kit. Customized in Video 4 via the assembler.*