Legacy workflow
Meeting actions
Turn meeting notes into a summary, sourced actions and unresolved questions without guessing owners or deadlines.
This older link keeps its original instructions and result contract. A similarly named skill in the current library may be a different workflow.
Example resultmeeting-actions.md
# Meeting record ## Summary The group agreed to keep the launch page short. The signup-form check still needs an owner and date. ## Actions | Action | Owner | Due | Source | | --- | --- | --- | --- | | Send the revised outline | Maya | by Friday (meeting date not supplied) | “Maya will send the revised outline by Friday” | | Check the signup form | Unassigned | Not stated | “Someone should check the signup form” | ## Open questions - Who will check the signup form, and when? - Which customer quote can we use?
Fictional, illustrative output. This is not a measured model run. Your assistant creates a new draft using your facts.
Facts used in this example
{
"meeting_notes": "Fictional planning meeting: Maya will send the revised outline by Friday. The group agreed to keep the launch page short. Someone should check the signup form; no owner or date was agreed. Which customer quote can we use? Still open.",
"context": "Illustrative notes for a fictional team. No meeting date supplied."
}What you bring
- Meeting notes
Optional: Additional context. Your assistant should ask for missing facts. Give them to your chosen assistant; this page does not collect them.
What to check in your assistant
- Required meeting notes and basic input types are checked
- Summary, Actions and Open questions headings and nonempty sections are checked
- Action-table column headers are checked; empty action sections may say None
- Structural checks do not verify completeness, owners, deadlines or factual accuracy; review against the original notes
These structural checks run in your assistant or browser. They do not establish accuracy, quality or real-world success. Review the draft against your original facts.