Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cbrock84/financial-modeling
Builds and stress-tests financial models for forecasting, scenario planning, and decision support — revenue build, cost structure, driver logic, and the sensitivities that show where a plan breaks. Use this to model a decision's financial consequence, build a forecast or long-range plan, evaluate an investment or hire, or pressure-test someone else's model before relying on it.
Passed 21 of 22 test cases with the skill, and 11 of 22 without it.
and 10 more in the full report
10 fixed11 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
What documentation metadata must accompany every line item listed on the input sheet of a project finance model?
| Checked | Without skill | With skill |
|---|---|---|
| The input sheet requirements mandate specifying a documented source for every assumption. | Passed | Passed |
| The input sheet requirements mandate specifying a date for every assumption. | Missed | Passed |
The instructions your model reads when the skill loads.
A model is an argument about how the business works, expressed in arithmetic. Its value is the argument, not the output precision.
Three separated layers, always:
One row, one calculation, carried consistently across periods. Models become unauditable through inconsistent rows more than through complexity.
Never grow a top-line by a percentage. Build it: volume × price, or accounts × retention × expansion. Driver-based models can be argued with, and being argued with is the point — a growth rate cannot be wrong, only optimistic.
Cost structure separated into fixed, variable, and step-fixed. The step-fixed items are where plans break, because they move in jumps nobody modeled.
A single-scenario model tells you nothing about risk. For every model, produce:
If a plan only works in the base case, that is the finding.
The description of a model is not evidence about the model. Check these, in this order, because
test cases passed, vs 11 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.