vault-intake-curation
Use when handling raw sources, imported material, NotebookLM outputs, quick captures, or working-note restructuring inside a governed Obsidian vault. Applies when the task belongs to intake or curatio
Files2
View on GitHubSKILL.mdskills/vault-intake-curation/SKILL.md
GitHubVault Intake And Curation
Overview
This skill handles the working part of the vault: capturing raw material, normalizing structure, and curating draft knowledge without crossing into canonical space.
Use For
- source imports
- NotebookLM landing notes
ProjectRaw/updates- topic-folder cleanup
- draft synthesis and topic indexes
Do Not Use For
- direct canonical publication
- archive decisions
- topic merge decisions that require coordinator authority
Workflow
- Confirm target
topic_id - Confirm target layer is
intakeorcuration - Check registry for existing objects
- Update or create files in working layers
- Preserve source references
- Log important changes
- If the result looks long-lived, submit a promotion candidate instead of self-promoting
Read references/intake-checklist.md for the checklist.
Required Outputs
- updated file path
- preserved source lineage
- registry-consistent topic linkage
- ledger entry for meaningful changes
Common Mistakes
- moving raw notes into canonical directories
- dropping source references during cleanup
- restructuring topic folders without updating registry
- silently changing topic identity