finance

Finance Ritual

This skill drives the local finance MCP server (financial-agent). It owns the source-of-truth reads, deterministic projections, provenance, and guarded actions. Your job is to call the right tools in the right order and report what they return — never to guess a number.

Hard rule

Every financial claim (a balance, an amount due, a date, a projection) MUST be backed by a finance MCP tool result in the same turn. If you do not have a tool result for it, say so and call the tool. Do not estimate, recall, or extrapolate dollar figures.

When the user corrects an account fact, re-read that account's live state with a finance MCP tool (get_finance_status or get_daily_digest) in the same turn before acting on the correction. Do not delete or reschedule a reminder, complete a follow-up task, or write a memory from a claimed or inferred account fact you have not re-read from a tool this turn. Never assume two accounts or two feeds are the same one; confirm the specific account first.

Daily ritual (the common path)

1. Collect inputs up front: ask for any portal screenshots or statement exports NOW, not mid-flow. Apple Card especially: its feed is balance-only, so its statement balance only enters the system when the user supplies it. Checking CSV pastes are safe to import since 2026-09-04 (MCP 0.3.35): the importer skips rows the SimpleFIN feed already has (reported as feed_duplicate), and a feed row that lands after a paste absorbs the paste copy. Feed row always wins. If a double count ever shows up anyway, run dedupe_pasted_transactions (dry run first).
2. Refresh live data: run_background_sync with options={"sync": true} (pulls SimpleFIN, then scans/reconciles/detects drift and surfaces due items in one audited run). For a quick manual refresh use sync_simplefin (incremental=true).
3. Read the digest: get_daily_digest (working cash, 7/14/30/60d projection, upcoming obligations, drift, matches to confirm, guardrail status). This is the morning summary. Lead your answer with its status_color and working cash.
4. Close out matches: list_reconciliation_review_items shows matches awaiting confirmation. For each one the user confirms, call confirm_reconciliation_match(instance_id). Use unconfirm_reconciliation_match to reverse. Never confirm without the user.
5. Triage discovered charges: list_charge_onboarding_queue / get_next_charge_onboarding_candidate; record a decision with record_charge_onboarding_decision; preview then apply with preview_charge_onboarding_apply and apply_charge_onboarding_candidate.