obsidian-vault-builderlisted

# Obsidian Vault Builder (general PKM, multi-vault aware) Patterns for operating an Obsidian vault from Claude Code: capture pipelines, plugin selection, REST API integration, file-portability discipline, methodology choice. Multi-vault aware. For academic study vault construction (course prep, lecture notes, mock exams, exam-ready content): the durable patterns from the deprecated `obsidian-study-vault-builder` skill have been folded into this skill. See `references/academic-vault.md`. The companion skill itself was removed via PR #6 and re-validated 2026-05-15 (over-triggered on exam-prep prompts; structurally misaligned with the interactive-practice approach in `~/.claude/rules/exam-prep-protocol.md`). ## When to use - User asks to add/edit/query content in an Obsidian vault - User asks to install or configure Obsidian plugins - User wants to integrate Claude Code with Obsidian via Local REST API or CLI - User wants to automate ongoing capture/organization/retrieval - User wants to design a PKM workflow - User asks to build a course/exam/study vault (see `references/academic-vault.md`) ## Checkpoint-based vault build (greenfield, large generation tasks) When generating a vault from scratch or filling in many chapters/sections at once, never generate everything upfront. Use progressive validation: 1. First chapter / first section — then STOP 2. User review — approve format, structure, quality 3. Remaining chapters / sections — continue with validated pattern 4. Final