meeting-to-action-converter
Skill0 starsChanged 21 days agoMITView on GitHub
Turn meeting notes, transcripts, or recordings summaries into a short recap of action items with one owner and a due date each, plus decisions and open questions. Use when someone pastes meeting notes or a transcript and wants next steps, action items, a recap email, a follow-up message, or asks "what did we agree to?
In this repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- beta-program-managerSkill
- cross-team-dependency-mapSkill
- customer-advisory-board-prepSkill
- data-request-routerSkill
- decision-logSkill
- deprecation-planSkill
- duplicate-request-mergingSkill
- experiment-logSkill
- feature-flag-trackingSkill
- feedback-taggingSkill
- information-debt-auditSkill
- internal-enablement-briefSkill
- kpi-health-checkSkill
- launch-readiness-checklistSkill
- new-pm-onboarding-packSkill
- pricing-packaging-change-logSkill
- process-documentationSkill
- product-metrics-definitionsSkill
- product-ops-contextSkill
- quarterly-planning-prepSkill
- raci-builderSkill
- release-notes-draftingSkill
- request-intake-triageSkill
- retro-facilitationSkill
- ritual-calendarSkill
- roadmap-hygieneSkill
- sprint-review-summarySkill
- support-escalation-patternsSkill
- tool-stack-auditSkill
- vendor-evaluation-scorecardSkill
- voice-of-customer-digestSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Read the whole source and pull out three kinds of things:
- Distinctive: line 24
Only count something as an action item if the source shows someone taking it on.
- Distinctive: line 28
Every action item needs:
- Distinctive: line 39
If two people both said they'd handle something, list it once with both names and flag "Owner unclear."
- Distinctive: line 60
Keep it short enough to paste into chat or email as is.
- Distinctive: line 62
If the person wants a follow-up message, write it as the recap with one opening line, ready to send.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Meeting to action converter
Most meetings end with everyone agreeing and nobody owning anything. This skill finds the commitments hidden in the conversation and makes each one specific enough to check off.
Before you start
If .agents/product-ops-context.md exists (or .claude/product-ops-context.md), read it first. Use the team, owners, tools, meetings, and metric definitions it already has, and only ask for what's missing or specific to this task. If it doesn't exist, go ahead with what you're given, and suggest running product-ops-context once so the next skill doesn't have to ask.
Step 1: Find the commitments
Read the whole source and pull out three kinds of things:
- Action items: someone said they would do something, or was asked and agreed
- Decisions: a call was made (hand these to the decision-log skill if a full entry is needed)
- Open questions: raised but not answered, or parked for later
Only count something as an action item if the source shows someone taking it on. "We should look into X" with no taker is an open question, not an action.
Step 2: Make each action specific
Every action item needs:
| Field | Rule |
| Action | Starts with a verb; says what "done" looks like |
| Owner | One person, by name. Never a team, never "we," never two names |
| Due | Date from the source. If none was set, write "No date set" |
| Depends on | Another action or person, if the source says |
Rewrite vague actions into checkable ones only using what the source says: "follow up on pricing" becomes "Send Dana the updated pricing sheet" if the notes say that's what was meant. If the source doesn't say, keep it vague and flag it.
If two people both said they'd handle something, list it once with both names and flag "Owner unclear."
Step 3: Write the recap
# [Meeting name] — [Date]
**Attendees:** [names]
## Action items
- [ ] **[Owner]:** [Action] — Due [date]
## Decisions
- [Decision, one line each]
## Open questions
- [Question] — Who can answer: [name, if known]
## Flags
- [Actions with no owner, no date, or an unclear owner]Keep it short enough to paste into chat or email as is. No meeting narrative, no "great discussion," no summary of who said what unless asked.
If the person wants a follow-up message, write it as the recap with one opening line, ready to send.
Related skills
- decision-log — log the decisions in full
- ritual-calendar — check the meeting has a clear purpose
- cross-team-dependency-map — track actions that block other teams
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

