financial-modeling
Skill62 starsChanged 12 days agoMITView on GitHub
Build auditable financial models and business cases for investment, valuation, cost-benefit, and build-versus-buy decisions. Use for cash-flow projections, NPV, IRR, ROI, payback, TCO, break-even, and sensitivity analysis.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- KMaruthi2002/universal-llm-skillstheir own version, first seen Oct 25, 2026
- poorvith-mp/skills-financetheir own version, first seen Oct 11, 2026
- ZeroTokenClaw/agents-skillstheir own version, first seen Sep 21, 2026
- magnus919/agent-skillstheir own version, first seen Jul 21, 2026
- claude-office-skills/claude-office-plugintheir own version, first seen Mar 9, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- claude-office-skills/skills★ 433same name
- magnus919/agent-skills★ 172same name
- claude-office-skills/claude-office-plugin★ 9same name
- elvismusli/business-validator★ 1same name
- KMaruthi2002/universal-llm-skills★ 1same name
- nisarth/claude-skills-store★ 1same name
- poorvith-mp/skills-finance★ 1same name
- ZeroTokenClaw/agents-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- change-managementSkill
- client-deliverablesSkill
- due-diligenceSkill
- engagement-pricingSkill
- engagement-setupSkill
- implementation-planningSkill
- org-designSkill
- process-excellenceSkill
- project-closeoutSkill
- project-governanceSkill
- proposal-developmentSkill
- strategic-analysisSkill
- thought-leadershipSkill
- workshop-facilitationSkill
- writing-styleSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Use cash-flow and return conventions for calculations and technology and TCO economics for build-versus-buy, automation, or AI investments.
- Distinctive: line 33
Test funding feasibility separately from investment return.
- Distinctive: line 41
Check signs, units, timing, totals, baseline treatment, cost and benefit overlap, terminal assumptions, and sensitivity direction.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Financial Modeling
Build the financial evidence for the user's decision. Work at the requested scope: checking a calculation, comparing investments, constructing a workbook, or valuing a business. Preserve supplied assumptions, horizons, conventions, and approved decisions; challenge a material inconsistency explicitly.
Establish the model basis
Use provided data first. Identify missing drivers and continue portions they do not block. Ask when a missing input prevents a defensible result; otherwise show a disclosed assumption, range, or symbolic formula. Keep hypothetical examples separate from client estimates. Never invent costs, forecasts, benchmarks, or evidence for a benefit.
For the model being built, define relevant conventions: currency and units, valuation date, cash-flow timing, horizon, baseline, inflation treatment, taxes, financing, working capital, and terminal value. Compare options on the same basis. Historical actuals, supplied forecasts, sourced estimates, and unsupported placeholders remain distinguishable.
Maintain one source for each assumption. Record its value, unit, period, basis, source, and limitation in a register when the model's size warrants one; for a short calculation, put the assumptions beside the result. Treat a management forecast as a forecast even if it arrives in a polished workbook.
Model the incremental economics
Calculate cash flows relative to the stated baseline. Include continuing the current course or deferral when relevant, without reopening an approved choice just to add an option. Avoid counting the same benefit as labor savings, productivity, and revenue uplift. Separate time released, usable capacity, realized cash savings, and additional output.
Use cash-flow and return conventions for calculations and technology and TCO economics for build-versus-buy, automation, or AI investments. Use valuation and uncertainty methods only when DCF, scenario probabilities, Monte Carlo, EVA, MIRR, or options are relevant.
Use available calculation tools for material arithmetic. Show formulas and enough intermediate results to reproduce the answer. In a workbook, link outputs to inputs, keep assumptions separate from formulas, label units and periods, and make scenarios update the model consistently. Recalculate where tools allow and inspect the saved output; disclose if formula results could not be refreshed.
Test the decision
Test funding feasibility separately from investment return. A positive NPV does not solve an interim cash shortfall. Examine payment timing, committed financing, capacity, and other hard constraints before recommending approval.
Find the inputs that can change the recommendation and vary them over plausible ranges. Show the break-even or switching threshold. Do not mechanically apply ±10%, increase discount rates because data is missing, or assign probabilities without a basis. Preserve conflicting sources and show their decision effect. Distinguish scenario assumptions from forecasts and avoid counting the same risk in both cash-flow haircuts and discount-rate adjustments without explaining why.
Present and verify
Lead with the recommendation, investment, financial result, funding requirement, and principal limitation. Report only metrics that help this decision. Use compact numeric tables and explain assumptions beside them. State the downside being accepted and what would change the choice. Where essential evidence is absent, a conditional decision or deferral can be the supported answer.
Check signs, units, timing, totals, baseline treatment, cost and benefit overlap, terminal assumptions, and sensitivity direction. For file requests, deliver the working artifact and a concise explanation of how to change its assumptions. Do not claim independent verification or audit assurance beyond the checks performed.
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
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.

