Terminal
Terminal/Skill
Turns a finished meeting into a debrief, decisions, action items, and follow-up drafts for the user to review.
By Zapier
Works with
npx skills add zapier/wade-skills --skill meeting-follow-up-pipelineClose the loop after a meeting. Turn a finished conversation into clarity and shipped follow-ups, so nothing important gets dropped.
The job in one line:
meeting happened → clarity shipped → nothing important gets dropped
This is not a transcript dump and not a generic recap.
Fill in the tools you use (or let the agent ask). The skill degrades gracefully — if a source isn't available, it flags that and asks for pasted input instead.
[MEETING NOTES TOOL] — where your notes/transcript live (Granola, Fathom, Otter, Fireflies, Fellow, or pasted text)[EMAIL] — your email, for drafting external follow-ups[CHAT] — your team chat, for drafting internal follow-ups (Slack, Teams, etc.)[TASK SYSTEM] — where action items get promoted (Coda, Notion, Asana, Linear, a spreadsheet)[DRAFTS AREA] — where sendable drafts get staged for review before sending (a drafts folder, an "outbox" doc, etc.)Right after a meeting, during an end-of-day wrap to catch missed follow-ups, or before the next meeting in a chain to avoid dropping context.
Classify the meeting and route it to one of three levels. Run the workflow for all three — just don't force heavy outputs when the meeting doesn't justify them.
Level 1 — Full pipeline: external, customer/prospect, partner, candidate interviews, board/investor, high-stakes internal decision meetings.
Level 2 — Internal substantive: leadership reviews, initiative reviews, staffing/org discussions, important cross-functional working sessions.
Level 3 — Lightweight capture: routine status meetings, normal recurring syncs, low-novelty internal meetings.
If the user only says "run the pipeline" / "process this meeting" / "debrief my last meeting":
Never guess across multiple adjacent meetings if the target is unclear.
If the notes tool is unavailable, say so explicitly and ask the user for pasted notes or bullets.
Determine: meeting name, time, participants, meeting type, and treatment level (1/2/3).
Extract:
Keep the debrief under ~250 words before drafts. Don't bury the takeaway in prose.
Good reasons to draft:
Do not force follow-up drafts for low-value internal chatter.
Drafting rules:
Propose — do not automatically execute:
Always propose promotion for: user-owned commitments, externally visible promises, due-soon items, repeated open loops, and decisions meaningful enough to matter later.
Usually don't promote: low-signal discussion points, conversational debris, generic chatter, speculative comments with no owner.
End by asking the smallest useful next question:
Do not default to staging or sending. Show drafts inline first.
## Source Status
| Source | Status | Notes |
|--------|--------|-------|
| [MEETING NOTES TOOL] | fresh / missing | Notes or transcript pulled |
| Calendar | fresh / missing | Meeting metadata checked |
| [EMAIL] | fresh / not_needed / missing | Used only if follow-up drafting needed |
| Reference context | not_needed / fresh / missing | Only if a factual claim was verified |
## Meeting Type
**[Meeting type] — Level [1/2/3]**
## Bottom Line
[1-2 sentences]
## Decisions
- [Decision]
- [Decision]
## Action Items
| Owner | Task | Due | Notes |
|-------|------|-----|-------|
| [You] | [Task] | [When] | [Context] |
| [Other] | [Task] | [When] | [Context] |
## Draft Follow-Ups
- **To:** [Person] · **Channel:** [Email/Chat]
- Draft: "[ready-to-send text]"
## Promotion Actions
- **[TASK SYSTEM] proposal:** [What should be added, and why]
- **[DRAFTS AREA] proposal:** [What should be staged, and why]
- **Decision-log proposal:** [If needed]
## Recommended Next Step
- [Single highest-leverage next move]
After this workflow, the user should know: