Run any Skill in Manus with one click

session-save

Stars27

Forks0

UpdatedApril 24, 2026 at 00:49

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, 회의록 작성, 정리해줘

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

hongdangmoo49

hongdangmoo49/oh-my-obsidian

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Secretaries and Administrative Assistants, Except Legal, Medical, and ExecutiveOffice and Administrative Support Occupations·SOC 43-6014

SKILL.md

readonly

name	session-save
description	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, 회의록 작성, 정리해줘
version	0.1.0
allowed-tools	["Bash","Read","Write"]

Session Save Skill — 세션 기록 저장

When to Activate

Activate when the user explicitly asks to save, record, or document the current session's work. Also activate when the stop hook prompts and the user agrees to save.

Steps

Check Environment Verify $OBSIDIAN_VAULT is set. If not, inform user and suggest /oh-my-obsidian:setup.
Analyze Session Review the conversation and extract:
- Main topics discussed
- Decisions made
- Code/files modified
- Problems solved
- Action items or next steps
Auto-Categorize Determine the best category and derive the type field:
- 작업기록/세션기록 → type: session-log: General work logs, coding sessions
- 작업기록/의사결정 → type: decision: Architectural choices, design decisions
- 작업기록/트러블슈팅 → type: troubleshooting: Bug fixes, error resolution
- 작업기록/회의록 → type: meeting-notes: Meeting summaries (if multiple participants mentioned)
- 서비스 레이어: Technical knowledge docs (API specs, schemas, etc.)
Discover Related Documents Before writing the note, search the vault for related documents using grep/glob. Add any found documents as wikilinks in the 관련 문서 section.
```
grep -ril "keyword1\|keyword2" "$OBSIDIAN_VAULT" --include="*.md"
```

Generate Document Create at: $OBSIDIAN_VAULT/작업기록/{세션기록|의사결정|트러블슈팅}/YYYY-MM-DD_{slug}.md

Template:

---
date: YYYY-MM-DDTHH:mm
topic: {inferred topic}
category: {auto-detected category}
type: {session-log|decision|troubleshooting|meeting-notes}
services: [{affected services}]
related_docs: [{auto-discovered wikilinks}]
status: done
tags: [auto-generated tags]
---

# {topic}

## 요약
{1-2 sentence summary}

## 상세 내용
{detailed notes from session}

## 주요 결정
- {decision 1}
- {decision 2}

## 변경된 파일
- `{file path}` — {what changed}

## 다음 단계
- [ ] {action item}

## 관련 문서
- [[{discovered-doc}]] -- (auto-discovered)

Git Commit

cd "$OBSIDIAN_VAULT"
git add "{category}/YYYY-MM-DD_{slug}.md"
git commit -m "docs: {category} — {topic}"

Confirm Print: "✅ 저장 완료: {category}/{filename}" If the user said "session-save skip", exit silently without saving.

Helper command with structural relationship flags:

node scripts/vault-ops.mjs session-save \
  --topic "<topic>" \
  --detail "<summary>" \
  --category "세션기록" \
  --type "session-log" \
  --service "<service>" \
  --related-doc "<vault-relative-path>"

More from this repository

same repository

oh-my-obsidian-setup

hongdangmoo49/oh-my-obsidian

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.

2026-04-2727

oh-my-obsidian-restore-history

hongdangmoo49/oh-my-obsidian

Use this skill when the user wants to restore, migrate, or import past Codex session history into the Obsidian vault as structured documents.

2026-04-2427

oh-my-obsidian-recall

hongdangmoo49/oh-my-obsidian

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.

2026-04-2427

recall

hongdangmoo49/oh-my-obsidian

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

2026-04-2427

oh-my-obsidian-session-save

hongdangmoo49/oh-my-obsidian

Use this skill when the user explicitly wants to save, record, or summarize the current session into the Obsidian vault.

2026-04-2427

oh-my-obsidian-vault-manager

hongdangmoo49/oh-my-obsidian

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.

2026-04-2327

name	session-save
description	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, 회의록 작성, 정리해줘
version	0.1.0
allowed-tools	["Bash","Read","Write"]

Session Save Skill — 세션 기록 저장

When to Activate

Activate when the user explicitly asks to save, record, or document the current session's work. Also activate when the stop hook prompts and the user agrees to save.

Steps

Check Environment Verify $OBSIDIAN_VAULT is set. If not, inform user and suggest /oh-my-obsidian:setup.
Analyze Session Review the conversation and extract:
- Main topics discussed
- Decisions made
- Code/files modified
- Problems solved
- Action items or next steps
Auto-Categorize Determine the best category and derive the type field:
- 작업기록/세션기록 → type: session-log: General work logs, coding sessions
- 작업기록/의사결정 → type: decision: Architectural choices, design decisions
- 작업기록/트러블슈팅 → type: troubleshooting: Bug fixes, error resolution
- 작업기록/회의록 → type: meeting-notes: Meeting summaries (if multiple participants mentioned)
- 서비스 레이어: Technical knowledge docs (API specs, schemas, etc.)
Discover Related Documents Before writing the note, search the vault for related documents using grep/glob. Add any found documents as wikilinks in the 관련 문서 section.
```
grep -ril "keyword1\|keyword2" "$OBSIDIAN_VAULT" --include="*.md"
```

Generate Document Create at: $OBSIDIAN_VAULT/작업기록/{세션기록|의사결정|트러블슈팅}/YYYY-MM-DD_{slug}.md

Template:

---
date: YYYY-MM-DDTHH:mm
topic: {inferred topic}
category: {auto-detected category}
type: {session-log|decision|troubleshooting|meeting-notes}
services: [{affected services}]
related_docs: [{auto-discovered wikilinks}]
status: done
tags: [auto-generated tags]
---

# {topic}

## 요약
{1-2 sentence summary}

## 상세 내용
{detailed notes from session}

## 주요 결정
- {decision 1}
- {decision 2}

## 변경된 파일
- `{file path}` — {what changed}

## 다음 단계
- [ ] {action item}

## 관련 문서
- [[{discovered-doc}]] -- (auto-discovered)

Git Commit

cd "$OBSIDIAN_VAULT"
git add "{category}/YYYY-MM-DD_{slug}.md"
git commit -m "docs: {category} — {topic}"

Confirm Print: "✅ 저장 완료: {category}/{filename}" If the user said "session-save skip", exit silently without saving.

Helper command with structural relationship flags:

node scripts/vault-ops.mjs session-save \
  --topic "<topic>" \
  --detail "<summary>" \
  --category "세션기록" \
  --type "session-log" \
  --service "<service>" \
  --related-doc "<vault-relative-path>"