plutus-net-worth

name	plutus-net-worth
description	Calculate and explain current net worth, account valuations, portfolio allocation and portfolio performance using local data files and live market data. Use when you need to answer questions like "what's my net worth", "show my asset allocations", "how did my holdings perform", "summarize my accounts" or break assets down by liquidity tier, currency exposure, tax status, or asset class.

Net Worth

Use this skill to show your user's net worth based on the data collected

Load the local finance context

Resolve the data directory first: use PLUTUS_DATA_DIR if set, otherwise ~/.config/plutus/data/.

• If the data directory does not exist, direct the user to onboard using the plutus-onboard skill.
• Read profile.json from the data directory first.
• Read preferences from profile.json before deciding how much detail to show.
• Read assets.json and any other files in the data directory that contain net worth related information.

Prepare pricing only when needed

• Use plutus market ticker for current prices. Run plutus market ticker --help if unsure of flags.
• Use plutus market history only when the user asks about performance over time. Run plutus market history --help if unsure of flags.
• For FX rates, use plutus market ticker with Yahoo Finance currency pair symbols (e.g. --ticker USDSGD=X).
• Cache ticker prices and FX rates within the conversation. Reuse cached values unless the user explicitly asks for a refresh or enough time has passed that a refresh is justified.
• Batch unique tickers into as few plutus calls as possible.

Value each account without flattening away metadata

• For savings, cash, and balance-based investment accounts, use the stored balance.
• For units-based investment accounts, compute units * current price using plutus market ticker.
• Preserve each account's native currency during intermediate calculations. Convert only when presenting a base-currency total.

Handle portfolio composition and performance requests

• Always provide allocation percentages for invested assets when the user asks for portfolio mix.
• When the user asks how the portfolio performed, use plutus market history with the appropriate ticker and period flags for units-based holdings.
• Prefer a value-weighted portfolio summary when combining multiple holdings and state that choice in one line.
• Do not fabricate returns for balance-based investment accounts. Exclude them from return calculations or note that performance is unavailable without historical price or transaction data.
• If the user asks for a "periodic summary", include current net worth, major account changes, allocation shifts, and performance for the requested period if data exists.

Present results in the house style

• Lead with the total net worth first.
• State key assumptions in one line: valuation date, pricing freshness, FX basis, and any omitted accounts or liabilities.
• Use markdown tables for account summaries and allocation breakdowns.
• Format currency with the user's configured symbol and two decimal places.
• Show movements as increase or decrease.
• Keep the default answer compact and scannable; expand only when the user asks for more detail.

Guardrails

• Never overwrite stored account data without confirming with the user first.
• Prefer explicit caveats over false precision when the data model is incomplete.
• If a request crosses into runway, savings rate, or goal planning, use the matching skill instead of stretching this one to cover everything.