vault-overhaul

Audit pod vaults to repair drift and refresh indexes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ChiroHD/pod-vault-template --skill vault-overhaul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vault-overhaul
Source: https://github.com/ChiroHD/pod-vault-template/tree/main/.claude/skills/vault-overhaul
Command: npx skills add https://github.com/ChiroHD/pod-vault-template --skill vault-overhaul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Periodic on-demand audit pass to keep the entire pod vault current and consistent. Complements the per-ingest enforcement (which prevents drift in real-time) by catching anything that slipped through, refreshing all index dates + counts, surfacing wiki candidates, linting cross-links, flagging stale claims, and (in deep mode) comparing against sibling pod vaults for cross-vault drift. Run weekly or whenever you suspect drift.

Core Features & Use Cases

  • Regular, comprehensive audit across the entire vault, including index refresh and artifact reconciliation
  • Configurable in-sequence checks: --dry-run, --section, --cross-vault-compare, and --update-template
  • Surface issues and provide judgment calls (without automatically changing decisions)
  • Cross-vault drift detection and optional template-backflow planning

Quick Start

Run the vault overhaul to start a full audit cycle and generate a findings report.

Frequently Asked Questions about vault-overhaul

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect and fix data drift in my wiki vault?

Wiki vault drift is detected and fixed by running periodic audits that refresh index counts, verify living artifacts, lint cross-links, and compare against sibling vaults. Mechanical fixes apply automatically while judgment calls surface for manual review.

What is the best way to automate cross-link integrity checks across a vault?

Cross-link integrity checks are automated through on-demand vault audits that lint links, verify indexes, and flag broken connections across the entire vault. Use the --section flag to target specific areas or run a full cycle for comprehensive coverage.

Can I run a dry-run audit to preview vault fixes before applying changes?

Yes, you can run a dry-run audit using the --dry-run flag to preview mechanical fixes like index updates and count corrections without applying changes. The audit surfaces all findings and judgment calls for review before you commit modifications.

How do I compare vault data against sibling vaults to catch cross-vault drift?

Cross-vault drift is compared by running the audit with the --cross-vault-compare flag, which evaluates your vault against sibling pod vaults. This surfaces inconsistencies and drift across multiple vault instances for reconciliation.

Does the vault audit automatically change decision statuses or just report them?

The vault audit does not automatically change decision statuses; it only flags them for review. It automatically applies mechanical fixes like counts, dates, and index updates, but surfaces all judgment calls and logical issues for manual user review.

Why do I need periodic vault audits if I already have real-time ingest enforcement?

Periodic vault audits catch drift that real-time per-ingest enforcement misses by refreshing all index dates, surfacing wiki candidates, checking log sanity, and scanning for self-improvement opportunities across the entire vault.