obsidian-save

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Capture current session context as a note in the Obsidian vault.

捕获当前会话上下文并保存为Obsidian库中的笔记。

Use when user wants to save conversation insights, decisions, or context to their Obsidian knowledge base.

当用户希望将会话见解、决策或上下文保存到其Obsidian知识库时使用。

Parse user prompt: The text accompanying the skill invocation guides the note:
- Focus areas: "just the debugging steps", "only architecture decisions"
- Exclusions: "skip the failed attempts", "don't include the tangents"
- Structure: "as a how-to guide", "as bullet points", "as a decision log"
- Title: Extract explicit title if given, otherwise derive from topic
Generate filename:
```
YYYY-MM-DDTHH-MM-SS-<slug>.md
```
- Use provided title as slug, or derive from session topic
- Slugify: lowercase, hyphens for spaces, no special chars
Summarize session based on user's direction:
- Default (no direction): decisions, solutions, key insights, action items
- With direction: prioritize what user asked for, shape content accordingly
- Use concise bullet points unless user requests different structure
Create note at
```
~/obsidian/Notes/<filename>
```
:

markdown

---
date: <ISO8601 timestamp>
daily: [[YYYY-MM-DD]]
tags:
  - claude-session
source: claude-code
---

解析用户提示：调用Skill时附带的文本将指导笔记的生成：
- 重点内容：“仅调试步骤”、“仅架构决策”
- 排除内容：“跳过失败尝试”、“不要包含题外话”
- 结构要求：“作为操作指南”、“作为项目符号列表”、“作为决策日志”
- 标题：如果用户指定了明确标题则提取，否则从主题衍生
生成文件名：
```
YYYY-MM-DDTHH-MM-SS-<slug>.md
```
- 使用用户提供的标题作为slug，或从会话主题衍生
- Slug处理：转为小写，用连字符代替空格，移除特殊字符
根据用户指示总结会话：
- 默认（无指示）：总结决策、解决方案、关键见解和行动项
- 有指示时：优先处理用户要求的内容，调整内容形式
- 除非用户要求其他格式，否则使用简洁的项目符号列表
在
~/obsidian/Notes/<filename>
路径下创建笔记：

markdown

---
date: <ISO8601 timestamp>
daily: [[YYYY-MM-DD]]
tags:
  - claude-session
source: claude-code
---

<会话的项目符号摘要>


5. **Confirm**: Echo the full path and brief summary of what was captured.

<任何值得保留的额外上下文、代码片段或具体细节>


5. **确认反馈**：返回笔记的完整路径以及所捕获内容的简要摘要。

The user's prompt is your primary guide. Examples:

Title: "save to obsidian: webpack config fixes" → title is "webpack-config-fixes"
Focus: "just the solution" → skip context, emphasize what worked
Format: "as a checklist" → use
```
- [ ]
```
items instead of prose
Filter: "only the API changes" → exclude unrelated discussion

When no direction given, default to a balanced summary of key outcomes.

用户的提示是主要指导依据。示例：

当没有用户指示时，默认生成包含关键成果的均衡摘要。

User says	Action
"save this to obsidian"	Summarize full session, auto-generated title
"note this discussion about auth"	Save with title "auth" as slug
"save to obsidian, focus on the fix we found"	Emphasize the solution, minimize context
"add to vault as a how-to guide for setting up the dev env"	Structure as step-by-step guide, not bullet summary
"dump to obsidian, just the architecture decisions we made"	Filter to only architectural choices
"save session, skip the debugging tangents"	Omit failed attempts, focus on outcomes

用户指令	执行操作
"save this to obsidian"	总结整个会话，自动生成标题
"note this discussion about auth"	以“auth”为slug保存笔记
"save to obsidian, focus on the fix we found"	重点强调解决方案，尽量减少上下文内容
"add to vault as a how-to guide for setting up the dev env"	整理为分步指南，而非项目符号摘要
"dump to obsidian, just the architecture decisions we made"	仅筛选保存架构决策内容
"save session, skip the debugging tangents"	省略失败尝试内容，重点关注成果

Always include
```
daily: [[YYYY-MM-DD]]
```
for today's date to create backlink
Keep summaries focused on actionable/memorable content
Include code snippets only if they're the key takeaway