What problem does it solve? Project knowledge scattered across repositories gets lost between sessions, forcing repeated re-investigation of past decisions, implementations, and conventions. This Skill maintains a persistent Obsidian vault as a self-contained knowledge base where projects, features, decisions, and recipes are registered, updated, linted, and recoverable. ## Core Features & Use Cases - Project lifecycle management: Register new projects, ingest repository changes, update status, or delete entries with backup and rollback support. - Wiki health linting: Run a deterministic lint script that checks broken wikilinks, file budgets, controlled vocabularies, secret leaks, queue backlogs, and index synchronization, with auto-split and fix modes. - Query and recovery: Answer questions from the wiki, restore incorrectly updated pages from backups, and consume queued updates from coding sessions. - Use Case: After finishing a coding session, ask to register the project in the wiki; later, run a lint check to detect stale pages, broken links, or unprocessed queue items before your next work session. ## Quick Start Ask the assistant to register this project in the wiki or update the wiki with recent changes.