메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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 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.
Fetch bank and credit card transactions from Pluggy API for a target month and write the raw month files used by the pipeline.
| name | compile |
| description | 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. |
Full monthly pipeline. {household} (e.g. trevo) scopes all data under resources/{household}/.
Output is the canonical flat array in SCHEMA.md at
resources/{household}/{YYYY-MM}/expenses/result/budget_{mmm}_{YYYY}.json.
node plugins/open-personal-finance/scripts/fetch.mjs --household {h} --month {YYYY-MM}
node plugins/open-personal-finance/scripts/recompile.mjs --household {h} --month {YYYY-MM}
node plugins/open-personal-finance/scripts/audit.mjs --household {h} --month {YYYY-MM}
/fetch → raw + split files. Each row is tagged _status (posted/pending). When a
card bill closes, Pluggy re-issues its transactions as POSTED under new ids; fetch
identifies those closed bills and removes the stale PENDING duplicates they leave behind
(a PENDING credit row is dropped when a POSTED row with the same card/description/amount/date
already supersedes it). It prints PENDING credit transactions remaining: N — genuine
still-open charges are kept./recompile → builds the canonical budget: auto-classifies expenses/income from
expenses_memory.md / income_memory.md, preserves any prior classifications, parses
installment fields, enriches opaque descriptions, and carries the status (posted/pending)
onto every row. Prints rows left unclassified./classify (or /categorize + /recognize for a first full pass) the unclassified
rows so they consult memory, get classified, and persist new patterns. Re-run /recompile
to apply the new patterns./forecast — for a partial month only, add provisional income (salary) and recurring
fixed expenses as provisional: true rows. /recompile carries these forward and
reconciles them as the real transactions post./audit → node .../audit.mjs --household {h} --month {YYYY-MM} (auto-fixes, retries).
Audit always runs as the final step of every compile so the budget is validated on disk./advise → generates and sends the two Telegram messages (it calls /notify).expenses_memory.md — merchant → category/subcategory rules (drives auto-classification).income_memory.md — salary definitions, amount ranges, date windows, known income./classify and /learn; they are the single source of truth, so
the scripts never need per-month edits.