← ClaudeAtlas

note-todoslisted

Extract action items from any non-meeting note (class notes, book notes, podcast notes, transcripts, panel writeups) and route them to the scope-correct to-do file with wikilinking and per-task owner tags. Generalization of meeting-todos. Trigger with /note-todos [filename-or-pattern]. For meetings, prefer /meeting-todos which carries the full meeting workflow cascade.
adelaidasofia/ai-brain-starter · ★ 18 · AI & Automation · score 81
Install: claude install-skill adelaidasofia/ai-brain-starter
## What this skill does Action items hide in notes you don't think of as task lists. A class note, a book chapter, a podcast transcript, a panel writeup — each one accumulates "I should do X" between the substantive content. Without a routing pass, those items stay invisible until weeks later when you wonder why nothing got done. This skill does the routing pass. It reads a note in full, extracts every actionable item, decides which scope each task belongs to (personal / team / consulting / etc), wraps entities in wikilinks, tags owners inline, writes to the correct canonical to-do file, and annotates the source note so future reads know the items have been ported. It is the non-meeting counterpart to `/meeting-todos`, which carries the 8-step meeting workflow cascade (transcript fetch, speaker attribution, decision capture, etc) on top of the same extraction logic. If the input is a meeting, route to `/meeting-todos` instead. ## Trigger `/note-todos` — optionally followed by a path, filename, or keyword: - `/note-todos` → finds candidate notes in recent activity (modified within 14 days, contain 3+ open `- [ ]` items, no "filed-on" annotation at the section head) - `/note-todos {keyword}` → globs for notes matching keyword in filename or first 200 chars of body - `/note-todos {full-path-to-note.md}` → opens the exact file Tell the user which file you found before proceeding. ## Step 1 — Read the note in full Always read the entire note. Action items can appear: - Inl