Agent Skills › sgharlow/claude-code-recipes › meeting-notes-to-actions

meeting-notes-to-actions

GitHub

将杂乱的会议记录转化为结构化摘要、待办事项表及跟进邮件草稿。严格基于原文提取，不虚构信息；若存在未分配项则标记并提示用户确认，确保责任明确与可追溯性。

skills/meeting-notes-to-actions/SKILL.md sgharlow/claude-code-recipes

触发场景

处理会议笔记提取行动项谁负责什么起草跟进内容

安装

npx skills add sgharlow/claude-code-recipes --skill meeting-notes-to-actions -g -y

更多选项

不安装直接使用

npx skills use sgharlow/claude-code-recipes@meeting-notes-to-actions

指定 Agent (Claude Code)

npx skills add sgharlow/claude-code-recipes --skill meeting-notes-to-actions -a claude-code -g -y

安装 repo 全部 skill

npx skills add sgharlow/claude-code-recipes --all -g -y

预览 repo 内 skill

npx skills add sgharlow/claude-code-recipes --list

SKILL.md

Frontmatter

{
    "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

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.
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.
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.
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.