| name | minutes |
| description | Manage meeting minutes as Google Docs — capture from a discussion, share with attendees, or email. One skill, three sub-actions. |
Minutes
Single skill, three sub-actions: capture, share, email. The user names the action; if absent, ask.
Sub-actions
capture
Create or update a minutes doc for a meeting (past or in-progress).
- Read config. Workspace MCP,
drive_folders.minutes.
- Identify the event (ID, URL, or fuzzy reference).
- Locate or create the doc. Look for an agenda already linked in the event description (
agenda link action). If found, append a "Minutes" section to that doc — agenda → minutes single-document flow. If no agenda exists, create a new Doc in drive_folders.minutes titled Minutes — <event title> — YYYY-MM-DD.
- Structure the minutes:
- Attendees (from the event)
- Decisions made
- Action items (with owner + due date if known)
- Open questions
- Notes / verbatim
- Push action items to Todoist if any were captured. Use
batch-create-tasks with the action-item rows. Confirm before pushing.
- Update the event description (if not already linked) with the minutes doc link.
share
Share a minutes doc with the event's attendees via Drive permissions.
- Identify the minutes doc and the event.
- Resolve attendees from the invite list.
- Set permissions (default role
viewer for minutes; ask for commenter if the user wants follow-up discussion).
- Confirm the share list before writing.
email
Email the minutes doc to attendees (or user-specified list) via Gmail.
- Identify doc and recipients.
- Compose with subject
Minutes — <event title> — YYYY-MM-DD and a short body summarising decisions + action items, plus a link.
- Send via workspace MCP's Gmail tool. Confirm before sending.
Notes
- Prefer the single-doc agenda → minutes flow when an agenda already exists. Do not create a duplicate doc unless the user explicitly asks.
link action isn't separate here because capture always links the doc to the event automatically.- Action items pushed to Todoist must be confirmed by the user — don't silently write tasks.
