agentleFS
shashu10shashu10/personal-finance-skills/skills/finance-plan/SKILL.md

finance-plan

Skill2 starsChanged 51 days agoMITView on GitHub

Review household spending and budgets, or model cash runway, income changes, debt, and life goals using confirmed facts and dated evidence. Use for personal finance planning and tax-sensitive scenarios, not tax filing or automatic transactions.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 6 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the selected private workspace's facts.json, decisions.json, rules.json, and relevant ledger data when available.

    line 13
  2. Very specific:

    Use the installed finance-core runtime for supported ledger calculations.

    line 19
  3. Very specific:

    Read the selected private workspace's setup.md and the active project's applicable AGENTS.md, when present, to resolve the interpreter and …

    line 23
  4. Distinctive:

    Keep scenario inputs, calculations and reports in the private workspace.

    line 29
  5. Distinctive:

    Use only the accounts and periods needed for that question.

    line 32
  6. Distinctive:

    Read planning methods for scenario design.

    line 37
  7. Distinctive:

    Do not treat net worth, retirement balances, or an estimated private mark as cash available for spending.

    line 50
  8. Very specific:

    If the user's question requires those extensions, calculate a separate documented scenario with sourced assumptions and show how it differs …

    line 68
  9. Very specific:

    Do not relabel unsupported extensions as outputs of finance-core plan.

    line 70
  10. Distinctive:

    Keep uncertain classification conditional.

    line 81
  11. Distinctive:

    Never save a researched interpretation as an immutable personal fact.

    line 83

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Finance plan

Answer the user's spending or planning question with explicit inputs. Separate facts, assumptions, calculations, and researched conclusions.

Establish the planning question

Read the selected private workspace's facts.json, decisions.json, rules.json, and relevant ledger data when available. Resolve superseded records before using them. Reuse confirmed goals and choices. Ask for missing information only when it changes the requested analysis; nationality, tax residence, dependents and employment cannot be inferred from balances, location, employer or account type.

Use the installed finance-core runtime for supported ledger calculations; inspect finance-core --help if needed. A review of supplied statements can proceed with private calculation artifacts without first initializing a complete ledger. It must be installed from the trusted project checkout in a dedicated environment. Read the selected private workspace's setup.md and the active project's applicable AGENTS.md, when present, to resolve the interpreter and any documented status or summary adapter. Reuse those interfaces where supported; keep the normalized workspace separate from the project's original records. Run the commands yourself and explain results and needed inputs in ordinary language. This skill does not require a sibling skill or a hosted research engine. Keep scenario inputs, calculations and reports in the private workspace.

For a budget or spending review, read spending review. Use only the accounts and periods needed for that question; a household spending review does not require fetching every investment account or tax document.

For a scenario, identify the horizon, base currency, goal cost/date, reliable net income, essential and discretionary expenses, irregular costs, and any committed debt payments. Read planning methods for scenario design. For tax, residency, benefits, or account eligibility questions, also read tax and jurisdiction research.

Check the account data

For plans that rely on account balances, run finance-core validate --workspace /private/path and finance-core summary --workspace /private/path --as-of YYYY-MM-DD for the plan date. Review freshness, account coverage, restrictions, FX dates, and missing information. For historical spending, also check transaction coverage for the requested period; a current balance does not establish a complete transaction history. Explain which missing inputs affect the question instead of withholding a supported partial review. Identify whether the plan needs cash, sale proceeds, borrowing, or restricted assets. Do not treat net worth, retirement balances, or an estimated private mark as cash available for spending.

Calculate a cash runway scenario

For a cash runway scenario, use explicit base-currency monthly amounts:

finance-core plan --workspace /private/path --as-of YYYY-MM-DD --monthly-expenses 3000 --monthly-income 2000 --one-time-cost 5000

These numbers are illustrative; replace all inputs with confirmed or clearly labeled scenario values. Supply income and one-time cost explicitly even when zero is the intended assumption. Unknown income is not verified zero income. Record whether recurring expenses already include debt payments and annual costs.

The current runtime uses unrestricted included cash in eligible accounts. It does not liquidate securities, forecast returns, estimate tax, or schedule repayments. If the user's question requires those extensions, calculate a separate documented scenario with sourced assumptions and show how it differs from the core result. Do not relabel unsupported extensions as outputs of finance-core plan.

Vary the assumptions that matter: income disruption, expense growth, one-time costs, timing, or an explicitly modeled asset sale. Show the downside as well as the base case. Avoid false precision in market returns, future compensation, or tax outcomes.

Apply personal and jurisdictional context

Research current official rules for the relevant year and jurisdiction when the answer depends on tax, residency, benefits, retirement access, or borrowing eligibility. Cite those rules and explain which confirmed facts make them applicable. Keep uncertain classification conditional; request the missing fact or identify the specific issue that needs a qualified professional's determination. Never save a researched interpretation as an immutable personal fact.

Deliver a usable plan

Lead with the result and conditions. Show input sources, dates, assumptions, scenario comparison, and the next action that the user can evaluate. Cite private files for personal figures and primary sources for external rules. Escape currency dollar signs. Save the plan as a dated private report. Confirmed choices may be recorded in decisions.json; unaccepted recommendations remain proposals. The workflow produces planning support, not a filing, loan approval, order or transfer.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.