Use after a meeting ends: turn the notes or transcript into a follow-up draft addressed to whoever was in the room, carrying the one next step and a date.
Installs into .claude/skills of the current project.
Are you the author of Draft Follow Ups After Meetings?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/alfera-labs-draft-follow-ups-after-meetings)
---
name: draft-follow-ups-after-meetings
description: "Use after a meeting ends: turn the notes or transcript into a follow-up draft addressed to whoever was in the room, carrying the one next step and a date."
license: Apache-2.0
compatibility: ">=1.0"
metadata:
display_name: Draft follow-ups after every meeting
author: Alfera
triggers:
- draft the follow-up
- send them a recap
- what did we agree
allowed-tools:
- google_calendar
- gmail
---
# Draft follow-ups after every meeting
## What to do
1. Take the notes, transcript or agenda for the meeting that just ended.
2. Find the single thing that has to happen next, and who owns it. If the notes name three, pick the one that unblocks the others.
3. Draft a reply in the existing thread. One line that proves you were there, the next step, a date.
4. Leave it as a draft. Never send it.
## Rules
- No recap paragraph. They were in the meeting.
- If nothing was agreed, the draft says so and asks one question.
- If the workspace has taught you how it writes follow-ups, that wins over anything here.
