--- name: pkm-curation description: Curate an Obsidian-style personal knowledge vault by classifying notes, normalizing frontmatter, improving structure, extracting atomic notes, and adding meaningful wikilinks. disable-model-invocation: true --- # PKM Curation Use this skill when working inside a Markdown-first vault that values curation over collection. ## Goals - Turn raw notes into clear, reusable notes. - Keep new notes consistent with vault conventions. - Strengthen the link graph with meaningful `[[wikilinks]]` syntax `[[Note Title]]`. - Extract atomic notes from long or mixed-topic notes. - Avoid unnecessary reorganization and weak links. ## Read This First - Read `AGENTS.md` in the current repo scope before editing notes. - Read `references/vault-conventions.md` when normalizing metadata, deciding note types, or choosing folders. - Read `references/agent-integration.md` when running this skill through an agent. - Keep changes small and reviewable. - Keep file operations local to the vault unless the user explicitly asks otherwise. ## Workflows ## Search for notes ```bash # Search by filename fd --type f ".md" "path/to/obsidian-vault" | rg -i "keyword" # Search by content rg -l "keyword" "path/to/obsidian-vault" --include "*.md" ``` ## Curate existing note 1. Inspect the target note or note set. 2. Identify the note type: inbox, source, atomic, project, daily, or reference. 3. Normalize frontmatter and basic structure. 4. Clarify the title if the current one is vague or timestamp-like. 5. Summarize or distill the note if it mixes too many ideas. 6. Add or suggest meaningful `[[wikilinks]]` to related notes. 7. If a note contains multiple durable ideas, extract 1-3 atomic notes. 8. Suggest moving the note only if the destination is clearly better. ## Find related notes Search for `[[Note Title]]` across the vault to find backlinks: ```bash rg -l "\\[\\[Note Title\\]\\]" "path/to/obsidian-vault" --include "*.md" ``` ### Find index notes ```bash fd --type f "Index" "path/to/obsidian-vault" ``` ## Operating Rules - Prefer reorganization over curation. - Do not move, rename, or delete many notes at once unless the user asks. - Do not invent links based only on shared words. - Preserve the user's voice unless the user asks for a rewrite. - Keep source material and evergreen ideas separate when possible. - Treat `Inbox/` as temporary capture, not long-term storage. - Preserve all command blocks, code snippets, configuration directives, and step-by-step instructions verbatim. Do not summarize or condense them. - For reference/source notes: add a brief overview at the top, but keep the original commands and details intact below. Completeness > brevity. - Read every file completely before editing. Do not rely on head/tail, heading-only scans, or partial reads to judge a file's content. - For any file you plan to move, rename, or modify, run `cat` on the full file first. Only then decide what stays, what moves, and what changes. ## Note-Type Heuristics ### Inbox note Use when the note is raw capture, partial thinking, copied text, or an unprocessed link dump. Actions: - clean obvious structure issues - add frontmatter if missing - classify for later promotion - avoid over-polishing unless requested ### Source note Use when the note is based on an article, video, book, paper, transcript, or other external material. Actions: - keep source context intact - summarize key takeaways - extract reusable ideas into separate atomic notes - link to related concepts and projects ### Atomic note Use when the note captures one durable idea, concept, claim, pattern, or insight. Actions: - ensure one main idea per note - make the title concept-focused - add links to neighboring ideas - keep it concise and self-contained ### Project note Use when the note supports active work, planning, resources, decisions, or tasks. Actions: - preserve project context - link tasks to the project note - avoid turning active project logistics into evergreen notes unless there is a reusable insight ### Daily note Use when the note is date-based and captures activity, learning, tasks, or reflection for a single day. Actions: - preserve chronology - link out to durable notes rather than stuffing ideas into the daily note ## Linking Guidance Add links only when they express one of these relationships: - concept to broader concept - source note to extracted idea - project note to relevant knowledge note - daily note to work done or ideas learned - sibling concepts that genuinely inform one another When linking, prefer existing notes over creating speculative new ones. ## Extraction Guidance Extract atomic notes when a note contains: - multiple durable ideas - a strong claim hidden in raw notes - a reusable method, distinction, or definition - a concept that should be linked from many places Keep extracted notes short. One note, one idea. ## Common Tasks ### Curate one note - inspect the note - identify note type - normalize frontmatter - tighten headings and summary - add a few strong links - suggest extracted atomic notes if warranted - locate the target file in the vault - inspect nearby related notes before adding links - patch the note in place - return a short summary of edits and suggested follow-up notes ### Curate an inbox batch - process a small batch, usually 5-10 notes - classify each note - normalize metadata - suggest which notes should stay raw, become source notes, or become atomic notes - avoid large folder reshuffles unless the pattern is clear - enumerate a small set of `Inbox/` notes - process them one at a time - stop and summarize after each batch ### Review recent notes - inspect recently edited notes - identify missing links and vague titles - flag notes with mixed concerns - suggest a small set of follow-up curation actions - search by recent filenames or recent folders when file metadata is available - keep edits conservative and return a review summary ### Serendipity review - choose a note from the vault - summarize it briefly - compare it to the user's current topic or active project - suggest only high-confidence connections - pick one note from a user-specified folder or from curated folders only - avoid randomizing across obviously raw capture unless the user asks for that ## Output Style When responding to the user: - state what kind of note you think it is - summarize the curation changes you made or recommend - list any extracted notes to create - list meaningful links added or suggested - mention any move or rename separately before doing it - name the file or files touched - separate completed edits from suggested next actions - call out anything that still needs user confirmation ## If You Need More Context If the vault structure is unclear, inspect folders and a few nearby notes before editing. If note conventions appear to conflict, follow the most local `AGENTS.md` instructions in scope. Don't guess at user preferences. When in doubt, ask the user before making big changes or suggesting speculative links.