メニュー
Use this skill when the user asks about previous decisions, earlier fixes, past session notes, troubleshooting history, or knowledge that should already exist in the Obsidian vault.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use this skill when the user wants to initialize oh-my-obsidian, create or attach an Obsidian vault, configure persistent vault resolution, or prepare Obsidian Git integration.
Use this skill when the user wants to restore, migrate, or import past Codex session history into the Obsidian vault as structured documents.
Automatically recall relevant past context from the Obsidian vault when the user asks about past decisions, previous work, how something was done before, troubleshooting history, or project knowledge. This skill searches the team's knowledge base to provide historical context. Triggers: 회상, 기억나, 이전에, 어떻게 했지, recall, remember, how did we, what did we decide, past decision, 이슈 해결, 작업 기록, 이전 작업, 과거, 히스토리, 히스토리 확인, 찾아줘, 검색, find, search vault, what was the decision on, how was X implemented
Use this skill when the user explicitly wants to save, record, or summarize the current session into the Obsidian vault.
Save current session context and work summary to the Obsidian vault when the user asks to record or save their work. Automatically generates a structured markdown document capturing what was discussed, decisions made, and next steps. Triggers: 기록해, 저장해, save session, 세션 저장, 작업 기록, 이 작업 기록, save this, record this, 기록, 저장, 로그, log, document this, 회의록 작성, 정리해줘
Use this skill when the user wants to inspect the vault structure, add a new document, organize loose markdown files, or run a vault health check.
| name | oh-my-obsidian-recall |
| description | Use this skill when the user asks about previous decisions, earlier fixes, past session notes, troubleshooting history, or knowledge that should already exist in the Obsidian vault. |
Use this skill when the user asks about previous decisions, earlier fixes, past session notes, troubleshooting history, or knowledge that should already exist in the Obsidian vault.
oh-my-obsidian setup skill..git, .obsidian, and .oh-my-obsidian.node scripts/vault-ops.mjs recall --query "<user query>"
session-catalog.json) for fast
in-memory matching, then expands to full documents only for matches. If no catalog
exists or no matches are found, it falls back to full vault walk.
type:decision or type:troubleshooting for more precise matching.
Type mapping: 세션기록→session-log, 의사결정→decision, 트러블슈팅→troubleshooting, 회의록→meeting-notestype field in the output.Output format should include the type field:
📋 회상 결과
[의사결정] YYYY-MM-DD — 제목 (type: decision)
> 관련 내용 발췌...
[트러블슈팅] YYYY-MM-DD — 제목 (type: troubleshooting)
> 관련 내용 발췌...
If no result is found, say so plainly and suggest a narrower or alternate query.