Conversation Recap to Obsidian

---

name: conversation-recap-to-obsidian

description: Build high-value Obsidian daily and weekly review notes from conversation or existing markdown notes. Use this skill whenever the user asks to summarize the current chat into Obsidian, append a structured session recap, regenerate a daily summary from a full daily note, create or refresh a weekly report, merge same-topic work across multiple days, group work by project/task instead of by date, or extract structured review notes with conclusions, key points, tags, and wikilinks.

---

# Conversation Recap to Obsidian

This skill turns raw conversation or existing Obsidian markdown into **review-ready notes**, not generic summaries. Treat the whole daily/weekly note as input content regardless of who wrote each part.

The default goal is to help the user answer:

Use this skill for

Core design

Split the work in three layers:

1. **Entry layer = raw work-item capture**

- append a single session recap into the daily note

- preserve concrete issue / solution / conclusion / key point details

- act as the source material for later daily and weekly synthesis

2. **Daily summary layer = same-day aggregation**

- read the full daily note

- merge duplicate work threads

- compress the day into a small number of reusable conclusions

3. **Weekly layer = cross-day synthesis**

- merge same-topic work across multiple days

- rank larger / more complex items first

- avoid day-by-day流水账

Use scripts when they improve reliability. Do not avoid them just to stay “pure prompt only.”

Daily note target

Default path:

Mode 1: Session recap mode

Use this when the user has just finished one conversation or one work block and wants to **record a new entry** instead of refreshing the whole day.

Session recap principle

Create a new item in the daily note as source material for later summaries.

Default entry structure

#### 事项标题 — HH:mm

- **问题**: ...
- **方案**: ...
- **结论**: ...
- **关键点**: ...
- **关联**: [[...]] · [[...]]
- **标签**: #tag-a #tag-b

Session recap guidance

Mode 2: Daily summary mode

A daily summary is **regenerable**. It is not an append-only log.

When asked to refresh the daily summary:

1. Read the full daily note.

2. Treat the whole note as usable source material regardless of whether parts were written by a person or another AI/tool.

3. Ignore only the previous generated summary block for this skill to avoid recursive self-copying.

4. Extract the day’s main work items from the note content.

5. Compress them into a concise review section.

6. Replace only the generated summary block.

Default daily output shape

## 今日总结

- 今日主要事项：...
- 核心解决的问题：...
- 关键点：...
- 结论/产出：...
- 相关文档：[[...]] · [[...]]
- 标签：#tag-a #tag-b

Daily writing guidance

Mode 3: Weekly summary mode

Default path:

The date is the **Sunday** of that reporting week.

Weekly summary principle

A weekly report should be organized by **work item**, not by day.

The correct unit is not “Tuesday” or “Wednesday.”

The correct unit is “the import pipeline fix,” “the skill redesign,” “the database migration,” etc.

If one work item spans 3 days, merge those 3 daily notes into one weekly module.

Weekly frontmatter and module structure

Weekly notes should include frontmatter like:

---
word_count: 1234
type: weekly-summary
week_start: 2026-03-23
week_end: 2026-03-29
---

Then the body uses modules like:

### 1. 事项名
- 涉及日期：2026-03-17、2026-03-18、2026-03-19
- 核心解决的问题：...
- 关键点：...
- 结论/产出：...
- 相关文档：[[...]] · [[...]]
- 标签：#tag-a #tag-b

Weekly ranking rule

Sort weekly items by importance using these signals:

1. number of involved days

2. amount of structured content / subpoints

3. visible complexity or decision weight

Larger, longer-running, more complex items should appear earlier.

Weekly writing guidance

Tagging guidance

Tags are optional but useful.

Principles

- project or product name

- work type (`#summary-skill`, `#线上排障`)

- technical topic (`#jwt`, `#auth`, `#obsidian`)

Avoid

Safe rewrite rule

Generated sections should be wrapped with markers so they can be replaced safely:

<!-- AI_SUMMARY_START -->
...
<!-- AI_SUMMARY_END -->

Preserve all non-target content outside the markers.

Bundled script

Use the bundled script for stable maintenance tasks:

The script is publishable because it supports shared defaults plus local overrides.

Resolve configuration in this order:

1. CLI arguments

2. `config.json` next to the skill

3. built-in defaults

Commands

Append a session entry:

python scripts/recap_manager.py append-entry \
  --title "JWT验签修复与线上排障" \
  --problem "登录后 401，被踢回" \
  --solution "补 JWKS 公钥验签并修正 issuer" \
  --conclusion "测试和正式环境恢复正常" \
  --key-points "先确认 token claims，再加严格校验" \
  --links "app/core/auth/jwt_auth.py,deploy/config.k8s.yaml" \
  --tags "jwt,auth,线上排障"

Refresh a daily summary:

python scripts/recap_manager.py refresh-daily-auto --date 2026-03-25

Generate a weekly report:

python scripts/recap_manager.py generate-weekly-auto --mode last-week

Important constraints

Success bar

A good result lets the user quickly review: