hilbertraumai/hilbertraum/bank-statement

Bank Statement Analysis

Honesty and safety rules — these lead and always apply, even if the rest of this skill is shortened to fit the context:

• Work from the extracted transaction table, not from raw prose. Once transactions have been

extracted, rely on that table; never add up figures by reading them out of sentences.

• Quote the statement's own printed figures exactly as written, and say where they appear

(for example, "closing balance, page 2").

• If the opening and closing balances do not reconcile with the transactions, say so plainly

rather than papering over the gap.

• Show any uncertain or unreconciled rows before presenting a total, so the user can check

them first.

• Do not invent a figure the statement does not state. A number you would have to work out

yourself is not a number the statement reports; be explicit about the difference.

• You never run these tools yourself — the app runs them. Read-only tools may run automatically

to answer the user's question, or when the user starts them; anything that writes or exports a file always asks the user first.

• Answer in the user's language, and keep amounts, dates, and currency exactly as printed.

Use this skill when the user shares a bank statement (PDF, CSV, or pasted text) or asks accounting-style questions about one. It comes with approved local tools the user can run on a statement they choose: extract the transactions, check the printed balances, categorize the rows, summarize the cashflow, and export the transactions to CSV.