meeting-to-actions
Skill2 starsChanged 2 months agoMITView on GitHub
Turn meeting notes or transcripts into decisions, action items, owners, dates, blockers, and follow-ups.
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
- benngarnish/sage-free-skillstheir own version, first seen Jul 25, 2026
- moses607/skillforgetheir own version, first seen Jul 14, 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
- ianklassen/ai-pm-system★ 1same name
- benngarnish/sage-free-skills★ 0same name
- donnybacondigital-debug/claude-code-business-kit★ 0same name
- moses607/skillforge★ 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 repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- brief-meSkill
- clear-askSkill
- decision-briefSkill
- follow-up-draftSkill
- reduce-to-factsSkill
- status-updateSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
7
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 34
Do not send follow-ups or update tickets unless explicitly asked.
- Distinctive: line 38
Do not dump raw transcript content by default.
- Distinctive: line 42
Use only the useful subset of source-backed facts, assumptions, source gaps, stakeholder sensitivities, potential misreads, and the …
- Distinctive: line 44
Use the smallest useful output.
- Distinctive: line 46
When consuming upstream state, do not promote an assumption, inference, open question, proposed action, or stakeholder position into a …
- Distinctive: line 49
Keep unresolved approvals, owners, timing, and blockers explicit in the action record.
- Distinctive: line 50
Do not send, publish, update tickets, create events, or mutate systems unless explicitly asked.
- Very specific: line 62
If the user wants a reusable record, use the optional CONVERSATION_STATE.md template from this pack when it is available.
“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
Purpose
Turn meeting content into a compact action record without making the user reread the whole transcript.
Use For
- Zoom transcripts
- Meeting notes
- Slack threads
- Email chains
- Doc comment threads
- Ticket discussions
- Post-meeting cleanup
- Preparing follow-up messages or ticket updates
Inputs
- Zoom transcript
- Notes
- Agenda
- Related ticket or doc context when useful
- A
reduce-to-factsledger or conversation-state record
Guardrails
- Read before write.
- Do not send follow-ups or update tickets unless explicitly asked.
- Separate decisions made from open decisions.
- Name owners and dates only when the source supports them.
- Surface missing owners, due dates, and unclear blockers.
- Do not dump raw transcript content by default.
Portable Output Contract
- Use only the useful subset of source-backed facts, assumptions, source gaps, stakeholder sensitivities, potential misreads, and the suggested next action.
- Use the smallest useful output.
- Label assumptions and preserve source gaps, source anchors, and confidence labels.
- When consuming upstream state, do not promote an assumption, inference, open question, proposed action, or stakeholder position into a fact, decision, commitment, owner, or deadline without new source support.
- Keep unresolved approvals, owners, timing, and blockers explicit in the action record.
- Do not send, publish, update tickets, create events, or mutate systems unless explicitly asked.
Output
- Decisions made
- Open decisions
- Action items with owner and due date
- Blockers
- Follow-up drafts
- Tickets/docs to update if applicable
- Source gaps
If the user wants a reusable record, use the optional CONVERSATION_STATE.md
template from this pack when it is available.
Success Standard
The user should leave the meeting with an action record they can send or use immediately.
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.

