asets-gobizit/save-to-obsidian

Save to Obsidian

Capture, organize, and format key information from the current Claude conversation into an Obsidian-compatible markdown note.

When to Use

• User says "save to obsidian", "save this to obsidian", "obsidian save"
• User invokes /save-to-obsidian
• User wants to preserve important decisions, findings, or discussion from the current session

How to Invoke

/save-to-obsidian
/save-to-obsidian [optional topic hint]

Examples:

• /save-to-obsidian — Claude reviews the conversation and saves key points
• /save-to-obsidian Paperclip setup — saves with focus on that topic

What It Does

1. Scan the current conversation for important content:

   • Decisions made
   • Technical findings or discoveries
   • Configuration changes
   • Action items or next steps
   • Key facts learned
   • Problems solved and how

2. Organize into a clean Obsidian note:

   • Descriptive filename (e.g., Paperclip Reinstall from Source.md)
   • Obsidian-formatted markdown with [[wikilinks]] and #tags
   • Sections: Summary, Key Decisions, Details, Action Items, Related Notes
   • Date stamped

3. Save to the Obsidian vault:

   • Path: C:\Users\dansk\Claude\Obsidian@Claude\
   • Uses Obsidian conventions (wikilinks, tags, short filenames)

4. Sync to Claude memory (MANDATORY final step): After saving to Obsidian, read back the new/updated Obsidian note(s) and:

   • Check each key decision, configuration change, and fact against existing Claude memory files
   • If the Obsidian note contains information that is not yet in Claude memory or updates stale memory, create or update the appropriate memory file:
     • user type — new info about Danny's role, preferences, knowledge
     • feedback type — new behavioral guidance (do this / don't do that)
     • project type — new project state, decisions, deadlines
     • reference type — new external resources, tools, links
   • Update MEMORY.md index if new memory files were created
   • Skip if the info is already accurately captured in memory or is too ephemeral
   • Never duplicate — check existing memory files first before creating new ones
   • Never store secrets — API keys, tokens, passwords must not go into memory

Output Format

# [Descriptive Title]

#tag1 #tag2 #relevant-tags

*Saved from Claude conversation — [date]*

## Summary
[2-3 sentence overview of what was discussed/decided]

## Key Decisions
- Decision 1 — why it was made
- Decision 2 — why it was made

## Details
[Organized content from the conversation — configs, findings, technical details]

## Action Items
- [ ] Item 1
- [ ] Item 2

## Related
- [[Related Note 1]]
- [[Related Note 2]]

Rules

• NEVER include API keys, tokens, passwords, or secrets in the saved note
• Use [[wikilinks]] for references to other Obsidian notes
• Use #tags inline (not YAML frontmatter tags)
• Keep filenames short and descriptive (no dates in filename)
• If a topic already has an Obsidian note, UPDATE it rather than creating a duplicate
• Always check if existing related notes exist in the vault before creating links