mem-file-scan_skill

Overview

This skill scans an Obsidian vault for files modified during the current week (excluding the AI_MEMORY directory and other system folders) and surfaces potential events, decisions, habits, and preferences worth saving to the L1 context layer. It lists changed files, lets you pick which to analyze, extracts candidate records, and helps record confirmed items via the mem-record skill. The goal is to capture non-conversational activities you performed in Obsidian so your memory system stays complete.

How this skill works

The skill computes the week range, runs a file-modification scan (using find with -newermt) to locate .md files while excluding AI_MEMORY, .obsidian, .trash, .claude and hidden directories, and groups results by note type (Daily, Projects, Learning, etc.). It then presents the list, asks which files to process, reads selected files, detects candidates (decisions, emotions, new projects, repeats, preferences, unfinished tasks), and prompts you to confirm, modify, or skip each candidate before invoking mem-record to save confirmed items to L1.

When to use it

• You say: "file scan", "show this week files", or "scan file changes"
• At the start of a weekly review to supplement L1 before analysis
• When you want to review your Obsidian activity for the week
• If you suspect important decisions or tasks were only noted in files
• When consolidating project progress or habit changes into memory

Best practices

• Run the scan early in weekly review so L1 includes file-driven context
• Exclude AI_MEMORY and system folders to avoid duplicate or irrelevant data
• Start with Daily and Project folders to prioritize likely important items
• Skip trivial notes; focus on decisions, emotions, new projects, repeats, and pending tasks
• Review and edit candidate records before saving to keep L1 concise and accurate

Example use cases

• You finished a feature and logged progress in Projects/ProjectA/notes.md — surface that as a completed milestone
• You wrote about feeling anxious about a deadline in a Daily note — capture the emotion and related decision
• You added resources for a new topic under Learning — record a new interest or research intent
• During weekly review, discover several recurring tasks across days and convert into a habit or pattern note
• Detect a documented tooling decision in a meeting note and record it as an explicit architectural choice