meeting-to-actions
Skill0 starsChanged 4 months agoMITView on GitHub
Convert meeting notes, a transcript, or a rough recap into a clean record of decisions, owned action items, and a follow-up message. Use whenever the user pastes meeting notes or a transcript, says "summarize this meeting", "what did we decide", "pull the action items", "who owns what", or asks for a recap email after a call. Trigger even from messy or partial notes.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- Sach1ng/PM-operating-OStheir own version, first seen Nov 1, 2026
- zhouey314-cloud/ai-agent-skillstheir own version, first seen Oct 20, 2026
- donnybacondigital-debug/claude-code-business-kittheir own version, first seen Oct 13, 2026
- tmusser/context-to-action-skillstheir own version, first seen Sep 16, 2026
- benngarnish/sage-free-skillstheir own version, first seen Jul 25, 2026
- ianklassen/ai-pm-systemtheir own version, first seen Apr 12, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- Sach1ng/PM-operating-OS★ 3same name
- tmusser/context-to-action-skills★ 2same name
- ianklassen/ai-pm-system★ 1same name
- benngarnish/sage-free-skills★ 0same name
- donnybacondigital-debug/claude-code-business-kit★ 0same name
- zhouey314-cloud/ai-agent-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- commit-craftSkill
- inbox-triageSkill
- incident-postmortemSkill
- landing-copySkill
- newsletter-forgeSkill
- pr-review-guardianSkill
- social-repurposeSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
ALWAYS produce these three blocks:
- Very specific: line 47
Never invent an owner or a due date.
- Distinctive: line 48
If two people seem jointly responsible, name a single directly responsible owner and list the other as support — shared ownership means no …
- Distinctive: line 49
Keep the recap skimmable: a busy attendee should get the gist in 15 seconds.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Meeting to Actions
A meeting only pays off if decisions and owners survive it. Extract signal (decisions + actions), drop chit-chat, and make every commitment traceable to a person.
Extraction rules
- Decision = a choice the group settled ("we'll go with Postgres"). Capture the decision AND its rationale if stated — future readers ask "why".
- Action item = something a specific person will do by some time. Every action needs an owner. If the notes name no owner, write
owner: UNASSIGNED— surfacing the gap is the point. - Open question = unresolved, needs a decision later. Don't fabricate resolutions.
- Discard: greetings, tangents, re-litigated points that were then dropped, filler.
Output template
ALWAYS produce these three blocks:
## <Meeting> — <date>
### Decisions
1. <decision> — rationale: <if given, else "not stated">
### Action items
| # | Action | Owner | Due | Notes |
|---|--------|-------|-----|-------|
| 1 | <verb-first, concrete> | <name> | <date or "TBD"> | |
### Open questions
- <question> — <who needs to answer / by when>Then, unless told not to, draft a follow-up message (Slack-length by default; email if the meeting was external):
### Follow-up draft
Subject: <meeting> — decisions & next steps
<2-3 line recap. Then the action list, each line "@owner: <action> (by <date>)". Close with the next checkpoint.>Rules
- Actions start with a verb: "Draft the RFC", not "RFC".
- Never invent an owner or a due date.
UNASSIGNED/TBDare correct answers. - If two people seem jointly responsible, name a single directly responsible owner and list the other as support — shared ownership means no ownership.
- Keep the recap skimmable: a busy attendee should get the gist in 15 seconds.
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.