memory-distill

Memory Distill

Distill raw DailyActivity logs into curated MEMORY.md entries. This skill runs automatically and silently — never announce, never ask permission.

1. Detection

Scan Knowledge/DailyActivity/*.md for unprocessed files:

1. List all .md files in Knowledge/DailyActivity/
2. For each file, read the YAML frontmatter (delimited by --- lines at the top)
3. A file is unprocessed if it has no frontmatter OR lacks distilled: true
4. Count unprocessed files
5. If count ≤ 3, exit silently — not enough material to distill

Do not announce the scan or its results.

2. Extraction

For each unprocessed DailyActivity file, extract:

• Key decisions — Architecture choices, tool selections, approach changes
• Lessons learned — What worked, what didn't, debugging insights
• Recurring themes — Patterns across multiple sessions
• User corrections — Times the user corrected your output or approach
• Error resolutions — Problems encountered and their fixes

Skip one-off observations, transient context, and information already captured in KNOWLEDGE.md or other context files.

3. Writing to MEMORY.md

Write distilled content to the appropriate sections of MEMORY.md:

1. Use the Edit tool for all MEMORY.md writes — never use python3 locked_write.py via Bash (crashes in PyInstaller bundles). Always prefix entries with the source DailyActivity date (not today's date). Read .context/MEMORY.md, find the target section, and prepend the new entry at the top of the section (after the ## heading). Format: - YYYY-MM-DD: <distilled entry>

2. Map extracted content to MEMORY.md sections:

   • Key decisions → ## Key Decisions
   • Lessons learned → ## Lessons Learned
   • Recurring themes → ## Patterns and Preferences
   • User corrections → ## Lessons Learned
   • Error resolutions → ## Lessons Learned
   • Current work status → ## Recent Context
   • Open thread updates → ## Open Threads

3. Fallback: If a target section is not found (user may have renamed or removed it), add a new ## Distilled section at the end of the file and write there.

4. Never remove existing MEMORY.md content — only prepend or append to sections

5. Keep entries concise: one line per decision/lesson, date-prefixed, grouped by theme

6. Deduplication: Before writing, check if the same content (ignoring date prefix) already exists in the target section. Skip duplicates.