Claude Meeting Todos
adelaidasofia/claude-meeting-todos
Captura ações de reuniões direto para seu to-do
Ver no GitHubExtrai itens de ação de notas ou transcrições de reuniões e os adiciona automaticamente ao seu arquivo de tarefas. Separa suas atribuições das de outros participantes, marca decisões pendentes e pede confirmação antes de escrever.
Instalação
npx convez-ai adelaidasofia/claude-meeting-todos1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Converter notas de reunião em tarefas estruturadas
- Evitar perda de ações atribuídas em transcrições
- Separar itens pessoais de responsabilidades de terceiros
- Rastrear decisões pendentes pós-reunião
Veredito

Skill prático que resolve um problema real: ações perdidas entre notas e listas de tarefas. Requer pasta de reuniões estruturada, mas uma vez configurado, poupa tempo significativo de triagem manual e reduz itens esquecidos.
README
A tradução para o português deste README ainda está na fila.
claude-meeting-todos
A Claude Code plugin that extracts action items from meeting notes or transcripts and adds them to your to-do file. Separates your tasks from others' tasks, flags pending decisions, and confirms before writing.
What it does
After a meeting, you run /meeting-todos. The skill:
- Finds the most recent meeting note (or one you specify by date/title)
- Reads the notes or transcript
- Extracts your action items, separates them from others' tasks, and flags decisions still pending
- Shows you a preview and waits for confirmation
- Appends the items to your to-do file in the format you already use
The point is to never lose an action item to "I'll write that down later" — and to never let the conversation die in a notebook nobody opens.
Install
Open Claude Code, paste:
/plugin marketplace add adelaidasofia/claude-meeting-todos
/plugin install claude-meeting-todos@claude-meeting-todos
Then in any Claude Code session:
/meeting-todos
On first use, Claude asks where your meeting notes live and where your to-do file is. Takes 30 seconds, never asks again.
claude plugin add github.com/adelaidasofia/claude-meeting-todos
Requirements
- Claude Code
- A folder where meeting notes are saved as markdown
- A to-do file (any format)
Optional integrations:
- Google Workspace MCP — pull from Google Docs (e.g. Gemini Notes meeting transcripts)
- Granola, Otter, Fireflies, Read.ai — any tool that exports markdown to a folder works the same way
- The daily-journal plugin — if installed, action items can also flow into your journal's accountability check
Configuration
On first use, preferences are saved to [VAULT]/.meeting-todos-prefs.md:
meeting_folder: Meeting Notes/
todo_path: TODO.md
meeting_source_integration: none
Edit this file anytime to change your setup.
How action items are extracted
Your tasks — anything where you were directly assigned, volunteered, or own the follow-up.
Others' tasks — assigned to someone else. Listed for visibility, NOT added to your to-do.
Decisions pending — unresolved questions surfaced for follow-up.
The skill writes them in the format your to-do file already uses (sectioned by meeting), without duplicating items already present and without reordering anything.
Why a separate skill (vs. a generic to-do tool)
Most to-do tools assume the input is already a clean list. Meetings produce mush — half-decisions, side comments, "let me check on that," "we should..." Without a discrete extraction step, those items either get dropped or get filed as one-line orphans nobody understands later.
This skill makes the extraction visible: you see what got pulled before it lands in your to-do, and the items are sectioned by meeting so context isn't lost.
Submitting to the Cowork marketplace
Once the repo is on GitHub, submit at: clau.de/plugin-directory-submission
For the community marketplace:
claude plugin marketplace add anthropics/claude-plugins-community
Telemetry
This plugin sends a single anonymous install signal to myceliumai.co the first time it loads in a Claude Code session on a given machine.
What is sent:
- Plugin name (e.g.
slack-mcp) - Plugin version (e.g.
0.1.0)
What is NOT sent:
- No user identifiers, names, emails, tokens, or API keys
- No file paths, message content, or anything from your work
- No IP address is stored after dedup processing
Why: Helps the maintainer know which plugins people actually install, so attention goes to the ones that get used.
Opt out: Set the environment variable MYCELIUM_NO_PING=1 before launching Claude Code. The hook will skip the network call entirely. Already-pinged installs leave a sentinel at ~/.mycelium/onboarded-<plugin> — delete it if you want to reset state.
License
MIT