Meeting Notes to Actions
A meeting summary tells you what was talked about. An action table tells you who's doing what by when. They're not the same document, and only one of them stops the same meeting happening again next week. Meeting Notes to Actions builds the second.
What this skill does
This is the action-extraction specialist — narrower than the broader meeting-debrief skill, deliberately. Where a debrief gives you the full picture (decisions, discussion, next steps, open questions, all sections), this one optimises for the bit that actually drives accountability: the action table. Everything else — decisions, open questions, parking lot, context — is supporting material around it. The action table is what gets posted in the channel within the hour. The full summary goes out same-day to attendees and absentees.
Extraction follows hard rules. Every action item starts with a verb. Every action has a single owner — not "the team", not "Sarah and Mike" — one name accountable, with the right to delegate. Every action has a deadline; if none was stated, it gets flagged "TBD — needs date" rather than quietly omitted. Vague timing gets translated ("soon" → flagged, "next week" → specific date, "after launch" → date with assumption). Passive commitments ("that needs to get done") get marked UNASSIGNED prominently rather than disappearing into the prose. The bias is toward over-extraction — better to flag something that gets dismissed than miss a commitment that falls through.
The skill catches the things that summarisers fudge. Implied decisions — the group debated A and B, then started planning A, that's a decision for A even though nobody said the word "decided". Unresolved disagreements — two people disagreed and the conversation moved on, that's an OPEN QUESTION not a decision, flagged with both positions. Contradictions — someone says "we're cutting feature X" and later someone references "when we build X", flagged explicitly. "We should" aspirations with no owner or timeline — Parking Lot, not Actions.
Thin meetings get diplomatic honesty. If the notes contain only chitchat and async-able status sharing with no decisions and no actions, the output says so plainly — "this meeting produced 0 decisions and 0 actions, the content could have been [specific async format]". That line is uncomfortable. It's also the only way the same meeting stops repeating.
When this triggers
- ·You've got raw notes or a Fireflies transcript and need the action items pulled out — fast
- ·Your meetings keep repeating because nobody can find what was actually agreed last time
- ·You want a single action table you can paste into Slack so people see their name and their deadline
- ·Half your action items have no owner ('we should...') and you need them flagged not hidden
- ·You need a confidential-redacted version for wider distribution alongside the full attendee version
Example
Trigger
User pastes a 6,000-word transcript from a product roadmap call.
Output
Action Items (9): | # | Action | Owner | Deadline | Status | |---|--------|-------|----------|--------| | 1 | Send revised pricing deck to [client] | Sarah | Fri | Open | | 2 | Spike JWT auth migration | Marcus | Wed | Open | | 3 | Schedule onboarding workshop | UNASSIGNED | TBD | Flagged | | ... 6 more ... | Decisions (4): 1. Pricing v2 launches Aug 1. Decided by [name]. Alternatives rejected: Q4 launch, phased rollout. 2. Drop the "Lite" tier — telemetry doesn't justify it. ... Open Questions (3): · SSO support this year — [A] favours yes, [B] favours no. Decision owner: TBD. Deadline to decide: TBD. Flagged. Parking Lot (2): EU expansion scoping · partner API tiering. Flagged for follow-up: 1 unassigned action, 2 missing deadlines, 1 unresolved disagreement.
Get this skill + 15 more
Included in the The Agency Owner Stack — scale delivery without scaling headcount. Save $130+ vs buying individually.
Get The Agency Owner Stack — $149What you get
- 150-line SKILL.md, ready to drop into ~/.claude/skills/
- Tested through 3 Karpathy-loop iterations (versions v1.0.0 → v1.3.0)
- Triggers automatically when relevant — no command to remember
- Lifetime updates as the skill is refined further
More from Project Management
Doesn't write teleprompter scripts — it writes structured talking outlines that make the speaker sound prepared, not robotic
Doesn't write internal status reports — it writes client-facing documents that manage expectations and build the relationship
Doesn't just format text — it filters for signal, highlight blockers early, and write updates that make managers confident without requiring follow-up questions
Doesn't just tell people to block time — it analyzes their role, energy patterns, and meeting load to engineer a schedule where deep work is structurally guaranteed, not aspirational
Doesn't give vague advice like "check email twice a day" — it builds the specific rules, filters, templates, and workflows that make inbox zero sustainable
Doesn't just tell people to have fewer meetings — it classifies each specific meeting with a verdict and replacement strategy
Browse the full library
297 skills across 31 categories. One purchase, lifetime updates.
See all bundles