Skip to main content
command CX Codex

obsidian-distill — Claude Code command: notes with provenance

obsidian-distill condenses a long note or article into key claims, each tagged with the exact source block it came from — paragraph, section, or timestamp.

MIT ★ 5,412 updated 2026-10-24

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add eugeniughelbur/obsidian-second-brain
/plugin install obsidian-second-brain@obsidian-second-brain
Open on GitHub

What obsidian-distill does

The command reads an Obsidian note, URL, or folder and breaks the text into numbered blocks — sections, paragraphs, list items. It extracts key claims, attaches a reference to the source block (src: B3) to each, and adds a confidence marker (stated | high | medium | speculation). The result is saved as a new note in wiki/concepts/ or Knowledge/, with a ## Source blocks section at the bottom — locators pointing to headings, paragraph indices, or line ranges in the original.

This is not a summary: a distillation keeps a verifiable trail. Every claim without a block reference is dropped, and inferences the agent makes but the source does not state go into a separate ## Inferences (not in the source) section marked speculation. If the source is an external URL or file, the command first saves it to raw/ so the link stays stable.

Works with the obsidian-second-brain skill, writes notes per references/ai-first-rules.md — frontmatter includes type: distillation, ai-first: true, mandatory wikilinks for people and projects, recency markers for external facts. Pairs with /obsidian-ingest (bringing material in) and /vault-deep-synthesis (cross-referencing notes): here — compressing a single source without losing the thread back to it.

What it helps with

  • compress an article or transcript while keeping links to source sections
  • pull key claims from a folder of notes and trace where each came from
  • build a summary with confidence labels for every statement
  • verify what any claim is based on — paragraph, timestamp, or heading

Example prompts for the agent

  • Distill raw/interview-notes.md with markers showing where each claim came from
  • Pull key claims from the folder research/ai-papers/ and list the source blocks
  • Condense this article URL into a summary, each claim tagged with the paragraph

How to install obsidian-distill

1Plugin marketplace

/plugin marketplace add eugeniughelbur/obsidian-second-brain
/plugin install obsidian-second-brain@obsidian-second-brain

2Manually: put the files in place

.claude/commands/obsidian-distill.md

Call it with /obsidian-distill. For all projects use ~/.claude/commands/

Questions about obsidian-distill

How to install obsidian-distill in Claude Code?

Run /plugin marketplace add eugeniughelbur/obsidian-second-brain, then /plugin install obsidian-second-brain@obsidian-second-brain. The command will be in .claude/commands/obsidian-distill.md.

What does obsidian-distill do?

Reads a long note, URL, or folder, breaks it into blocks, extracts claims, and tags each with a reference to the source block. The result is a new note with an anchor section at the bottom so any claim can be checked.

How is distillation different from a summary?

A summary discards the source, a distillation keeps a verifiable trail: each claim is marked (src: B3) and tied to a numbered block with a locator — heading, paragraph index, or timestamp.

Source text

obsidian-distill.md · MIT
---
description: Condense a long note or source into key claims, each tagged with provenance back to the exact source block it came from
category: thinking
triggers_en: ["distill this", "condense this note", "summarize with sources", "distill this source", "boil this down with provenance"]
triggers_de: ["das verdichten", "diese Notiz kürzen", "mit Quellen zusammenfassen", "diese Quelle auswerten", "mit Herkunftsnachweisen zusammenfassen"]
triggers_es: ["destila esto", "condensa esta nota", "resúmelo con fuentes", "destila esta fuente", "resume esto sin perder el contexto", "sácame lo importante de esto con las fuentes"]
triggers_pt: ["destile isto", "condense esta nota", "resuma com fontes", "destile esta fonte", "reduza isto com proveniência"]
triggers_zh: ["提炼这篇笔记", "把这个内容压缩成关键结论", "总结这份材料并标明出处", "精简内容但保留来源", "从这个来源提炼要点"]
---

Use the obsidian-second-brain skill. Execute `/obsidian-distill $ARGUMENTS`:

The optional argument is a note path, a `[[wikilink]]`, a folder, or a source URL/file. If none is given, ask what to distill (offer the longest recently-touched notes in `raw/` and the research folders as candidates).

A distillation is not a summary. A summary throws the source away; a distillation keeps a verifiable trail, so a teammate (or a future agent) can check every claim against the exact place it came from. This is the trust primitive: condensed but never unmoored from evidence.

1. Read `_CLAUDE.md` first if it exists in the vault root. Resolve the destination folder per `references/folder-map.md` (a distillation is a concept/reference note: wiki-style `wiki/concepts/`, Obsidian-style `Knowledge/`).

2. Resolve and read the source:
   - A vault note or `[[wikilink]]`: read it in full.
   - A folder: read every note in it and distill them as one corpus (note which file each claim comes from).
   - A URL: fetch it (read the page). A local file: read it. Save the untouched original to `raw/` first if it is not already there - the distillation must point at a stable source.
   - Never distill from memory or a partial read. If the source is too large to read in one pass, read it in ordered chunks and keep going; do not sample (see the anti-fabrication rule).

3. Segment the source into stable, citable **source blocks** and number them. A block is a heading section, a paragraph, a list, or a transcript turn - whatever the source's natural unit is. Record for each block a locator the reader can find again: a heading path, a paragraph index, or a timestamp/line range. These locators are the provenance anchors.

