Vault Health Check
Run a comprehensive diagnostic on the provenance database and present findings with suggested actions.
Steps
- •
Check database status: Call
db_statusto confirm the database is initialized and get overall statistics. - •
Find orphaned inputs: Call
find_orphaned_inputsto list inputs that were stored but never linked to any note.- •Suggest reviewing these: were they forgotten, or are they no longer needed?
- •
Find unlinked notes: Call
find_unlinked_notesto list notes with no known input source.- •These notes have no provenance trail. Suggest linking them to their sources.
- •
Find stale notes: Call
find_stale_noteswith a reasonable threshold (e.g. 30 days).- •For each stale note, suggest the user check whether the file still exists in the vault.
- •
Show recent activity: Call
get_event_logwithlimit: 10to show the most recent events. - •
Present a summary report with:
- •Total inputs, notes, links, events
- •Number of orphaned inputs
- •Number of unlinked notes
- •Number of stale notes
- •Recent activity
- •
Suggest actions for any issues found. Never auto-fix — always present findings and let the user decide.
Important
- •This skill is diagnostic only. It never modifies data automatically.
- •The MCP server suggests — it never auto-fixes. All vault changes require user approval.
- •If the database is not initialized, suggest running
/vault-initfirst.