Working with Obsidian, Readwise, and AI to Create Notes
🔗 **Source:** [Working with Obsidian, Readwise, and AI to Create Notes](https://www.stefanimhoff.de/note-taking-obsidian-readwise-ai/)
> [!note]+ Document Notes
> tags: [Assign relevant tags or keywords to the note to facilitate organization and retrieval. Add a # before each tag. Tags cannot have special characters. Do not use the tag #articles]
> - #obsidian
> - #readwise
> - #ai-workflows
> Author: Stefan Imhoff
> Source: Stefan Imhoff’s Journal
> Reference: https://www.stefanimhoff.de/note-taking-obsidian-readwise-ai/
> date created: 2025-08-16 21:22
>
> # 📝 Title: Working with Obsidian, Readwise, and AI to Create Notes — Structured Analysis & Advocate’s Guide
>
<!-- deep-read:sections start -->
## 🧭 Table of Contents
- [📚 References (from the article)](#-references-include-a-list-of-sources-consulted-and-cited-in-the-article)
- [📝 Summary](#-summary)
- [📖 Main Content](#-main-content)
- [🗒️ Notes](#-notes)
- [🔗 References (external)](#-references)
- [🗣️ Paraphrase](#-paraphrase)
- [📰 Newsletter Blurb](#-newsletter)
- [✅ Action Items (Advocacy, Education, OSPO Path)](#-action-items)
- [🧪 Hypotheses](#-hypotheses)
- [📊 Methodology](#-methodology)
- [❓ Questions](#-questions)
- [🔮 Future Research](#-future-research)
- [💡 Implications](#-implications)
- [🧠 Learning Styles Assessment](#-learning-styles-assessment)
- [♿ Accessibility Assessment](#-accessibility-assessment)
- [🌍 DEIB Assessment](#-deib-diversity-equity-inclusion-and-belonging-assessment)
- [🧩 Logical Validity & Tone](#-logical-validity)
- [🛡️ DARVO Screen](#-darvo-analysis-prompt)
- [🔍 SEO Evaluation](#-seo-evaluation)
- [🎯 Conclusion](#-conclusion)
### 📚 References: Include a list of sources consulted and cited in the article.
- 🧑💻 **Author**: Stefan Imhoff. **Date**: February 16, 2025. **Title**: *Working with Obsidian, Readwise, and AI to Create Notes*. :contentReference[oaicite:0]{index=0}
- 🔗 **Linked docs in-article**: Readwise “Chat with Highlights” & MCP guides. :contentReference[oaicite:1]{index=1}
- 🪟 **Tool background**: Obsidian overview & history. :contentReference[oaicite:2]{index=2}
---
## 📝 Summary
- ✅ **What**: A practitioner’s walkthrough of a modern **note-making** stack: **Obsidian** + **Readwise (Reader + Chat)** + **local/cloud AI** for summarizing, refactoring, connecting, and publishing notes. :contentReference[oaicite:3]{index=3}
- 🧩 **How**: Opinionated setup: minimal folders, heavy linking (Zettelkasten), **core/community plugins** (Backlinks, Dataview, Note Refactor, Git, Copilot, Omnisearch, Templater), **weekly exports** from Readwise, and **Raycast AI** prompts to TL;DR highlights. :contentReference[oaicite:4]{index=4}
- 🧠 **Why**: Increase **idea flow** and retrieval by connecting literature notes to original sources and to other atomic notes; use AI to **speed comprehension**, not replace judgment. :contentReference[oaicite:5]{index=5}
- 🤝 **New**: **Readwise Chat** and **Readwise MCP** allow conversational querying of your own highlights in Readwise or via external clients like Claude and Raycast. :contentReference[oaicite:6]{index=6}
---
## 📖 Main Content
### 🧱 Layout & Structure
- 🔹 **Vault structure**: Sparse folders (`assets`, `canvas`, `clippings`, `journals`, `pages`, `references`, `templates`). Encourages links over hierarchy. :contentReference[oaicite:7]{index=7}
- 🔹 **Panes**: Left = files/search/bookmarks/calendar/Git; Right = local graph, outline, outgoing links, backlinks, tags. Aims for **fast navigation** and **context awareness**. :contentReference[oaicite:8]{index=8}
- 🔹 **Zettelkasten** discipline: **Backlinks** and **MOCs** highlight connections; **Random Note** drives spaced resurfacing and maintenance. :contentReference[oaicite:9]{index=9}
### 🔌 Plugins (Selected)
- 🧭 **Core**: Backlinks, Canvas, Daily Notes, Graph View, Random Note, **Unique Note Creator** (timestamp IDs, rename later), **Templates**. :contentReference[oaicite:10]{index=10}
- 🧰 **Community**:
- 🧮 **Dataview** for queries/tables.
- ✂️ **Note Refactor** for splitting long notes into atomic notes.
- 🧵 **Git** (auto-commit), **Prettier**, **Reading Time**, **Callout Manager**.
- 🤖 **Omnisearch** + **AI Image Analyzer** (Ollama) for local multimodal search.
- 🧑🏫 **LanguageTool**, **Editor Syntax Highlight**. :contentReference[oaicite:11]{index=11}
### 📑 Templates
- 🧱 **Note**, **Daily Note**, **Literature Note**, **Person**, **Book**, **Movie** templates with consistent front matter (`created/updated`, `aliases`, `tags`, `urls`, `reference`). Emphasis on **aliases** to avoid link rot. :contentReference[oaicite:12]{index=12}
### 📥 Intake → 📤 Output
- 🌐 **Readwise hub**: Imports highlights from web, Reader, Kindle, podcasts, YouTube transcripts; weekly export to Obsidian (often a separate vault first). :contentReference[oaicite:13]{index=13}
- 🗣️ **Chat with Highlights**: Ask natural-language questions; see referenced highlights; optionally route via **MCP** to Claude/Raycast. :contentReference[oaicite:14]{index=14}
- 🧪 **AI for research**: Brave Leo, Perplexity, Raycast AI, local models; **always reviewed and corrected** by the author. :contentReference[oaicite:15]{index=15}
- ✍️ **AI for literature notes**: TL;DR bullets with emojis → rename result into a **memorable atomic title** → link to related nodes. :contentReference[oaicite:16]{index=16}
---
### 🗒️ Notes
- 🔸 **Philosophy**
- 🔹 Link ideas aggressively; tags stay broad.
- 🔹 Backlinks and MOCs reveal concept clusters.
- 🔹 Random resurfacing keeps notes alive. :contentReference[oaicite:17]{index=17}
- 🔸 **Process**
- 🔹 Capture everywhere → **Readwise** → weekly export.
- 🔹 Draft in large notes; **Note Refactor** to atomize.
- 🔹 Summarize with AI; **human edits** finalize. :contentReference[oaicite:18]{index=18}
- 🔸 **Risk management**
- 🔹 **Git** backup alongside **Obsidian Sync**.
- 🔹 **LanguageTool** + **Prettier** ensure consistency. :contentReference[oaicite:19]{index=19}
- 🔸 **Tooling landscape**
- 🔹 Obsidian supports **graphs**, **Canvas**, **core/community** plugins.
- 🔹 Sync is E2E encrypted; Canvas added in v1.1 (2022). :contentReference[oaicite:20]{index=20}
---
## 📖 References
- 🧑💻 Imhoff, S. “Working with Obsidian, Readwise, and AI to Create Notes.” Feb 16, 2025. :contentReference[oaicite:21]{index=21}
- 📚 Readwise Docs: **Chat with Highlights**; **Readwise MCP**. :contentReference[oaicite:22]{index=22}
- 🪟 Obsidian (software) overview & timeline. :contentReference[oaicite:23]{index=23}
---
## 🗣️ Paraphrase
- 🧩 **Original idea (workflow stance)**: The author prefers **few folders** and **many links**. He uses **Zettelkasten** principles, then **Random Note** to revisit and connect items.
- 🗣️ **Paraphrase**: Keep the file tree light. Let links do the organizing. Resurface old notes daily so networks form and strengthen. :contentReference[oaicite:24]{index=24}
- 🤖 **Original idea (AI posture)**: AI speeds summarizing and structuring, but **human judgment** remains essential to fix errors and set context.
- 🗣️ **Paraphrase**: Use AI to compress and clarify, then edit firmly. The person—not the model—ensures accuracy and meaning. :contentReference[oaicite:25]{index=25}
---
## 📰 Newsletter
**Subject idea:** Your notes should work while you sleep.
- 🧰 This week: a field-tested workflow combining **Obsidian**, **Readwise**, and **AI** to turn highlights into connected knowledge.
- ⚙️ Highlights: minimal folders, maximal links; **Dataview** queries; **Note Refactor** to split big drafts; **Readwise Chat** to query your own reading history; **MCP** to bring those highlights into **Claude** or **Raycast**. :contentReference[oaicite:26]{index=26}
- 🏁 Try it: Export your Readwise highlights weekly, summarize with AI, then rename the best bullet into a punchy note title.
- 🔗 Links: [Article](https://www.stefanimhoff.de/note-taking-obsidian-readwise-ai/), [Readwise Chat](https://docs.readwise.io/readwise/guides/chat-with-highlights), [Readwise MCP](https://docs.readwise.io/readwise/guides/mcp).
---
## ✅ Action Items
**Goal**: Align takeaways with open-source advocacy, contributor education, and a path toward **OSPO leadership** at GoDaddy.
- 🧱 **Publish a “starter vault” for contributors**
- 🧩 Include templates for “Issue Triage,” “Proposal,” “Decision Record,” and “Docs PR.”
- 🔁 Add **Note Refactor** workflow so contributors can split RFCs into atomic decisions.
- 🧑🤝🧑 Tie to inclusion: prompts for non-native English writers and accessibility checks.
- 🧪 **Run a “Readwise → Obsidian” onboarding workshop**
- 🗺️ Show weekly highlight export, **Chat with Highlights**, and MCP into **Claude**/**Raycast**.
- 📊 Measure: # of first-time PRs attributable to workshop within 30 days. :contentReference[oaicite:27]{index=27}
- 🧠 **Create curriculum: “AI as junior editor”**
- ✍️ Teach AI prompts for TL;DR with **human verification**.
- 🧵 Provide examples for docs, release notes, and meeting minutes.
- 🔍 **Transparency dashboard**
- 📈 Use **Dataview** to surface contributor shout-outs, decision logs, and governance timelines.
- 🔗 Publish via Obsidian Publish or static build; document data sources. :contentReference[oaicite:28]{index=28}
- 🤝 **Under-represented dev outreach**
- 🎓 Offer scholarships for the workshop; schedule sessions in friendly time zones.
- 🗣️ Provide live captions and code-of-conduct reminders in materials.
- 🧭 **OSPO readiness**
- 🧩 Map this workflow to OSPO pillars: **Policy**, **Engagement**, **Compliance**, **Metrics**, **Education**.
- 🗺️ Document playbooks with open licensing for reuse across teams.
---
## 🧪 Hypotheses
- 🧠 **H1**: Teams using weekly **Readwise → Obsidian** exports will create more connected notes and **reduce duplicate docs**.
- ⏱️ **H2**: AI-assisted TL;DRs cut **docs grooming time** by >30% without harming accuracy.
- 🧩 **H3**: MCP-based highlight chat improves **onboarding retention** for new contributors.
### 📊 Methodology
- 🧾 **Design**: 8-week A/B pilot across two contributor cohorts.
- 📚 **Data**: Vault commit logs (Git plugin), Dataview queries, PR counts, issue cycle time, contributor surveys. :contentReference[oaicite:29]{index=29}
- 🔬 **Analysis**: Pre/post comparisons, Mann-Whitney U for non-normal metrics, inter-rater reliability on summary accuracy.
### ❓ Questions
- ❔ Where does AI introduce subtle bias in summaries of governance debates?
- ❔ Which plugin set yields best onboarding outcomes with least friction?
- ❔ How do MCP integrations change contributor **search behavior**?
### 🔮 Future Research
- 🔭 Compare **local LLMs** vs hosted models for privacy and speed.
- 🧭 Study **Zettelkasten** effects on decision traceability in OSS projects.
- 🔌 Explore **automated provenance**: link summaries back to highlights and commits.
### 💡 Implications
- 🧩 Better note networks can **improve governance memory**.
- 🧑🏫 AI as assistant—not author—can scale documentation education.
- 🧠 MCP bridges private knowledge to chat UIs, improving **contextual answers**. :contentReference[oaicite:30]{index=30}
---
## 🧠 Learning Styles Assessment
**Readability**: General audience tech blog; roughly Grade 9–11 reading level (short paragraphs, direct voice).
- 🖼️ **Visual**
- ✅ Images of Graph View, Raycast AI, layout.
- ➕ Add **diagram** of the capture → summarize → refactor → link pipeline. :contentReference[oaicite:31]{index=31}
- 🔊 **Aural**
- ⚠️ No audio/podcast embeds. ➕ Provide brief **audio summary** or TTS link.
- ✍️ **Verbal**
- ✅ Clear explanations with examples and definitions.
- ➕ Add **mini-glossary** for plugin names and acronyms.
- 🧍 **Kinesthetic**
- ⚠️ Few hands-on tasks. ➕ Add a **5-step lab** with copy-paste prompts.
- 🧮 **Logical**
- ✅ Step-wise processes and tool rationales.
- ➕ Include a **flowchart** and success metrics.
- 👥 **Social**
- ⚠️ No built-in community prompts. ➕ Add discussion questions and a forum link.
- 🧘 **Solitary**
- ✅ Encourages personal template tweaking.
- ➕ Add reflection prompts after each section.
- 🌱 **Naturalistic**
- ⚠️ Not applicable. ➕ Use environmental metaphors to explain “knowledge gardens.”
---
## ♿ Accessibility Assessment
- 🧭 **Semantic structure**: Uses H1/H2/H3, readable lists. Good baseline.
- 🖼️ **Alt text**: Images appear labeled; ensure **descriptive alt** and captions beyond “Image: …”. :contentReference[oaicite:32]{index=32}
- ⌨️ **Keyboard navigation**: Likely fine for a static article; confirm focus states.
- 🌗 **Contrast & fonts**: Check against WCAG 2.2 AA; ensure reflow at 200% zoom.
- 🔍 **Text resizing**: Confirm responsive layout does not clip code blocks.
---
## 🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment
- 🌐 **Cultural breadth**: Neutral, tool-centric; few diverse case studies.
- ➕ Add examples from **non-Western** contributors and **access-limited** contexts.
- 🗣️ **Inclusive language**: Generally neutral and respectful.
- ➕ Define jargon; offer plain-language summaries.
- 🧩 **Neurodiversity support**: Clear headings; consistent patterns.
- ➕ Provide **checklists**, **callouts**, and **shortcuts** summaries.
- 👥 **Representation**: Limited visuals of people; content-only.
- ➕ Include links to **community stories** and beginner pathways.
- 🛟 **Psychological safety**: No triggering material; add **CoC** link for workshop tie-ins.
---
## ✅ Logical validity
- 🧠 **Strengths**
- 🧩 **Causal reasoning**: “More links → better retrieval/serendipity,” supported by Zettelkasten practice. Suggest adding metrics to quantify “better.” :contentReference[oaicite:33]{index=33}
- 🔗 **Appeal to evidence**: Concrete plugin list, weekly export habit, and screenshots. :contentReference[oaicite:34]{index=34}
- 🧰 **Balanced view of AI**: Positions AI as accelerator with human review. Strengthens credibility. :contentReference[oaicite:35]{index=35}
- ⚠️ **Weaknesses / potential fallacies**
- 🎯 **Hasty generalization**: The “graph as Death Star = good connectivity; others are messy” implies quality via appearance; needs retrieval metrics.
- 🎬 **Possible straw framing**: The aside that *Starship Troopers* is “not Fascist” and the director “never read the book” asserts a contested claim with a single link; invite more sources for balance. :contentReference[oaicite:36]{index=36}
- 🎙️ **Tone of voice**: Practical, confident, and reflective; first-person narrative; didactic but not dogmatic; light humor (“Death Star”); minimal hype; instructive screenshots. :contentReference[oaicite:37]{index=37}
---
## 🛡️ DARVO Analysis Prompt
- 🚫 **Deny / Attack / Reverse**: Not present. The piece is instructional, not adversarial; no signs of reputational attack or role reversal.
---
## 🔍 SEO Evaluation
- 🔑 **Keywords**: “Obsidian,” “Readwise,” “AI,” “Zettelkasten,” “plugins.” Used naturally in H1/H2 and body. Good. :contentReference[oaicite:38]{index=38}
- 🧾 **Meta/Title**: Clear H1 with primary keywords. Ensure meta description contains “Obsidian + Readwise + AI workflow.”
- 🏗️ **Heade:contentReference[oaicite:39]{index=39}**
<!-- deep-read:sections end -->