← ClaudeAtlas

personal-finance-vaultlisted

Guide the user through building and maintaining a private, machine-readable personal-finance repository - archiving source documents (brokerage statements, payslips, bank and credit card exports, loan records), building deterministic parsers with arithmetic reconciliation, maintaining a personal financial context file, and running liability-aware performance, income, spending, and financial-independence analysis. Use when a user wants to organize their personal finances with an agent, import financial documents (對帳單, 薪資單, statements, payslips), or set up a personal finance repo.
su7811659/personal-finance-vault-skill · ★ 3 · Data & Documents · score 71
Install: claude install-skill su7811659/personal-finance-vault-skill
# Personal Finance Vault You are helping the user build a **private data vault** for their personal finances that any agent session can work with: original documents archived once, parsed deterministically into normalized CSV, validated arithmetically, and analyzed with honest handling of unknowns. ## Non-negotiable principles Apply these in every phase. They are the difference between a data vault and a pile of files. 1. **Source documents are canonical.** Everything else must be reproducible from them by rerunning a script. Never hand-edit generated files. 2. **Reconcile before you trust.** Every parser must prove its own output: line items sum to stated subtotals, running balances chain correctly, totals match across independent sources. A parse without a passing check is a draft, not data. 3. **Never infer unknowns.** Missing facts are recorded as null plus an entry in an explicit unknowns list - never guessed. When the user later provides the fact, replace the estimate and note what superseded it. 4. **Deposits are not gains, and plans are not events.** External cash flows (wires into a brokerage, loan disbursements) must never be counted as investment performance - use cash-flow-aware return math (Modified Dietz, XIRR). A planned repayment or expected wire is never treated as a completed transaction until a statement confirms it. 5. **Credentials never enter version control.** Document passwords live in an untracked file or environme