メニュー
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.
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.
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.
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, 회의록 작성, 정리해줘
| name | oh-my-obsidian-vault-manager |
| description | 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. |
Use this skill when the user wants to inspect the vault structure, add a new
document, organize root-level loose markdown files into 작업기록/세션기록,
or run a vault health check.
list and health-check may run with an attached or incomplete vault if the
resolver works.add and organize-apply require setup-state.status == "complete".add must never overwrite.organize is plan-first. Do not apply moves without explicit confirmation.add and organize-apply matches session-save: if unrelated
git changes exist, write or move the file but skip commit.oh-my-obsidian setup skill.node scripts/vault-ops.mjs vault list
node scripts/vault-ops.mjs vault add --title "<title>" --body "<body>" --relative-dir "<safe dir>"
node scripts/vault-ops.mjs vault organize-plan
node scripts/vault-ops.mjs vault organize-apply --plan-token "<token>" --move "old.md:작업기록/세션기록/old.md"
node scripts/vault-ops.mjs vault health-check
list, show the service root and work-record counts.add, choose a safe target directory, run the helper, and report the
created note path plus git result.organize, run organize-plan first, show the proposed moves and plan
token, then wait for approval before organize-apply.health-check, summarize setup-state.status, missing managed artifacts,
total Markdown count, and git status.