meeting-notes-to-actions
Skill48 starsChanged 17 days agoMITView on GitHub
Converts raw meeting notes or a transcript into decisions, action items with owners and due dates, and open questions. Use when the user pastes meeting notes, asks for a summary of a call, or wants a follow-up message for attendees.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- Amazon-Quick/Amazon-Quick-official-catalogtheir own version, first seen Oct 28, 2026
- dss-time/repo-doctor-skillstheir own version, first seen Oct 15, 2026
- Baba01hacker666/dummyskillstheir own version, first seen Oct 13, 2026
- SkillMedev/remote-team-toolkittheir own version, first seen Oct 5, 2026
- create-aquarius/business-skills-jatheir own version, first seen Sep 17, 2026
- rickbauer327-cell/solo-stack-startertheir own version, first seen Sep 15, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- Amazon-Quick/Amazon-Quick-official-catalog★ 50same name
- mDevsLabs/Skills★ 2same name
- rickbauer327-cell/solo-stack-starter★ 2same name
- ahnchen1983/agentic-substrate★ 1same name
- dss-time/repo-doctor-skills★ 1same name
- Baba01hacker666/dummyskills★ 0same name
- create-aquarius/business-skills-ja★ 0same name
- kakarot-oncloud/claude-skills★ 0same name
- SkillMedev/remote-team-toolkit★ 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 repository15 other files it gives its agents.
- api-endpoint-testerSkill
- changelog-generatorSkill
- commit-message-writerSkill
- csv-profilerSkill
- dockerfile-linterSkill
- env-file-auditorSkill
- json-diffSkill
- log-analyzerSkill
- pr-description-writerSkill
- python-code-smellsSkill
- readme-doctorSkill
- secure-code-reviewSkill
- skill-authorSkill
- sql-query-reviewerSkill
- todo-extractorSkill
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 7 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 39
Only list an action item when someone committed to it or was asked to do it.
- Very specific: line 40
Never invent an owner or a date.
- Distinctive: line 41
Start every task with a verb and keep it specific enough to tell when it is done.
- Distinctive: line 42
Keep names exactly as written in the notes.
- Distinctive: line 43
Keep the summary neutral. Do not add opinions or judge what people said.
- Distinctive: line 47
Read all of the notes before writing anything.
- Distinctive: line 50
If asked for a follow-up message, write a short one that repeats the action table and nothing else.
- Distinctive: line 54
If the notes are too short to contain decisions or tasks, say so and return only the summary.
“Common” is measured: kept by at least 6 in 10 of the 7 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 notes to actions
When to use
- The user pastes notes or a transcript and asks for a summary.
- The user needs a follow-up email or chat message after a meeting.
- Action items are buried in a long discussion.
Output format
## Summary
Two to three sentences on the purpose and the outcome.
## Decisions
- What was decided, and by whom if it is stated.
## Action items
| Owner | Task | Due |
| --- | --- | --- |
| Name | A verb-first task that can be checked | Date or "not set" |
## Open questions
- Things that were raised and not resolved.Rules
- Only list an action item when someone committed to it or was asked to do it. Ideas that nobody took are open questions.
- Never invent an owner or a date. Write
unassignedornot setinstead. - Start every task with a verb and keep it specific enough to tell when it is done.
- Keep names exactly as written in the notes.
- Keep the summary neutral. Do not add opinions or judge what people said.
Steps
- Read all of the notes before writing anything.
- Pull out decisions first, then commitments, then unresolved points.
- Fill the format above and remove empty sections.
- If asked for a follow-up message, write a short one that repeats the action table and nothing else.
Errors
If the notes are too short to contain decisions or tasks, say so and return only the summary.
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.

