Skip to content
Productivity
Skill

/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

From plugin
claude-code-recipes
3766 skills
Install
$ npx -y skills add sgharlow/claude-code-recipes --skill meeting-notes-to-actions --agent claude-code

How 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.md
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`.

Read more
Ships withclaude-code-recipes

Claude Code artifacts graded by Skill Crossroads — click the badge for the evidence-cited scorecard. Your Complete Guide to AI-Powered Productivity

Get the whole plugin
Stats
376
Stars
47
Forks
Active
Maintenance
8d ago
Last commit
8mo ago
Created

Repo: sgharlow/claude-code-recipes

Other skills on claude-code-recipes.