Meeting notes to actions
Pulls decisions and action items out of raw notes.
Operations · produces a Document · built in, ready to run
What you give it
Something like this:
weekly, mon. present: ahmed, sana, me, imran joined for last 10 min.
sana: sap api sandbox is ready, partner gave creds. we said we'd test by fri.
ahmed: wants urdu in the app - long discussion abt whether urdu or roman urdu, went nowhere, parked.
imran: says 3 of the pilot stores have no smartphone. nobody knew what to do abt this.
decided: pilot = 20 stores not 50. go live 1 march.
decided: reps keep commission on portal orders (ahmed confirmed w/ mgmt)
ahmed will send the 20 store list by wed. sana testing sap by fri. i owe them the training deck - no date agreed.
also talked abt whether to charge stores a fee, ahmed said no, dropped it.
What you get back
This is a real run of the skill on the input above, not a mock-up:
# Meeting Notes Summary
## Decisions Made
- Pilot will include 20 stores instead of 50
- Go-live date set for 1 March
- Reps will keep commission on portal orders
## Action Items
| Action | Owner | Due Date |
|--------|-------|----------|
| Send list of 20 pilot stores | Ahmed | Wednesday |
| Test SAP API sandbox | Sana | Friday |
| Prepare training deck | Me (unassigned owner) | No date agreed |
## Open Questions
- How do we address the 3 pilot stores that have no smartphone?
- Should the app support Urdu, Roman Urdu, or neither? (parked, awaiting decision)
The wording changes a little every run. The shape does not — that is what the procedure below is for.
Tools it uses
None of its own. A skill that only writes needs no tools, so this one inherits whatever your assistant can normally reach.
The procedure it follows
This is the skill, in full. Add it to your own skills to change any of it.
From the notes below, produce:
- Decisions made, one line each
- Action items, each with an owner and a due date where one was stated
- Open questions nobody answered
Leave out discussion that led nowhere. If an action has no owner, write "owner: unassigned" rather than guessing one.
How to run it
| Where | How |
|---|---|
| Chat | "Run my Meeting notes to actions skill", or pick it from the + menu |
| Skills page | Find Meeting notes to actions under Library and press Add & Use |
| Automations | Invoke it on every trigger |
| API | POST /v1/skills/{id}/run — add it to your own skills first, then take the id from GET /v1/skills |
In chat, on the Skills page and in automations you do not have to add it first — a library skill runs as it is. Adding it makes an editable copy under your own skills, which is what you need to change the wording, and what the API works against.
New to skills? Start with what a skill is.