Meeting to Actions

Meeting to Actions is a free agent skill maintained by Scopeful. It teaches an AI coding agent such as Claude Code, Cursor, Windsurf or Codex how to drive this tool correctly, so you do not have to re-explain it every session. Every published Scopeful skill is free and the install command is public, with no sign-in required. Scopeful also tracks hand-verified USD pricing for 39 AI creative tools at https://www.scopeful.org/tools.

Turn a meeting transcript or messy notes into clear action items.

Tags: meetings, productivity

Reference

name: meeting-to-actions description: Use this skill whenever the user has a meeting transcript, call recording notes, voice memo text, or messy meeting notes and wants the outcomes extracted. Triggers include "what were the action items", "summarize this meeting", "turn these notes into tasks", "who agreed to what", "write the follow-up email", or pasting any transcript from Zoom, Meet, Teams, Granola, Otter, or similar. Produces decisions, owned action items with deadlines, open questions, and a ready-to-send follow-up.

Meeting to Actions

A transcript is not an outcome. This skill extracts the three things that matter — what was decided, who does what by when, what's still open — and drafts the follow-up so it actually gets sent.

Input handling

• Accepts pasted text, or a file (txt/vtt/srt/docx — strip timestamps and speaker noise first).
• Audio/video file instead of text? Transcribe locally first (Whisper), then proceed — same pipeline as the video-to-tasks skill.
• If speakers are unlabeled ("Speaker 1"), infer names from context ("thanks, Maria" → previous speaker is Maria); mark uncertain attributions with (?).

Extraction rules

1. Decisions ≠ discussion. "We should probably look at X" is not a decision. "OK, let's go with the monthly plan" is. When in doubt, put it under Open questions, not Decisions.
2. Every action item needs an owner and a date. If the transcript has neither: owner = the person who volunteered or was addressed; date = "not set" flagged in red, never invented. Unassigned actions go to a separate "Unclaimed" list — those are the ones that die.
3. Keep the receipt. Each decision and action carries a short quote from the transcript. This kills "I never agreed to that" threads.
4. Deadlines in absolute dates. "By Friday" → "by Fri, Jul 17" (compute from the meeting date; ask if unknown).
5. Nothing invented. If only 2 actions were agreed, the output has 2 actions, not a padded list of 7.

Output format

MEETING: [title] — [date] — [attendees]

DECISIONS
1. [decision] — "[short supporting quote]"

ACTION ITEMS
| # | Action | Owner | Due | Source quote |
|---|--------|-------|-----|--------------|

UNCLAIMED (needs an owner)
- [action] — flag to raise in the follow-up

OPEN QUESTIONS
- [question] — [who can answer it]

PARKED / NOTED
- [things explicitly deferred]

Follow-up email (always offer, draft on yes)

Subject: [Meeting title] — decisions & next steps. Body: 1 line of thanks, decisions as short sentences, action table pasted, one explicit ask for the unclaimed items ("X needs an owner — volunteers?"), deadline recap. Under 200 words. Written in the user's voice, ready to send — not a template with placeholders.

Optional destinations

After the summary, offer once: push actions into the user's tracker (TASKS.md, Obsidian note, Linear/Asana/Notion via their MCP if connected, or a dated file). Don't ask before the summary — extract first, route second.