agentleFS
mycelium-hqmycelium-hq/ai-brain-starter/skills/meeting-todos/SKILL.md

meeting-todos

Skill50 starsChanged 7 months agoMITView on GitHub

Use when the user says /meeting-todos, "the meeting is done", "I just had a meeting", "pull the action items", "what did I commit to", or otherwise wants action items from a recent meeting note captured on their to-do list. Also when a meeting note or transcript needs its tasks pulled out. NOT for general task management, journaling, non-meeting notes (use note-todos), or pulling full meeting transcripts.

The file

Show its rules and text

We split this skill into the rules it gives an agent

18 rules. About 0 are common, 16 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈16

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After a meeting, pull action items from the transcript/notes and update your to-do file.

    line 9
  2. Distinctive:

    Check these locations for the most recent (or matching) meeting note:

    line 49
  3. Distinctive:

    If the user specified a date or title, find the matching file.

    line 62
  4. Distinctive:

    Read the full meeting note.

    line 68
  5. Distinctive:

    Wait for confirmation before writing.

    line 108
  6. Distinctive:

    Use the to-do file path resolved (or created) in Step 0.

    line 112
  7. Distinctive:

    Read the file first to understand current structure

    line 115
  8. Distinctive:

    Add a new section or append to the most relevant existing section

    line 116
  9. Distinctive:

    Use this format for the new items:

    line 117
  10. Very specific:

    Place it after ## 🔥 Urgent / Active if the tasks are urgent, or at the bottom if they're not.

    line 126
  11. Distinctive:

    Do NOT duplicate tasks already in the file

    line 128
  12. Distinctive:

    Do NOT delete or reorder existing tasks

    line 129
  13. Very specific:

    Update the updated: field in frontmatter to today's date if it exists

    line 130
  14. Distinctive:

    If the meeting note did NOT already have a structured summary, add one at the top of the meeting file (above the Transcript section):

    line 134
  15. Distinctive:

    Ask the user if they want this added before writing.

    line 147
  16. Distinctive:

    Always confirm before writing to to-do

    line 151
  17. Distinctive:

    If a meeting had no clear action items, say so — don't invent tasks

    line 155
  18. Distinctive:

    NEVER fail silently: If the meeting file doesn't exist or can't be read, tell the user immediately

    line 156

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Meeting → To-Do Extractor

After a meeting, pull action items from the transcript/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

Step 0 — Locate (or create) the to-do file

Run this first, before searching for the meeting note. A fresh-install vault may not have a to-do file yet, and you don't want to do all the extraction work only to discover at Step 5 that there's no destination.

  1. Try the common paths first (fastest — one Glob or Read per location, stop on the first hit):
    • 🏠 Home/✅ Get to-do.md (canonical layout)
    • Home/✅ Get to-do.md
    • ✅ Get to-do.md (vault root)
    • Home/TODO.md / TODO.md / tasks.md
  2. If none of those exist, read the user's vault CLAUDE.md for a vault-map / to-do location hint. If the hint resolves to an existing file, use it and proceed to Step 1.
  3. If still nothing, ASK the user before creating anything:

    I don't see a to-do file in your vault. Want me to create 🏠 Home/✅ Get to-do.md with a basic structure (frontmatter + Inbox section) so the meeting items have somewhere to land? You can move or rename it later.

  4. On yes, create the file with this canonical structure (replace YYYY-MM-DD with today's date in both places):
    ---
    type: todo
    created: YYYY-MM-DD
    updated: YYYY-MM-DD
    ---
    
    # To-do
    
    ## Inbox
    Tell the user where you put it, then proceed to Step 1.
  5. On no, stop here. Don't extract action items from a meeting you can't file anywhere; that's silent-no-op territory. Tell the user /meeting-todos needs a destination file and ask them to create one (or point you at where their tasks live) before re-running.

Cache the resolved to-do path mentally for Step 5 — don't re-search the filesystem there.

Step 1 — Find the meeting note

Check these locations for the most recent (or matching) meeting note:

  • $AI_BRAIN_MEETING_NOTES_DIR if it is set — a colon-separated list of folder names the user has already told the substrate about. When it is set it is AUTHORITATIVE: scripts/write-hook.sh matches on exactly these and ignores the English defaults, so honoring it here keeps the two halves of the cascade pointed at the same folder.
  • [VAULT]/Meeting Notes/ or [VAULT]/Meeting-Notes/ (the English defaults)
  • The same folder in the user's own language — Reuniones/, Réunions/, 会議/. Do NOT search only the English names: a Spanish or French vault keeps meetings under its own word, and matching English-only is a silent no-op that looks identical to "you have no meetings".
  • Any team vault meeting notes folder if configured

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 or Summary section (structured — prioritize this)
  • A Transcript section (raw — extract from this if no summary)

Step 3 — Extract action items

From the content, identify:

Your tasks — anything where:

  • You were directly assigned ("You will...", "I'll...", your name + action)
  • You volunteered ("I'm thinking...", "let me...")
  • It requires your decision or follow-up ("we need to define X" where you're the one with context)
  • You said you'd research or provide something

Commitment cues are language-specific, so listen for them in the language actually spoken. Spanish first-person commitments read as "me toca...", "voy a...", "yo lo hago", "yo me encargo", "quedo de...". A transcript can be bilingual within one sentence; catch the cue in whichever language it appears.

Others' tasks — anything assigned to someone else — list these separately for visibility but DO NOT add to your to-do.

Decisions pending — anything that was left unresolved and needs a meeting or decision soon.

Step 4 — Confirm before writing

Show the user a preview:

## From: [Meeting Name] — [Date]

### Your action items (going to to-do):
- [ ] [task 1]
- [ ] [task 2]

### Others' tasks (not going to to-do — just FYI):
- [Name]: [task]

### Open questions / decisions pending:
- [item]

Shall I add these to your to-do? (yes/no, or edit first)

Wait for confirmation before writing.

Step 5 — Update to-do

Use the to-do file path resolved (or created) in Step 0. Do NOT re-search the filesystem — you already did that.

Rules:

  • Read the file first to understand current structure
  • Add a new section or append to the most relevant existing section
  • Use this format for the new items:
## 📋 From [Meeting Name] — [Date]

- [ ] [task 1]
- [ ] [task 2]

Place it after ## 🔥 Urgent / Active if the tasks are urgent, or at the bottom if they're not.

  • Do NOT duplicate tasks already in the file
  • Do NOT delete or reorder existing tasks
  • Update the updated: field in frontmatter to today's date if it exists

Step 6 — Save meeting summary (optional)

If the meeting note did NOT already have a structured summary, add one at the top of the meeting file (above the Transcript section):

## Summary

**Date:** [date]
**Attendees:** [names]
**Key decisions:** [bullet points]
**Your action items:** [bullet points]
**Others' action items:** [bullet points]
**Next steps:** [bullet points]

Ask the user if they want this added before writing.

Rules

  • Always confirm before writing to to-do
  • Transcripts in any language are fine — extract in the language of the meeting, or match the user's preference
  • Be specific: "Research optimal response time for our target market" not "Do research"
  • Include context in the task where helpful: "Discuss referral API payload with John (what data to send when hotel can't take event)"
  • If a meeting had no clear action items, say so — don't invent tasks
  • NEVER fail silently. If the meeting file doesn't exist or can't be read, tell the user immediately

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.