一键导入
extract-todo
Extracts action items from content and routes to project-specific TODO files. Used by ingest-brain-dump when TODOs are identified in brain dumps.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Extracts action items from content and routes to project-specific TODO files. Used by ingest-brain-dump when TODOs are identified in brain dumps.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Seed a brain from a LARGE existing source by TRIAGING it, then calibrating the agent's judgment on small batches, then bulk-mining. Use when the owner says "mine my [source]", "mine this export", "calibrate the mining", "idea mining", "process my archive", or "seed my brain from this export" — pointing at a sizable export (notes-app dump, chat history, voice-note archive, bookmarks, podcast snips). Phase 0 TRIAGE: categorize the source into keep/skip bins, sample the skip-bins, get owner approval per bin, build the target list. Phase 1 CALIBRATE: small batches → present COMPACT numbered proposals (verbatim quote + the agent's call + one-line reason, no tables) → owner corrects → write every correction back into the rules (CONTENT_TAXONOMY / KEYWORD_GUIDE / INTELLECTUAL_LANDSCAPE) → draft the full Template only after the calls are approved → repeat until a batch is clean. Phase 2 SET LOOSE: process the remainder autonomously, spot-check, re-calibrate on drift. Implements "invest in structure and calibrate the
Onboard a human into THEIR own second brain — the guided interview that turns this blank template into their personalized system. Use when the user says "set this up", "let's set it up", "set up my second brain", "personalize", "personalise", "make this mine", "onboard me", "help me fill this in", "walk me through PERSONALIZE", or starts a fresh session wanting to begin. Drives the whole __FILL_FROM_USER__ fill-in via an interview. Resumable — pick up where you left off. NOT for ingesting content (use /ingest-brain-dump) — this is first-run setup.
Handles connections between related ideas. Options include creating folders, adding shared keywords, merging content, or rejecting false positives. Used when ingest-brain-dump identifies related content.
Weekly self-improvement of the HARNESS itself — not project QA. Reviews the last N days of this brain's Claude Code session traces for harness-level friction (where the owner corrected the agent, repeated permission prompts, skills that misfired or weren't used, rules/memories the agent ignored, weak sub-agent prompts), drafts a proposal of findings, and the owner reviews + applies it finding-by-finding (gated — nothing auto-applies). Uses the in-session Workflow tool to fan out over trace chunks; no external services, no API keys. Use when the owner says "/harness-review", "review the harness", "self-review", "what's the agent getting wrong", or accepts the optional offer at the end of /weekly-maintenance.
Full orchestrator for stream-of-consciousness input pasted or dictated into the Claude Code session. Pipeline: explore-second-brain (find related files) → semantic segmentation → verify-idea (dedupe check) → process-content (create Template A files) → validate_template.py → user approval → save. Use when user pastes unstructured text or dictates a voice note into chat and says "brain dump", "process this", "ingest this", "save this", "what should we do with this". One paragraph may contain 3 ideas; 5 paragraphs may be 1 idea — always semantic, never algorithmic chunking. NOT for phone inbox (use a phone-inbox ingest skill if configured). NOT for podcast snips (use a snip-processing skill if configured). NOT for bookmark exports (use a bookmarks-ingest skill if configured). For a LARGE existing source export (notes-app dump, chat history, voice-note archive), use /mine — it triages the source, then calibrates the agent's judgment on small batches before the bulk pass. Preserves the owner's exact language — no
Low-level mechanic that turns raw text into Template A/B files. Segments semantically (never algorithmic chunking), classifies each segment, creates files, runs validate_template.py. Does NOT sync from external sources — text must already be in context. Called by the ingestion skills (e.g. /ingest-example) as their file-creation stage; can also be invoked directly when user pastes content and says "make files from this", "turn this into Template A", "parse this into ideas". NOT for voice/phone inbox work (use an inbox-ingest skill), NOT for searching the brain (use explore-second-brain or semantic-search). If input has multiple distinct ideas, all are processed in one invocation.
| name | extract-todo |
| description | Extracts action items from content and routes to project-specific TODO files. Used by ingest-brain-dump when TODOs are identified in brain dumps. |
Identifies and extracts action items from content, formats them properly, and routes to the appropriate project TODO file.
Called by ingest-brain-dump when content contains action items. Can also be invoked directly with /extract-todo.
Before extracting TODOs, ensure access to:
Content containing one or more action items (explicit or implicit).
Look for:
Route each TODO to the appropriate project's folder (TODOs are now distributed).
| Content Type | Location |
|---|---|
| FILL_FROM_USER:project_1 related | Projects/__FILL_FROM_USER__:project_1/TODO___FILL_FROM_USER__:project_1.md |
| FILL_FROM_USER:project_2 related | Projects/__FILL_FROM_USER__:project_2/TODO___FILL_FROM_USER__:project_2.md |
| Database/Second Brain work | Orientation_Docs/TODO_Second_Brain.md |
| Inventions (Bits/Atoms) | Inventions/TODO_Inventions.md |
| Personal tasks/Habits/Learning | Journal_Personal/TODO_Personal_Effectiveness.md |
| Other writing | Writing_AllElse/TODO_Writing_Other.md |
| General/unclear | Orientation_Docs/TODO_Miscellaneous.md |
- [ ] [Action item text] (Source: [date or brain dump ref])
Add directly to the appropriate file in the project's folder (see Step 2 for locations).
Find the appropriate section within that file and add the item.
## TODO Extracted
**Action:** [brief description]
**Project:** [project name]
**Added to:** Project_TODOs/TODO_[Project].md
Input: "I need to research a researcher's work on a topic and reach out to them about a project idea"
Output:
- [ ] Research [researcher]'s work on [topic] (Source: Dec 25 brain dump)
- [ ] Draft outreach message to [researcher] about [project concept] (Source: Dec 25 brain dump)
Added to: Projects/__FILL_FROM_USER__:project_name/TODO___FILL_FROM_USER__:project_name.md → Outreach section
TODOs now live in their project folders. Populate this list to match your routing table above:
__FILL_FROM_USER__:project_1_todo_path - FILL_FROM_USER:project_1_description__FILL_FROM_USER__:project_2_todo_path - FILL_FROM_USER:project_2_descriptionOrientation_Docs/TODO_Second_Brain.md - Database work (meta)Inventions/TODO_Inventions.md - Bits + Atoms ideasJournal_Personal/TODO_Personal_Effectiveness.md - Habits, learning, skillsWriting_AllElse/TODO_Writing_Other.md - Other creative writingOrientation_Docs/TODO_Miscellaneous.md - UncategorizedCalled by: ingest-brain-dump (Step 3 - Route TODOs)