4. Extract the key claims. For each claim, write one tight sentence and attach its provenance: which block(s) it came from, as `(src: B3)` or `(src: B3, B7)`. Every claim MUST carry at least one block reference - a claim with no source does not go in the distillation (if you believe it but the source does not say it, it is your inference, not a distilled claim; see step 6). Mark each claim's confidence (`stated | high | medium | speculation`) and add a recency marker on any time-sensitive external fact (`(as of YYYY-MM, domain)`).

5. Group the claims under short thematic headings (the distilled structure), preserving the provenance tags inline. Keep the source's own terms; do not smooth them into generic phrasing.

6. Keep inference separate from evidence. If the distillation surfaces a conclusion the source implies but never states, put it under a clearly labelled `## Inferences (not in the source)` section, each marked `confidence: speculation`, so distilled fact and your reasoning never blur.

7. Write the distillation note. Path: `<resolved-folder>/Distill - <source-title> (YYYY-MM-DD).md`. It MUST follow `references/ai-first-rules.md`. If that path does not resolve from your working directory, search upward for it; if you still cannot read it, say so before writing rather than producing a note that silently skips the rule. Frontmatter includes `type: distillation`, `ai-first: true`, `source` (the verbatim path/URL of what was distilled), `source-blocks` (the count), `date`, `tags: [distillation, thinking]`, `related-people` and `related-projects` (wikilinks, per the `type: distillation` schema). Body order:
   - `## For future agent` - 2-3 sentences: what was distilled, why, and that every claim carries a `(src: Bn)` pointer back to the numbered source blocks at the bottom for verification.
   - `## Distilled claims` - the grouped claims with inline provenance tags.
   - `## Inferences (not in the source)` - only if step 6 produced any.
   - `## Source blocks` - the numbered list (`B1`, `B2`, ...) with each block's locator (heading/paragraph/timestamp) and a short quote or first line, so the anchors are resolvable from inside the vault. This is the recency/verification anchor.

8. Link the distillation from the original source note (add a `Distilled: [[...]]` line) and from today's daily note. Append a one-line entry to the operation log (`Logs/YYYY-MM-DD.md` if it exists, else `log.md`).

9. Report: the source, how many blocks and claims, the path written, and any claim you dropped because it had no traceable source (so the gap is visible, never silently cut).

Distillation is what makes a vault trustworthy to more than one person: condensed enough to read fast, anchored enough to audit. Pairs with `/obsidian-ingest` (which brings the source in) and `/vault-deep-synthesis` (which cross-references many notes); this one compresses a single source without losing the thread back to it.

---

**AI-first rule:** Every note created or updated by this command MUST follow `references/ai-first-rules.md` - `## For future agent` preamble, rich frontmatter (`type`, `date`, `tags`, `ai-first: true`, plus type-specific fields), recency markers per external claim, mandatory `[[wikilinks]]` for every person/project/concept referenced, sources preserved verbatim with URLs inline, and confidence levels where applicable. If that path does not resolve from your working directory, search upward for it; if you still cannot read it, say so before writing rather than producing a note that silently skips the rule. The vault is for future agent retrieval - not human reading.

**Anti-fabrication:** Every distilled claim must trace to a real source block - never invent a claim, a block, or a locator, and never attach a `(src: Bn)` tag to a block that does not support it. Read the source exhaustively rather than sampling; a confident distillation built on a partial read is the failure mode this command exists to prevent. Mark inferences as `speculation` and keep them out of the distilled-claims section. See the anti-fabrication and search-completeness hard rules in `references/ai-first-rules.md`.

© Eugeniu Ghelbur · MIT · eugeniughelbur/obsidian-second-brain

Similar slash commands

All slash commands for Notes, tasks and projects →

From the same set51

The whole set →
youtube Pulls a YouTube transcript, metadata, and top comments into an Obsidian note. Add --visual when the video’s frames matter too. CX Codex +1 ★ 5,412repo stars obsidian-architect obsidian-architect scans a project and generates architecture notes in your vault: overview with diagram, per-module notes, key decisions. Re-run to refresh docs without losing your edits. CX Codex +1 ★ 5,412repo stars obsidian-reconcile obsidian-reconcile is a Claude Code command that finds contradictions in an Obsidian vault and resolves them automatically or flags them for review. It scans the full vault or a specific topic. CX Codex +1 ★ 5,412repo stars obsidian-visualize The obsidian-visualize command maps your Obsidian vault visually: shows how notes connect, identifies hubs, and highlights isolated entries. Use it to see your second brain's shape at a glance. CX Codex +1 ★ 5,412repo stars obsidian-merge obsidian-merge merges near-duplicate Obsidian notes without deleting files. It preserves links, unions frontmatter, and converts the retired note into a redirect stub. CX Codex +1 ★ 5,412repo stars obsidian-checkin The obsidian-checkin command asks the vault owner to confirm aging facts in notes and records their replies. Use it to review details about people or projects that may have changed. CX Codex +1 ★ 5,412repo stars research-deep research-deep scans your Obsidian vault to map what you already know, identifies missing or stale information, fills gaps via Perplexity or Grok, synthesizes the findings, and updates your notes on people, projects, and ideas automatically. CX Codex +1 ★ 5,412repo stars create-command create-command scaffolds a new slash command for Obsidian through an interactive interview, removing the need to write Markdown or frontmatter by hand. CX Codex +1 ★ 5,412repo stars

Project sponsors

Companies that keep this analytics open