meeting-follow-up-pipeline
Turn a completed meeting into a debrief, decisions, action items, ready-to-send follow-up drafts, and proposed writebacks. Use when the user asks to debrief a meeting, process their last meeting, review meeting follow-ups, or run the meeting follow-up pipeline.
npx skills add zapier/wade-skills --skill meeting-follow-up-pipeline --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Meeting Follow-Up Pipeline Close 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. ## Setup 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.) ## When to Use - "Run the meeting follow-up pipeline" - "Debrief my last meeting" - "Process this meeting" - "What are the key follow-ups from that meeting?" Right after a meeting, during an end-of-day wrap to catch missed follow-ups,
- Setup
- When to Use
- Scope Rule: All Meetings Eligible, Not All Get the Same Treatment
- Default Target
- Source Priority
- Core Flow
- Step 1: Identify and Classify the Meeting
- Step 2: Generate the Debrief
- Step 3: Draft Follow-Ups Inline (Only When Earned)
- Step 4: Propose Promotion Actions (Propose, Don't Auto-Write)
- Step 5: Hand Off or Stop
- Required Output Shape
- Edge Cases
- Anti-Patterns
What does the meeting-follow-up-pipeline skill do?
Turn a completed meeting into a debrief, decisions, action items, ready-to-send follow-up drafts, and proposed writebacks. Use when the user asks to debrief a meeting, process their last meeting, review meeting follow-ups, or run the meeting follow-up pipeline.
How do I install it?
Run `npx skills add zapier/wade-skills --skill meeting-follow-up-pipeline --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From zapier/wade-skills, a repository with 54 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.