/meeting-notes-to-actions
Turn raw meeting notes into a shareable summary, an action-item table with owners and deadlines, and follow-up email drafts. Use when the user says "process my meeting notes", "extract action items", "who owns what from this meeting", or "draft the follow-ups" — or pastes messy
$ npx -y skills add sgharlow/claude-code-recipes --skill meeting-notes-to-actions --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/meeting-notes-to-actions
Context preview
The summary Claude sees to decide when to auto-load this skill.
Turn raw meeting notes into a shareable summary, an action-item table with owners and deadlines, and follow-up email drafts. Use when the user says "process my meeting notes", "extract action items", "who owns what from this meeting", or "draft the follow-ups" — or pastes messy
SKILL.md
meeting-notes-to-actions.SKILL.mdname: meeting-notes-to-actions
description: Turn raw meeting notes into a shareable summary, an action-item table with owners and deadlines, and follow-up email drafts. Use when the user says "process my meeting notes", "extract action items", "who owns what from this meeting", or "draft the follow-ups" — or pastes messy notes right after a meeting.
Meeting Notes to Action Items
Convert disorganized meeting notes into structured accountability: a clean summary, an action-item table, and a personalized follow-up draft per owner. Work only from what the notes actually say — never invent owners, deadlines, or decisions that are not in the notes.
Steps
1. Get the notes. Accept pasted text, a file path, or a transcript. If the notes name attendees ambiguously (initials, first names shared by two people), ask the user to resolve them before assigning ownership. 2. Extract, citing the notes:
- **Decisions made** — each with the sentence in the notes that records it.
- **Action items** — task, owner, deadline, and one line of context. If the notes give
no owner or deadline, mark it `UNASSIGNED` / `NO DATE` rather than guessing, and list those gaps for the user to fill.
- **Open questions** — anything discussed but unresolved.
3. Render three outputs in this order:
- A 3–5 sentence meeting summary suitable for forwarding.
- An action-item table: `Owner | Task | Deadline | Context`.
- One short follow-up email draft per owner covering only that owner's items.
4. Verify before presenting: every action item in the table must trace to a line in the notes, and every owner must appear in the attendee list. Ask the user to confirm the `UNASSIGNED` / `NO DATE` gaps — do not send or save drafts until they have reviewed them.
Constraints
- Drafts are drafts: Claude only writes text; the user reviews and delivers everything
from their own mail client.
- Keep each follow-up email under ~120 words — one ask, one deadline, no filler.
- If the notes contain fewer than three concrete items, say the skill is overkill and
offer a two-line summary instead.
Full walkthrough, examples, and variations: `recipes/Recipe-001-Meeting-Notes-to-Action-Items.md`.
Read more
name: meeting-notes-to-actions description: Turn raw meeting notes into a shareable summary, an action-item table with owners and deadlines, and follow-up email drafts. Use when the user says "process my meeting notes", "extract action items", "who owns what from this meeting", or "draft the follow-ups" — or pastes messy notes right after a meeting.
Meeting Notes to Action Items
Convert disorganized meeting notes into structured accountability: a clean summary, an action-item table, and a personalized follow-up draft per owner. Work only from what the notes actually say — never invent owners, deadlines, or decisions that are not in the notes.
Steps
1. Get the notes. Accept pasted text, a file path, or a transcript. If the notes name attendees ambiguously (initials, first names shared by two people), ask the user to resolve them before assigning ownership. 2. Extract, citing the notes:
- **Decisions made** — each with the sentence in the notes that records it.
- **Action items** — task, owner, deadline, and one line of context. If the notes give
no owner or deadline, mark it `UNASSIGNED` / `NO DATE` rather than guessing, and list those gaps for the user to fill.
- **Open questions** — anything discussed but unresolved.
3. Render three outputs in this order:
- A 3–5 sentence meeting summary suitable for forwarding.
- An action-item table: `Owner | Task | Deadline | Context`.
- One short follow-up email draft per owner covering only that owner's items.
4. Verify before presenting: every action item in the table must trace to a line in the notes, and every owner must appear in the attendee list. Ask the user to confirm the `UNASSIGNED` / `NO DATE` gaps — do not send or save drafts until they have reviewed them.
Constraints
- Drafts are drafts: Claude only writes text; the user reviews and delivers everything
from their own mail client.
- Keep each follow-up email under ~120 words — one ask, one deadline, no filler.
- If the notes contain fewer than three concrete items, say the skill is overkill and
offer a two-line summary instead.
Full walkthrough, examples, and variations: `recipes/Recipe-001-Meeting-Notes-to-Action-Items.md`.
Claude Code artifacts graded by Skill Crossroads — click the badge for the evidence-cited scorecard. Your Complete Guide to AI-Powered Productivity
Repo: sgharlow/claude-code-recipes
Other skills on claude-code-recipes.
- /data-cleanup
Clean and standardize messy tabular data (CSV, spreadsheet paste, system exports) into an analysis-ready dataset — consistent dates and names, typed columns, duplicates identified, missing values handled explicitly. Use when the user says "clean this data", "standardize this
Open skill - /qc-checklist
Turn a process description into an operational quality-control checklist — binary pass/fail checks, acceptance criteria, critical-vs-routine tiers, and failure modes with catch-points. Use when the user says "build a QC checklist", "standardize how we review X", "acceptance
Open skill - /research-synthesis
Synthesize multiple sources — articles, reports, notes, transcripts — into one structured brief with themes, agreements, contradictions, and gaps. Use when the user says "synthesize this research", "combine these sources", "what do these articles agree on", or has a folder of
Open skill - /summarize-document
Summarize a long document into an executive summary, key points, and role-specific implications. Use when the user says "summarize this document", "give me the key points", "do I need to read this?", or drops a long PDF, report, or contract and asks what matters in it.
Open skill - /weekly-status-report
Turn scattered weekly updates (notes, emails, task exports, meeting notes) into a structured status report with highlights, progress, severity-rated blockers, and next-week priorities. Use when the user says "write my status report", "weekly update", "summarize my week for my
Open skill

