# Readwise Addendum This vault uses a split Readwise setup: - The Obsidian Readwise plugin owns the `Readwise/` tree. - The `readwise` CLI owns Reader and Readwise interactions outside plugin sync. ## Rules - For Readwise or Reader tasks, prefer the official `readwise-cli` skill and the `readwise` command. - Use the CLI first for: - searching Reader documents - querying a particular text for information - searching highlights across the library - saving URLs to Reader - tagging, moving, archiving, and inbox triage - daily review and related operational workflows - Treat `Readwise/` as plugin-managed sync output. Do not edit, rename, move, or create files in `Readwise/` unless explicitly asked. - When a task benefits from a vault artifact created by the agent, write it outside `Readwise/`. - Prefer `Readwise Queries/` for retrieval-oriented outputs and `Notes/` for durable synthesis. - When asked what a particular text says, prefer this order: 1. `readwise reader-search-documents` 2. `readwise reader-get-document-details` 3. `readwise reader-get-document-highlights` 4. `readwise readwise-search-highlights` - Use synced Obsidian Readwise notes for browsing, linking, and synthesis after retrieval, not as the primary interface. - If the user asks to highlight a passage inside Reader, use the existing `readwise-reader` browser workflow unless the CLI path is clearly better for that specific case. - When presenting quoted source material in chat, format any quotation longer than one sentence or roughly 25 words as a Markdown block quote. - For source-retrieval answers, prefer short framing followed by block-quoted passages rather than inline long quotes.