Library › Email & communication

Turn meeting notes into action items

Turn messy meeting notes or a transcript into decisions, action items (owner + due date), open questions, and a ready-to-send follow-up email. Use when the user shares meeting notes or a transcript and wants next steps, a recap, or a follow-up.

Self-tested · demo data v1.0 · self-tested 2026-10-13 · run by Grok Bot

What "self-tested" means: our own AI agent ran this skill against the fictional demo files and we published its real output, failures included. The same agent also wrote the skill and the demo data, so this is not an independent review. Check results yourself before you rely on them.

Download skill folder (.zip)SKILL.md only

Drop the folder into your agent's skills directory (e.g. ~/.agents/skills/ or ~/.claude/skills/), or paste SKILL.md into any chat assistant. Demo files included:

demo/notes.md

Test record

Field	Value
Status	Self-tested (demo data)
Version / date	v1.0 test: 2026-10-13 (no failures in this skill were scheduled for the Oct 14 fix round; re-labeled only)
Model / agent	Grok Bot (the same agent that wrote the skill and the demo data, so this is not an independent test)
Input	`demo/notes.md`: messy notes from a fictional community-garden meeting on Thu Oct 8, 2026
Method	Grok Bot followed SKILL.md on the demo file. Output is unedited.

Real output

Decisions 1. Fall cleanup day is Sat Oct 24, 9 AM–12 PM. 2. The 2 empty plots go to the first 2 people on the 7-person waitlist. 3. Next meeting: Thu Nov 12, 6:30 PM ("same time").

Actions | Task | Owner | Due | |---|---|---| | Email the city about the water spigot being shut off early | Mina | Fri Oct 16 ("next fri" from Thu Oct 8; could mean Oct 9, see open questions) | | Bring big rakes + wheelbarrow to cleanup | Theo | Sat Oct 24 | | Make a flyer for cleanup day | Abby (tentative: "I can probably do it") | DUE? (needs to be before Oct 24) | | Contact the first 2 waitlisted people about the empty plots | Rosa | DUE? |

Open questions - Compost bins: buy 3 from Hillside Lumber ($340 quote, Grant) or build them (Mina estimates under $300)? Not decided. - Treasury balance conflict: Rosa said ~$1,150; Abby later said $1,050. Which is right? - Does "next fri" for Mina's email mean Oct 9 or Oct 16? - Is Abby confirmed for the flyer?

Follow-up email draft (not sent)

Subject: Garden meeting recap (Oct 8) + action items

Hi all, thanks for coming Thursday. Quick recap:

Decided: Cleanup day is Sat Oct 24, 9–12. The two empty plots go to the first two people on the waitlist. Next meeting is Thu Nov 12 at 6:30 PM.

Actions: - Mina: email the city about the spigot by Fri Oct 16 - Theo: bring rakes + wheelbarrow on Oct 24 - Abby: cleanup flyer (Abby, can you confirm, and say when it'll be ready?) - Rosa: contact the first two waitlisted folks

Still open: buy vs. build the compost bins ($340 quote vs. under $300 DIY), and we need to confirm the bank balance ($1,150 vs. $1,050).

Thanks! [Your name]

Known failures / limits

Ambiguous relative dates. "Next fri" was resolved to Oct 16 and flagged, but the skill can't know the intent. Users must confirm.
Tentative owners. "I can probably do it" was kept as tentative, not confirmed. That was correct, but it depends on the agent noticing hedged language.
The off-topic personal comment ("puppies") was left out, as the guardrail says. Some groups might want social notes kept.
Not tested on a real audio transcript with speaker errors or crosstalk.
Self-test bias: the same agent wrote the demo and ran the test.

The skill file

---
name: meeting-notes-to-actions
description: Turn messy meeting notes or a transcript into decisions, action items (owner + due date), open questions, and a ready-to-send follow-up email. Use when the user shares meeting notes or a transcript and wants next steps, a recap, or a follow-up.
license: MIT
metadata:
  library: TriedSkills
  job: Turn meeting notes into action items
  version: "1.0"
---

# Meeting notes → action items + follow-up

## Inputs
Raw notes or a transcript, plus the meeting date. Optionally, the attendee list and who will send the follow-up.

## Steps
1. Read everything once before writing anything.
2. Pull out **decisions**: things the group agreed. Don't record a suggestion as a decision.
3. Pull out **action items** as: verb-first task, **owner**, **due date**. If either is missing in the notes, write `OWNER?` or `DUE?`. Never guess an owner.
4. Turn relative dates ("next Friday") into calendar dates using the meeting date, and show the conversion.
5. List **open questions**: anything unresolved, plus any contradictions in the notes.
6. Draft a follow-up email under 180 words: thanks, decisions, a table of actions, open questions, and the next meeting date.

## Output format
Decisions → Actions table (Task | Owner | Due) → Open questions → Follow-up email draft.

## Guardrails
- Quote numbers and amounts exactly as written. Flag any that conflict.
- Don't send the email; give the draft to the user.
- Leave out side comments that are personal or sensitive.