Vault Upkeep

The problem

Personal knowledge bases like Obsidian rot as facts evolve. A deadline changed in a project note remains outdated in a weekly review, and "next week" markers from months ago clutter your search results.

What it does

• Identifies cross-note contradictions where numbers, statuses, or dates disagree across your vault.
• Locates "expired futures" like past-due relative dates and stale "in-progress" status lines.
• Fixes broken wikilinks and identifies orphaned notes or near-miss duplicate stubs.
• Generates a prioritized report of factual errors and dormancy before applying any audited, minimal edits.

Frameworks & tools

Markdown-based vaults (Obsidian, Logseq, Foam) and Git for version-controlled upkeep commits.

Why this beats prompting it yourself

Standard LLM prompts often hallucinate or rewrite your entire note style. This skill uses a multi-pass inventory system that enforces "recency wins" logic and requires evidence from your own files before suggesting a change.

Use cases

• Synchronizing project statuses across disparate trackers and summary notes.
• Cleaning up broken links and empty files after a major vault reorganization.
• Auditing a knowledge base for stale commitments and expired "active" project flags.
• Performing a disciplined fact-check after a high-velocity work sprint.

Known limitations

Does not support automated deletion or folder restructuring. Large vaults over 200 notes require targeted sweeps to maintain accuracy.