Menu
Fetch bank and credit card transactions from Pluggy API for a target month and write the raw month files used by the pipeline.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Finalize a target month — always refetch it fresh to confirm the movements are complete (all transactions present, no pending left), then recompile with --final to strip provisionals, and run heartbeat for the current month. Defaults to settling the previous month.
Assess a household's monthly investment snapshot for real anomalies. A script produces an objective month-over-month diff (value + quantity per holding, tagged qty/price/new/gone, plus integrity checks); then you reason over it and write a plain-language verdict — a summary message, an assess_{month}.md, and an assess_{month}.json (per-item, consumed by the viewer). Called at the end of /investments; also use whenever the user asks to review, sanity-check, validate, or "assess" a month's investments/portfolio/patrimônio, or whether anything looks unusual, missing, or wrong.
Build a household's monthly investment-portfolio snapshot by reading the broker statements (screenshots + PDFs) in investments/input and writing the canonical personal_finances_{YYYY-MM}.json. Use when the user asks to compile, snapshot, update, or generate investments / portfolio / patrimônio / posições for a month, or mentions BTG/Nubank/Wise/FGTS/Morgan Stanley statements under investments/input.
Validate the schema of a monthly budget, auto-fixing where possible. Checks required fields, types, buckets, FX, enrichment and installment rules. Use when /fetch, /recompile, or /heartbeat call it, or when the user asks to audit, validate, or check a month's data integrity.
Generate a monthly categorized budget JSON by running fetch + recompile, then classifying leftovers and forecasting partial months. Use when the user asks to generate, create, or analyze a monthly budget, expenses, or income.
Generate the two Telegram budget messages (leftover preamble + full advisory) from a compiled budget. Use when /compile, /heartbeat, or /settle need insights, or when the user asks for advice/analysis on their budget.
| name | fetch |
| description | Fetch bank and credit card transactions from Pluggy API for a target month and write the raw month files used by the pipeline. |
Run the bundled script (no per-month code):
node plugins/open-personal-finance/scripts/fetch.mjs --household {household} --month {YYYY-MM}
It authenticates with Pluggy (credentials from {household}/.env.local), pulls every
non-manual account in pluggy_items.json for the month window, preserves the full
Pluggy payload (only rename creditCardMetadata → metadata), appends household
metadata (_holder, _accountType, _accountName, _accountNumber from
pluggy_items.json, _bank), dedupes by id, and writes:
{household}/{YYYY-MM}/expenses/
transactions_raw.json ← all transactions (source of truth)
cc_open_bill.json ← CREDIT + status PENDING
cc_closed_bill.json ← CREDIT + status POSTED
savings.json ← BANK
/accounts first if pluggy_items.json is stale./audit on the split files, or proceed to /recompile.