How do I install the Vault Save skill?

Run npx skillmds@latest add danmestas/vault-save in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Vault Save safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Vault Save?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Vault Save free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Vault Save?

danmestas (@danmestas) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Vault Save by danmestas — Agent Skill

Name: Vault Save
Author: danmestas

Vault Save

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", "/save", "file this", "save to wiki", "save this session", "file this conversation", "keep this", "save this analysis", "add this to the wiki".

danmestas 48840f1 3.7 KB Updated Sep 17, 2026

File contents

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/questions/	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.
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.

---name: vault-savedescription: 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", "/save", "file this", "save to wiki", "save this session", "file this conversation", "keep this", "save this analysis", "add this to the wiki".---# save: File Conversations Into the WikiGood 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 DecisionDetermine the best type from the conversation content:| Type | Folder | Use when ||------|--------|---------|| synthesis | wiki/questions/ | 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 Workflow1. **Scan** the current conversation. Identify the most valuable content to preserve.2. **Ask** (if not already named): "What should I call this note?" Keep the name short and descriptive.3. **Determine** note type using the table above.4. **Extract** all relevant content from the conversation. Rewrite it in declarative present tense (not "the user asked" but the actual content itself).5. **Create** the note in the correct folder with full frontmatter.6. **Collect links**: identify any wiki pages mentioned in the conversation. Add them to `related` in frontmatter.7. **Update** `wiki/index.md`. Add the new entry at the top of the relevant section.8. **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] ```9. **Update** `wiki/hot.md` to reflect the new addition.10. **Confirm**: "Saved as [[Note Title]] in wiki/[folder]/."---## Frontmatter Template```yaml---type: <synthesis|concept|source|decision|session>title: "Note Title"created: YYYY-MM-DDupdated: YYYY-MM-DDtags: - <relevant-tag>status: developingrelated: - "[[Any Wiki Page Mentioned]]"sources: - "[[raw/source-if-applicable.md]]"---```For `question` type, add:```yamlquestion: "The original query as asked."answer_quality: solid```For `decision` type, add:```yamldecision_date: YYYY-MM-DDstatus: 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. SkipSave:- Non-obvious insights or synthesis- Decisions with rationale- Analyses that took significant effort- Comparisons that are likely to be referenced again- Research findingsSkip:- Mechanical Q&A (lookup questions with obvious answers)- Setup steps already documented elsewhere- Temporary debugging sessions with no lasting insight- Anything already in the wikiIf it's already in the wiki, update the existing page instead of creating a duplicate.

Frequently asked questions