Menu
Manage meeting minutes as Google Docs — capture from a discussion, share with attendees, or email. One skill, three sub-actions.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Manage meeting agendas as Google Docs — create, link to a calendar event description, share with attendees, or email. One skill, four sub-actions.
Assign due dates to Todoist tasks in batch. Walks the user through each undated task and applies their choice.
Assign priorities to Todoist tasks in batch. Walks the user through each unprioritised task and applies their choice.
Create multiple Google Calendar events from a structured list. Resolves attendees once across the batch, confirms the table, then writes.
Create multiple Todoist tasks from a structured list. Confirms the table, then writes serially.
Create a single Google Calendar event. Resolves attendees via the contacts MCP. Optionally links a Drive doc (agenda) into the description.
| name | minutes |
| description | Manage meeting minutes as Google Docs — capture from a discussion, share with attendees, or email. One skill, three sub-actions. |
Single skill, three sub-actions: capture, share, email. The user names the action; if absent, ask.
captureCreate or update a minutes doc for a meeting (past or in-progress).
drive_folders.minutes.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.batch-create-tasks with the action-item rows. Confirm before pushing.shareShare a minutes doc with the event's attendees via Drive permissions.
viewer for minutes; ask for commenter if the user wants follow-up discussion).emailEmail the minutes doc to attendees (or user-specified list) via Gmail.
Minutes — <event title> — YYYY-MM-DD and a short body summarising decisions + action items, plus a link.link action isn't separate here because capture always links the doc to the event automatically.