maintain-obsidian-vaultlisted

Maintain and normalize an Obsidian Markdown vault for human navigation and AI/RAG indexing. Use when Codex is asked to audit, update, cross-link, clean up, align terminology, validate frontmatter, add hub/index pages, enforce vault indexing policy, maintain PROJECT_KNOWLEDGE.md files, or keep an Obsidian vault continuously current without losing information.
thestratcore/My-skills · ★ 0 · AI & Automation · score 62

Install: claude install-skill thestratcore/My-skills

# Maintain Obsidian Vault ## Core rule Treat the Obsidian vault as the source of truth. Preserve existing information. Never delete, merge, rename, or archive notes without explicit user approval. Never edit credential-like files structurally. Keep generated content deterministic and separate from handwritten content. Use stable filenames and metadata so Obsidian, external Markdown tooling, and RAG pipelines can address notes consistently. ## Standard workflow 1. Inventory Markdown files with `rg --files -g '*.md'`, excluding generated dependency folders. 2. Run `scripts/vault_audit.py <vault-root>` before editing. 3. Detect available vault tooling before relying on it. Use the filesystem and `vault_audit.py` workflow when optional Obsidian CLI or other helpers are unavailable; do not assume an Obsidian CLI installation. 4. Read root governance notes if present: - `Vault Indexing Policy.md` - `Canonical Terminology.md` - `Document Lifecycle.md` - `Repository Improvement Report.md` 5. Read the target notes and nearby directory context before changing links or metadata. 6. Apply minimal edits: - add or repair YAML frontmatter - add semantic wikilinks where they improve navigation - add `## See also` sections for genuinely related concepts - add hub/index pages only when they connect existing knowledge - add placeholder concept pages only when repeated concepts have no canonical note 7. For any approved rename, inventory inbound wikilinks fi