菜单
Export Claude Code sessions to Obsidian markdown. Sync, list, resume, annotate sessions. Use when user says "sync session", "export session", "log session", "add session note", "close session", "resume session".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Backfill structured session summaries from Claude Code .jsonl transcripts into the vault's per-project Sessions folder. Distills each CC session into TL;DR / Goal / Outcome / Decisions / Blockers / Next / References — agent- and human-searchable, not raw transcripts. Use when user says "backfill sessions", "summarize my sessions for X", "fill in the empty session notes", or wants to make QMD project history actually useful.
Second brain onboarding wizard. Scaffolds PARA vault structure, company knowledge base, detects git projects from the filesystem, seeds company notes from the web, installs Obsidian plugins, initializes Git/Beads/QMD, and writes CLAUDE.md. Use when user says "setup", "set up my vault", "onboard", "initialize second brain", "run setup", or installs this plugin for the first time.
Client relationship management. Look up client context, log engagement notes, track status, and prep for meetings. Use when user says "client notes", "pull up [client name]", "update client", "new client", "prep for [client] call", "log meeting", "client status".
Open, create, or update today's daily note. Review yesterday, plan today, log progress. Use when user says "open today", "daily note", "what's today", "log this", "what did I do yesterday", "plan my day", "morning review", "EOD".
Run a Brain Check — audit your second brain across Setup, Connections, Beads, Memory, and Inbox. Use when user says "brain check", "health check", "system status", "what's broken", "what needs attention", "check connections", "what's backed up".
Create, find, and link atomic notes in your Zettelkasten. Distill insights into permanent notes with backlinks. Use when user says "add to zettelkasten", "atomic note", "permanent note", "note on X", "link this idea", "what atoms do I have on", "write a zettel", "capture this insight".
| name | sessions |
| description | Export Claude Code sessions to Obsidian markdown. Sync, list, resume, annotate sessions. Use when user says "sync session", "export session", "log session", "add session note", "close session", "resume session". |
| argument-hint | ["sync | list | export --today | resume | note TEXT | close TEXT"] |
| allowed-tools | Bash(python3:*) |
Export Claude Code conversations to 2. Areas/Sessions/ as structured Obsidian notes.
# Sync current session
python3 {baseDir}/scripts/sessions.py sync
# Export today's sessions
python3 {baseDir}/scripts/sessions.py export --today
# Export all sessions
python3 {baseDir}/scripts/sessions.py export --all
# List active sessions
python3 {baseDir}/scripts/sessions.py list
# Resume a session (pick from list)
python3 {baseDir}/scripts/sessions.py resume --pick
# Add timestamped note to current session
python3 {baseDir}/scripts/sessions.py note "figured out the auth bug"
# Close session with summary
python3 {baseDir}/scripts/sessions.py close "scaffold complete, moving to next task"
Sessions exported to 2. Areas/Sessions/ with frontmatter:
---
type: claude-session
date: YYYY-MM-DD
session_id: uuid
title: "..."
summary: "..."
messages: 42
status: active | done | blocked | handoff
tags: []
rating: null
comments: |
[2026-05-04 10:30] Note here
---
## My Notes sectioncomments, tags, rating, status frontmatter fieldsYour ~/.claude/settings.json already has session-export-qmd.js and session-auto-close.js
on the Stop event — no additional hooks needed. Session export is already automated.
Use the export command manually when you want to bulk-sync historical sessions.