Meeting Notes → Action Items
Convert messy meeting notes or a transcript into owned, dated action items with decisions separated from open questions. Use after a meeting when asked to pull action items, list decisions, or capture who owns what.
Copy the file into your agent runtime. Cursor loads personal skills from ~/.cursor/skills/meeting-notes-to-actions/SKILL.md and project skills from .cursor/skills/meeting-notes-to-actions/SKILL.md. Claude Code looks in .claude/skills/meeting-notes-to-actions/SKILL.md.
Meeting Notes → Action Items
When to use
Notes or a transcript are unstructured and follow-ups would otherwise vanish. Triggers: pull the action items, what did we decide, who owns what.
What it does
Separates three things people usually blur:
- Decisions — settled outcomes, stated as facts.
- Action items — each with an owner and a due date (ask or infer, never leave blank).
- Open questions — unresolved items that need a follow-up.
Steps
- Read the full notes before extracting anything.
- Pull decisions first; phrase each in past tense.
- Extract actions; attach an owner. If no owner is named, mark
owner: unassignedrather than guessing a person. - Attach a due date; if none is stated, propose one and mark it
(proposed). - List open questions last so nothing is dropped.
Output
Three lists: Decisions, Actions (owner / due / verb + object), Open questions.
Guardrails
Never invent an owner's name. unassigned is always safer than a wrong assignment. Keep action verbs concrete (draft, send, review) — avoid look into.