| name | obsidian-cc-session |
| description | Legacy/support skill for writing a concise Claude Code session summary to an Obsidian daily note. Prefer /note for normal capture. Use only when the user explicitly asks for the old session-summary format or names /obsidian-cc-session. |
obsidian-cc-session
Append a concise summary of the current Claude Code session to today's Obsidian daily note. Each entry is one timestamped heading (with a wikilink topic), one aphoristic headline, 2-4 concrete bullets, and one ASCII diagram.
Where to write
~/Documents/Obsidian Vault/0-Diary/YYYY-MM-DD.md
- Create the file if missing.
- Append to the end if it exists.
- Never edit content already in the file.
Scope โ what counts as "this session"
Default: the most recent coherent unit of work in the conversation.
User can scope explicitly:
/obsidian-cc-session โ default (recent unit of work)/obsidian-cc-session full โ entire session/obsidian-cc-session last 3 โ last N exchangessummarize the recent discussion of <topic> โ only threads about that topic, ignore unrelated tangents
When in doubt, prefer narrower scope and ask the user what to include before drafting.
Entry format
## YYYY-MM-DD HH-MM โ [[<TopicWikilink>]] <optional 1-3 word descriptor>
> *<one aphoristic headline โ punchy, memorable, would survive as a standalone quote>*
- <concrete bullet: name files, paths, decisions, values โ not just verbs>
- <key decision with the reason>
- <output or artifact: path, name, count>
- <next step or open question>
โ```text
<one ASCII diagram summarizing the session>
โ```
> <emoji> *<one short joke or wry observation about THIS session โ specific, not generic>*
Heading time format is YYYY-MM-DD HH-MM (24h local, hyphen between hour and minute).
Title wikilink is required โ it's the backlink target. Open [[<Topic>]] in Obsidian later and every diary that touched it shows up. Stub pages (link target doesn't exist yet) are fine; the wikilink itself is the index.
Headline is one sentence, italicized blockquote (> *...*). Aphoristic โ should read well in isolation, like a quote on a card. If you can't write one, the session probably isn't worth logging.
Joke line at the end is required. One short wry remark or self-deprecating observation tied to this session โ a specific bug, a near-miss, an ironic pattern in the work. Lead with a single relevant emoji (๐ for a bug just fixed, ๐ for a citation/lit issue, ๐ช for an irony, ๐
for a near-miss, ๐ for slowness, ๐ฏ for an unexpected hit, etc.). Italicized inside a blockquote like the headline (> ๐ *...*). Keep it โค 25 words. Generic jokes ("AI is hard!") are forbidden โ every joke must reference something concrete from the session. If no joke fits without forcing it, swap the emoji for ๐คท and write a wry one-liner about the session's most absurd moment; never skip the line entirely.
Diagram โ pick ONE primitive
Choose whichever fits the session best:
| Primitive | Use for |
|---|
| annotated folder tree | what shipped (file/folder changes) |
| pipeline (leftโright or topโ) | a flow or step sequence |
| decision table | "we picked X over Y" |
| side-by-side comparison | X vs Y framing |
| single boxed callout | takeaway-only entry |
Rules:
- โค 12 lines of diagram.
- Heavy emoji where they help (โ
โณ ๐ โ).
- One diagram per entry โ no bullet-only entries.
Steps
- Get today's date + current time (24h local) โ format
YYYY-MM-DD HH-MM. Use date "+%Y-%m-%d %H-%M".
- Resolve path:
~/Documents/Obsidian Vault/0-Diary/<date>.md.
- Draft the entry: heading (with
[[Topic]] wikilink) + headline blockquote + 2-4 concrete bullets + one fenced diagram block.
- Show the draft to the user for โ
before writing.
- On confirm, append
\n\n + the block to the file (Edit if the file exists, Write if not).
- Confirm with the file path.
Style
- English default; quote the user verbatim if they spoke another language.
- Bullets: 1-2 sentences, โค 25 words each. Concrete > abstract โ name files, paths, decisions, values. Drop weak bullets โ better 3 strong than 5 vague.
- Never insert mid-line newlines. Each bullet, headline, and heading is ONE physical line in the source markdown. Do not soft-wrap at 80/100/any column โ Obsidian's live preview merges hard wraps into ugly paragraph runs, and editing wrapped bullets in the vault is annoying. If a bullet feels too long, shorten the bullet, do not wrap it. The only newlines in an entry are between blocks (heading / headline / each bullet / diagram fence / each diagram line).
- Wikilinks: title topic is always a wikilink (backlink target โ stubs OK). Body wikilinks only for notes that exist or topics worth aggregating across diaries.
- Headline: one aphoristic sentence right after the heading. Memorable in isolation. If you can't write one, the session probably isn't worth logging.
- Skip the whole entry if the session was trivial.
What this skill does NOT do
- โ Edit anything already in the daily note
- โ Read transcripts (the conversation is in your context already)
- โ Sync to git (Obsidian handles sync)
- โ Build canvases or roll up sessions
