Obsidian Note Capture
Overview
Use this skill to turn working material into durable Obsidian notes in the user's primary vault.
Resolve the vault root at runtime. Do not keep a device-specific absolute path in this shared skill.
Use this precedence:
- A vault path explicitly provided by the user.
- The vault derived from
OBSIDIAN_AGENT_ROOT by removing the /_system/agents suffix.
OBSIDIAN_VAULT_ROOT.
- In the
general-tasks workspace, read the device ID from local/device-name, then read the vault root from local/<device-id>/obsidian-vault-root.txt.
- If none resolves to an existing vault, ask one concise path question instead of reusing a path from another device.
This skill is about note capture and knowledge preservation. For raw Obsidian syntax details, combine it with obsidian-markdown. For batch CLI operations, combine it with obsidian-cli-automation.
Workflow
- Identify the capture intent.
- Preserve source documents, research traces, conversation summaries, implementation notes, or final deliverables.
- Keep Chinese as the default language unless the source or user asks otherwise.
- Resolve the target path.
- If the user specifies a file or directory, use it.
- Otherwise resolve the vault root using the precedence above.
- If the user explicitly says root directory, write under the vault root.
- Otherwise route by reading vault rules and nearby directory conventions.
- If routing is still ambiguous, ask one concise path question before writing.
- Read applicable instructions before mutation.
- Always read the vault root
AGENTS.md.
- If writing under a subdirectory, read the nearest subdirectory
AGENTS.md files that apply.
- Load
references/oldwinter-notes-rules.md for the detailed capture contract.
- Inspect existing notes before creating duplicates.
- Search for same or near-same title.
- If updating an existing note, read it first and make a local edit.
- If a same-name note is the same topic, merge or append.
- If the same name is a different topic, create
Title - YYYY-MM-DD.md.
- Write a valid Obsidian Markdown note.
- Include frontmatter for new Markdown notes.
- Use Obsidian wikilinks only when they are useful and do not invent fake links casually.
- Do not write local absolute paths into tracked Markdown unless the user explicitly wants the path recorded.
- Verify.
- Confirm the target file exists.
- Re-read the frontmatter and first section.
- Report the final vault-relative path.
Note Shape
New Markdown notes must include:
---
publish: false
date created: YYYY-MM-DD
date modified: YYYY-MM-DD
title: Note Title
tags:
- AI生成
---
Prefer this body structure unless the target directory has a stronger convention:
# Note Title
One-sentence definition or summary.
## 核心判断
- ...
## 事实
- ...
## 判断
- ...
## 待确认
- ...
For short notes, collapse sections and keep only what helps future retrieval.
Routing Defaults
- Root directory: only when explicitly requested or when the note is a top-level entry/document.
_system/: stable operating context, memory, plans, tool notes, and agent collaboration infrastructure.
Atlas/LLM Wiki/: source/query/concept/synthesis style compiled knowledge.
Calendar/: daily notes, tasks, plans, and dated working material.
Cards/: compact evergreen cards.
Clippings/ or Sources/: imported or clipped source material.
- Existing project or area folders: use when the note clearly belongs to an active folder and its local rules allow it.
When in doubt, prefer asking over silently widening the target.
References
references/oldwinter-notes-rules.md: Detailed oldwinter-notes capture rules, routing heuristics, and verification checklist.
1---
2name: obsidian-note-capture
3description: Capture documents, notes, research processes, conversation summaries, and deliverables into the user's Obsidian vault oldwinter-notes. Use when the user asks to save, write, archive, extract, distill, or record content into Obsidian, oldwinter-notes, a note vault, a digital garden, or a markdown knowledge base.
4metadata:
5 source: https://skillmd.com/skills/oldwinter/obsidian-note-capture
6---
7
8# Obsidian Note Capture
9
10## Overview
11
12Use this skill to turn working material into durable Obsidian notes in the user's primary vault.
13
14Resolve the vault root at runtime. Do not keep a device-specific absolute path in this shared skill.
15
16Use this precedence:
17
181. A vault path explicitly provided by the user.
192. The vault derived from `OBSIDIAN_AGENT_ROOT` by removing the `/_system/agents` suffix.
203. `OBSIDIAN_VAULT_ROOT`.
214. In the `general-tasks` workspace, read the device ID from `local/device-name`, then read the vault root from `local/<device-id>/obsidian-vault-root.txt`.
225. If none resolves to an existing vault, ask one concise path question instead of reusing a path from another device.
23
24This skill is about note capture and knowledge preservation. For raw Obsidian syntax details, combine it with `obsidian-markdown`. For batch CLI operations, combine it with `obsidian-cli-automation`.
25
26## Workflow
27
281. Identify the capture intent.
29 - Preserve source documents, research traces, conversation summaries, implementation notes, or final deliverables.
30 - Keep Chinese as the default language unless the source or user asks otherwise.
312. Resolve the target path.
32 - If the user specifies a file or directory, use it.
33 - Otherwise resolve the vault root using the precedence above.
34 - If the user explicitly says root directory, write under the vault root.
35 - Otherwise route by reading vault rules and nearby directory conventions.
36 - If routing is still ambiguous, ask one concise path question before writing.
373. Read applicable instructions before mutation.
38 - Always read the vault root `AGENTS.md`.
39 - If writing under a subdirectory, read the nearest subdirectory `AGENTS.md` files that apply.
40 - Load `references/oldwinter-notes-rules.md` for the detailed capture contract.
414. Inspect existing notes before creating duplicates.
42 - Search for same or near-same title.
43 - If updating an existing note, read it first and make a local edit.
44 - If a same-name note is the same topic, merge or append.
45 - If the same name is a different topic, create `Title - YYYY-MM-DD.md`.
465. Write a valid Obsidian Markdown note.
47 - Include frontmatter for new Markdown notes.
48 - Use Obsidian wikilinks only when they are useful and do not invent fake links casually.
49 - Do not write local absolute paths into tracked Markdown unless the user explicitly wants the path recorded.
506. Verify.
51 - Confirm the target file exists.
52 - Re-read the frontmatter and first section.
53 - Report the final vault-relative path.
54
55## Note Shape
56
57New Markdown notes must include:
58
59```yaml
60---
61publish: false
62date created: YYYY-MM-DD
63date modified: YYYY-MM-DD
64title: Note Title
65tags:
66 - AI生成
67---
68```
69
70Prefer this body structure unless the target directory has a stronger convention:
71
72```markdown
73# Note Title
74
75One-sentence definition or summary.
76
77## 核心判断
78
79- ...
80
81## 事实
82
83- ...
84
85## 判断
86
87- ...
88
89## 待确认
90
91- ...
92```
93
94For short notes, collapse sections and keep only what helps future retrieval.
95
96## Routing Defaults
97
98- Root directory: only when explicitly requested or when the note is a top-level entry/document.
99- `_system/`: stable operating context, memory, plans, tool notes, and agent collaboration infrastructure.
100- `Atlas/LLM Wiki/`: source/query/concept/synthesis style compiled knowledge.
101- `Calendar/`: daily notes, tasks, plans, and dated working material.
102- `Cards/`: compact evergreen cards.
103- `Clippings/` or `Sources/`: imported or clipped source material.
104- Existing project or area folders: use when the note clearly belongs to an active folder and its local rules allow it.
105
106When in doubt, prefer asking over silently widening the target.
107
108## References
109
110- `references/oldwinter-notes-rules.md`: Detailed oldwinter-notes capture rules, routing heuristics, and verification checklist.