← ClaudeAtlas

meeting-todoslisted

Extract action items from a meeting note and add them to the to-do list. Separates your tasks from others' tasks. Trigger /meeting-todos. Do NOT use for general task management or pulling full meeting transcripts.
adelaidasofia/claude-meeting-todos · ★ 0 · Data & Documents · score 73
Install: claude install-skill adelaidasofia/claude-meeting-todos
# Meeting → To-Do Extractor After a meeting, pull action items from the transcript or notes and update your to-do file. ## Trigger `/meeting-todos` — optionally followed by a meeting title or date, e.g.: - `/meeting-todos` → uses the most recent meeting note - `/meeting-todos 2026-04-09` → finds meeting from that date - `/meeting-todos Team Sync` → finds meeting matching that title ## First-run config On first invocation, look for `[VAULT]/.meeting-todos-prefs.md`. If it doesn't exist, ask the user: 1. **Meeting notes folder:** Where do meeting notes live? (default: `Meeting Notes/`) 2. **To-do file path:** Where should action items go? (e.g. `TODO.md`, `tasks.md`, `Home/To-do.md`) 3. **Meeting source integration (optional):** Do you have a meeting notes integration like Granola, Otter, or Gemini Notes saving to a Google Doc? If yes, what's the source folder or doc path? If no, skip — just read meeting notes from the local folder. Save preferences to `[VAULT]/.meeting-todos-prefs.md` as a single markdown file with frontmatter. Don't ask again on future runs. ## Step 1 — Find the meeting note Check the configured `meeting_folder` (or any team meeting folder if set) for the most recent (or matching) meeting note. If the user specified a date or title, find the matching file. If no argument, use the most recently modified file. Tell the user which file you found before proceeding. ## Step 2 — Read the meeting Read the full meeting note. It may contain: - A **Notes**