wiki-capture

To save a conversation as a permanent knowledge note in Obsidian, this Skill extracts the core substance, rewrites it declaratively, and generates a structured markdown note with frontmatter and internal wikilinks. It categorizes the content and routes it to the correct vault folder.

Converting chat history into declarative wiki notes requires extracting the substantive information rather than saving a transcript. This process rewrites the discussion into factual statements suitable for future reference and retrieves existing context to avoid duplicating knowledge.

Content classification for wiki capture works by sorting the extracted conversation into categories like synthesis, concepts, references, decision rationale, or session journal entries. This determines the correct Obsidian vault folder for the generated markdown note.

Yes, you can capture technical procedures and decision rationale from a chat. The Skill is designed for scenarios where you need to preserve decisions, frameworks, external-source summaries, and multi-topic discussions for later retrieval in your vault.

Yes, wiki capture prevents duplicate notes by reading existing index and recent-activity context before writing. This deduplication process aligns the new note with the current wiki structure to ensure no overlapping knowledge is saved.

Yes, you need to resolve configuration for the vault path and link format before capturing notes. This vault-aware formatting ensures the Skill writes markdown notes with consistent internal linking and correct placement.