Meeting notes to action items
Turn a meeting transcript or rough notes into decisions, owned actions with dates, and open questions, and nothing else.
In Lobstack: Skills › Library › Add
What your agent will do.
A transcript, recording summary or page of notes arrives and somebody needs to know what was agreed and who owes what.
- 01
Read all of it before writing. Decisions get reversed twenty minutes later; only the final position counts.
- 02
Decisions: one line each, with a short quote of the moment it was settled, so it can be checked against memory.
- 03
Actions as a table: action, owner, due date, source line. An owner is a named person. "We", "the team" or "someone" is not — move those to Open questions as "needs an owner".
- 04
Convert dates as said ("by Friday") into real dates from the meeting date. Where none was given, write "no date"; never invent one.
- 05
Open questions: what was raised and not settled, and who could settle it.
- 06
Leave out small talk, status recitals, and anything repeated from an earlier meeting unless it changed.
- 07
Post it as a document. Offer to create the actions as tickets or send the summary to attendees, and wait for a yes — both are writes to other people's tools.
If the notes are too thin to name owners for most actions, say so at the top rather than guessing.
The whole SKILL.md: 34 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: meeting-notes-to-actionsdescription: "Turn a meeting transcript or rough notes into decisions, owned actions with dates, and open questions, and nothing else."metadata: title: "Meeting notes to action items" category: personal tags: [meetings, actions]--- ## When to use this A transcript, recording summary or page of notes arrives and somebody needs toknow what was agreed and who owes what. ## How 1. Read all of it before writing. Decisions get reversed twenty minutes later; only the final position counts.2. Decisions: one line each, with a short quote of the moment it was settled, so it can be checked against memory.3. Actions as a table: action, owner, due date, source line. An owner is a named person. "We", "the team" or "someone" is not -- move those to Open questions as "needs an owner".4. Convert dates as said ("by Friday") into real dates from the meeting date. Where none was given, write "no date"; never invent one.5. Open questions: what was raised and not settled, and who could settle it.6. Leave out small talk, status recitals, and anything repeated from an earlier meeting unless it changed.7. Post it as a document. Offer to create the actions as tickets or send the summary to attendees, and wait for a yes -- both are writes to other people's tools. If the notes are too thin to name owners for most actions, say so at the toprather than guessing.
- PersonalFeatured
Inbox triage
Sort a mailbox, channel or queue into what needs a person today, this week, or never, with a reason and a suggested action for each.
SKILL.md · App - Personal
Daily brief
A short morning brief: what needs the person today, what changed overnight, and what the agents finished — each with a link.
SKILL.md · App - Engineering
Commit message from a diff
Write a commit message from a diff: a subject line that states what was found, then prose explaining why the change was made.
SKILL.md · App - Engineering
Triage a failing build
Triage a red CI run: find the first real failure, attribute it to a change, and say whether the code is wrong or the runner was.
SKILL.md · App - Engineering
Review what a linter cannot
Review a change for what a linter cannot see: whether it is correct, what it breaks elsewhere, and which parallel list it forgot to update.
SKILL.md · App - Writing
Release notes from merged work
Turn merged work, or a thread about it, into release notes written for the person installing the version rather than the person who built it.
SKILL.md · App