Save

Skill eliransu/digital-brain/skills/save

Claude + Obsidian knowledge companion. A persistent, compounding wiki vault based on Karpathy's LLM Wiki pattern — drop sources, ask questions, knowledge compounds.

Install

npx -y skills add eliransu/digital-brain --skill save

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Save the current conversation, answer, or insight into the Obsidian wiki vault as a structured note. Analyzes the chat, determines the right note type, creates frontmatter, files it in the correct wiki folder, and updates index, log, and hot cache. Triggers on: "save this", "save that answer", "/digital-brain:save", "file this", "save to wiki", "save this session", "file this conversation", "keep this", "save this analysis", "add this to the wiki".

SKILL.md

4.6 KB, as published. Nobody here has run it

save: File Conversations Into the Wiki

Good answers and insights shouldn't disappear into chat history. This skill takes what was just discussed and files it as a permanent wiki page.

The wiki compounds. Save often.

Note Type Decision

Determine the best type from the conversation content:

Type	Folder	Use when
synthesis	wiki/synthesis/	Multi-step analysis, comparison, or answer to a specific question
concept	wiki/concepts/	Explaining or defining an idea, pattern, or framework
source	wiki/sources/	Summary of external material discussed in the session
decision	wiki/meta/	Architectural, project, or strategic decision that was made
session	wiki/meta/	Full session summary: captures everything discussed

If the user specifies a type, use that. If not, pick the best fit based on the content. When in doubt, use synthesis.

Save Workflow

Scan the current conversation. Identify the most valuable content to preserve.
Ask (if not already named): "What should I call this note?" Keep the name short and descriptive.
Determine note type using the table above.
Extract all relevant content from the conversation. Rewrite it in declarative present tense (not "the user asked" but the actual content itself).
Create the note in the correct folder with full frontmatter.
Flywheel: file new people BEFORE wikilinking. Scan the note's body for distinct person names. Read wiki/entities/people/_index.md. For each name not yet filed (no page in wiki/entities/people/<Full Name>.md and no alias match), invoke the ppl skill's add flow to create a page. Use the conversation context for role/relationship; if uncertain, file with role: "—" + a > [!todo] Confirm role callout. Default company: Your Organization unless the source says otherwise. Track newly-filed names and show them in the final confirmation. Never emit a [[Name]] wikilink to a non-existent page — phantom links rot the graph.
Collect links: identify any wiki pages mentioned in the conversation. Add them to related in frontmatter.
Update wiki/index.md. Add the new entry at the top of the relevant section.

Append to wiki/log.md. New entry at the TOP:

## [YYYY-MM-DD] save | Note Title
- Type: [note type]
- Location: wiki/[folder]/Note Title.md
- From: conversation on [brief topic description]

Update wiki/hot.md to reflect the new addition.
Confirm: "Saved as [[Note Title]] in wiki/[folder]/."

Frontmatter Template

---
type: <synthesis|concept|source|decision|session>
title: "Note Title"
created: YYYY-MM-DD
updated: YYYY-MM-DD
tags:
  - <relevant-tag>
status: developing
related:
  - "[[Any Wiki Page Mentioned]]"
sources:
  - "[[.raw/source-if-applicable.md]]"
---

For question type, add:

question: "The original query as asked."
answer_quality: solid

For decision type, add:

decision_date: YYYY-MM-DD
status: active

Writing Style

Declarative, present tense. Write the knowledge, not the conversation.
Not: "The user asked about X and Claude explained..."
Yes: "X works by doing Y. The key insight is Z."
Include all relevant context. Future sessions should be able to read this page cold.
Link every mentioned concept, entity, or wiki page with wikilinks.
Cite sources where applicable: (Source: [[Page]]).

What to Save vs. Skip

Save:

Non-obvious insights or synthesis
Decisions with rationale
Analyses that took significant effort
Comparisons that are likely to be referenced again
Research findings

Skip:

Mechanical Q&A (lookup questions with obvious answers)
Setup steps already documented elsewhere
Temporary debugging sessions with no lasting insight
Anything already in the wiki

If it's already in the wiki, update the existing page instead of creating a duplicate.