File valuable conversation outputs as permanent vault notes and update the changelog. Use when a conversation produced a synthesis, analysis, comparison, decision rationale, research summary, narrative account, or discovery worth preserving. Triggered by the Stop hook reminder, by the user saying "file this", "save this conversation", "remember this", or at agent discretion when a response deserves to outlive chat history.
Capture valuable conversation outputs as permanent notes in the vault and log what happened, so that insights compound rather than disappearing into chat history.
Each session can produce up to two outputs. Decide which combination fits based on what happened.
Always append to .config/obsidian-knowledge/CHANGELOG.md if the
session produced anything substantive — edits, decisions, discoveries,
dead ends. Keep entries terse (one line per action) and link out to
session notes for detail rather than documenting inline. Follow the
format defined by the vault-organizer skill. Skip if nothing meaningful
happened or you already logged.
Create a session note when the conversation produced something a future agent or the user would benefit from finding later. There are two types:
-diary suffix) — narrative accounts: what happened, what
was tried, what worked or didn't, and why. Use for processes, incidents,
debugging sessions, migration stories, or any sequence of events worth
retelling.-convoA session can produce both types if it involved a notable process AND yielded a separable analytical insight.
Do not create session notes for:
Every session note follows this structure:
# {Descriptive title}
## Context
{What prompted this — the question, task, or trigger. 1-2 sentences.}
## {Body}
{The narrative or analysis. Section heading and structure should fit
the content — "What happened" for diaries, "Analysis" or "Comparison"
for convos, etc. As long as it needs to be.}
## Key takeaways
- {Concise bullets summarizing actionable or memorable points}
## Related
- [[wikilinks to relevant vault pages]]
Adapt sections to fit — not every note needs every section.
Session notes go in a sessions/ subfolder within the relevant subtree:
area/topic/
├── _sources/
├── sessions/
│ ├── index.md
│ ├── 2026-04-05-deduction-analysis-convo.md
│ └── 2026-04-06-tax-filing-process-diary.md
├── index.md
└── ...
Place the note in the most specific subtree that covers its topic. If a conversation spans multiple domains, choose the primary one and add wikilinks to the others in the Related section.
Follow the vault's CLAUDE.md for naming style. If no convention is
defined, default to YYYY-MM-DD-{slug}-{type}.md where {type} is
diary or convo. The -{type} suffix is always required regardless
of the vault's naming style.
Determine the subtree — identify where session notes belong based on topic.
Create sessions/ if needed — if the subtree doesn't have a
sessions/ folder yet, create it with an index.md:
# Sessions
- [[YYYY-MM-DD-slug-type]] — orientation phrase
Write the note — create the file using the Obsidian CLI so Obsidian's link index stays in sync:
obsidian create path="{subtree}/sessions/YYYY-MM-DD-slug-type.md" content="..." vault="<vault-name>"
Use \n for newlines in the content value. Always specify the vault
name if more than one vault is registered.
Update sessions/index.md — add an entry for the new note.
Update parent index.md — if the sessions/ subfolder is new,
add it to the parent folder's index:
- [[sessions/index|Sessions]] — conversation and diary notes
Update the changelog — append a dated entry to
.config/obsidian-knowledge/CHANGELOG.md summarizing actions taken.
Link to session notes created above rather than documenting detail
inline.