Curate the Basic Memory knowledge graph: find orphan notes and suggest links, propose typed relations, merge duplicates, audit tags and folders, and build hub notes. Use to organize, connect, and improve a knowledge base as notes accumulate.

Memory Curate Maintain a healthy, well connected knowledge graph. As notes accumulate, it pays to periodically organize, link, and curate the knowledge base so isolated notes become a connected graph. This skill curates the knowledge graph — the notes, relations, and tags that make up the knowledge base. (For hygiene on an agent's own memory files — splitting bloated files, pruning stale entries — see memory defrag .) When to Use Asked to organize, clean up, or improve the knowledge base Asked to find connections between notes, or what isn't linked yet Orphan or unlinked notes are mentioned Asked about duplicate or similar notes Asked for help with folder organization or tag consistency Phrases like "help me organize", "find related notes", "what's not linked", "clean up my notes" Curation Capabilities 1. Find Orphan Notes Orphans have no relations to other notes — they're islands in the graph. What to do with orphans: Suggest relations based on content similarity Ask whether they should connect to existing topics Propose hub notes to gather related orphans (see capability 6) 2. Suggest Typed Relations Analyze a note's content and propose meaningful connections. Suggest relations based on shared topics, complementary content (problem/solution, question/answer), sequence (part 1 → part 2), or hierarchy (parent concept → detail). Relation type vocabulary: relates to — general topical connection extends — builds upon or elaborates implements — realizes a concept or spec depends on — requires understanding of part of — hierarchy or composition contrasts with — presents an alternative view inspired by — source of insight enables — makes something possible Custom relation types are fine — use whatever verb is descriptive. Add a confirmed relation with edit note : 3. Identify Similar / Duplicate Notes Find notes that may cover the same ground. Actions for duplicates: Merge into a single comprehensive note, then redirect the loser with a relation Link with supersedes / updates when one revises the other Differentiate by adding context that clarifies each note's distinct focus 4. Folder Organization Review Look for overcrowded folders, single note folders, inconsistent naming, and notes that belong elsewhere. Suggest grouping related notes into topic folders, adding subfolders for large categories, and a consistent naming convention. Move misplaced notes with move note — the permalink stays stable, so wiki links keep resolving. 5. Tag Consistency Look for: Variant tags — architecture vs arch ; pick one and standardize Unused tags — present on a single note, no longer carrying weight Over used generic tags — so broad they don't aid discovery Missing tags — relevant notes lacking an obvious tag 6. Create Index / Hub Notes After finding a cluster of related notes, build a navigation hub. 7. Enrich Sparse Notes Find notes lacking structure and fill them in. If the note is missing an Observations section, suggest categories. If it has no Relations, suggest links. If it has no tags, suggest relevant ones. If it lacks context, suggest adding background. Apply with edit note . Curation Workflows Quick Health Check A fast overview of knowledge base status: 1. Count total notes 2. Identify orphan count 3. List recently modified ( recent activity ) 4. Check for obvious duplicates 5. Report folder distribution Deep Organization Session Thorough review and improvement: 1. Audit — catalog all notes, identify issues 2. Orphans — address unlinked notes 3. Relations — suggest new connections 4. Duplicates — merge or differentiate similar notes 5. Structure — reorganize folders if needed 6. Index — create hub notes for major topics Topic Focused Organization Organize around a specific subject: 1. Find all notes related to the topic ( search notes ) 2. Map existing relations with build context(url="memory://...") 3. Identify gaps in the topic graph 4. Suggest new notes to fill them 5. Create a topic index note Best Practices 1. Work incrementally. Don't reorganize everything at once. 2. Confirm before changing. Always ask before moving, merging, or editing notes. 3. Preserve permalinks. Moving a note is fine; changing its permalink breaks inbound links. 4. Explain suggestions. Say why a relation or merge makes sense. 5. Respect the existing system. Enhance the user's organization — don't impose a new taxonomy. 6. Show the graph. Use build context to help the user see how notes connect. Example Conversations User: "Help me organize my notes" The assistant: 1. Runs a health check on the knowledge base 2. Reports: "You have 47 notes. I found 12 orphans and 3 potential duplicates." 3. Asks: "Want to start by connecting the orphans, or review the duplicates first?" User: "Find notes that should link to my API design note" The assistant: 1. Reads the API design note 2. Searches for related content 3. Suggests: "5 notes could relate — 'REST Best Practices' → relates to 'Authentication Flow' → implements 'Rate Limiting Decision' → extends Should I add any of these relations?" User: "Are there notes on similar topics?" The assistant: 1. Analyzes titles and content for clusters 2. Reports: "Possible overlaps — 'Auth Flow' and 'Authentication Design' cover similar ground 'DB Schema v1' and 'DB Schema v2' likely want a supersedes relation Want to review either?"

memory-curate