agentleFS
d-wweid-wwei/openclaw-financial-services/skills/fsi-fa-check-model/SKILL.md

fsi-fa-check-model

Skill16 starsChanged 9 months agoApache-2.0View on GitHub

description: Debug and audit financial models for errors — circular references, broken formulas, hardcoded overrides, balance sheet imbalances, cash flow mismatches, and logic gaps. Use when a model isn't tying, producing unexpected results, or before sending to a client or IC. Triggers on "debug model", "model check", "audit model", "model won't balance", "something's off in my model", "check my model", "QA model", or "model review". Tab & Layout Review: - Are inputs clearly separated from calculations? - Is there a…

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. About 0 are common, 15 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈15

    Distinctive · estimate

    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
  1. Distinctive:

    Check for hardcoded numbers inside formulas (partial hardcodes)

    line 28
  2. Distinctive:

    Check for inconsistent formulas across row/column ranges (should be the same formula dragged across)

    line 29
  3. Distinctive:

    If imbalanced, quantify the gap and trace where it breaks

    line 37
  4. Distinctive:

    Check that retained earnings rolls forward correctly: Prior RE + Net Income - Dividends = Current RE

    line 38
  5. Distinctive:

    Verify goodwill and intangibles flow from acquisition assumptions (if M&A model)

    line 39
  6. Distinctive:

    Check for circular references (interest expense → debt balance → cash → interest)

    line 55
  7. Distinctive:

    If intentional (common in LBO/3-statement models), verify the iteration toggle works

    line 56
  8. Distinctive:

    If unintentional, trace the loop and suggest how to break it

    line 57
  9. Distinctive:

    Do growth rates make sense?

    line 62
  10. Distinctive:

    Do leverage ratios go negative or exceed realistic bounds?

    line 71
  11. Distinctive:

    Do linked cells actually match their source?

    line 75
  12. Distinctive:

    Do units match (thousands vs.

    line 77
  13. Distinctive:

    Always check the BS balance first — if it doesn't balance, nothing else matters until it does

    line 135
  14. Distinctive:

    If the model uses VBA macros, note any macro-driven calculations that can't be audited from formulas alone

    line 139
  15. Distinctive:

    Don't change the model without asking — report issues and let the user decide how to fix

    line 140

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Model Checker

description: Debug and audit financial models for errors — circular references, broken formulas, hardcoded overrides, balance sheet imbalances, cash flow mismatches, and logic gaps. Use when a model isn't tying, producing unexpected results, or before sending to a client or IC. Triggers on "debug model", "model check", "audit model", "model won't balance", "something's off in my model", "check my model", "QA model", or "model review".

Workflow

Step 1: Ingest the Model

  • Accept the user's Excel model (.xlsx or .xlsm)
  • Identify model type: DCF, LBO, merger, 3-statement, comps, returns, or custom
  • Map the structure: which tabs exist, how they're linked, where inputs vs. outputs live

Step 2: Structural Checks

Tab & Layout Review:

  • Are inputs clearly separated from calculations?
  • Is there a consistent color-coding convention? (blue = input, black = formula, green = link)
  • Are there hidden tabs or rows that could contain overrides?
  • Is the model flow logical? (assumptions → IS → BS → CF → valuation)

Formula Consistency:

  • Check for hardcoded numbers inside formulas (partial hardcodes)
  • Check for inconsistent formulas across row/column ranges (should be the same formula dragged across)
  • Identify any #REF!, #VALUE!, #N/A, #DIV/0! errors
  • Flag cells that are formatted as formulas but contain hardcoded values

Step 3: Integrity Checks

Balance Sheet:

  • Total Assets = Total Liabilities + Equity (every period)
  • If imbalanced, quantify the gap and trace where it breaks
  • Check that retained earnings rolls forward correctly: Prior RE + Net Income - Dividends = Current RE
  • Verify goodwill and intangibles flow from acquisition assumptions (if M&A model)

Cash Flow Statement:

  • Ending cash from CF = Cash on BS (every period)
  • Operating CF + Investing CF + Financing CF = Change in Cash
  • D&A on CF matches D&A on IS
  • Capex on CF matches PP&E rollforward on BS
  • Working capital changes on CF match BS movements (AR, AP, inventory)

Income Statement:

  • Revenue builds tie to segment/product detail
  • COGS and gross margin are consistent with assumptions
  • Tax expense = Pre-tax income × tax rate (check for deferred tax adjustments)
  • Share count ties to dilution schedule (options, converts, buybacks)

Circular References:

  • Check for circular references (interest expense → debt balance → cash → interest)
  • If intentional (common in LBO/3-statement models), verify the iteration toggle works
  • If unintentional, trace the loop and suggest how to break it

Step 4: Logic Checks

Reasonableness:

  • Do growth rates make sense? (100%+ revenue growth without explanation = red flag)
  • Are margins within industry norms? Flag outliers
  • Does terminal value dominate the DCF? (>75% of EV from TV is a yellow flag)
  • Are projections hockey-sticking unrealistically?
  • Does EBITDA growth compound to an absurd number by Year 10?

Sensitivity & Edge Cases:

  • What happens at 0% growth? Negative growth?
  • Does the model break with negative EBITDA?
  • Do leverage ratios go negative or exceed realistic bounds?
  • Are there any divide-by-zero risks?

Cross-Tab Consistency:

  • Do linked cells actually match their source? (copy-paste errors are common)
  • Are date headers consistent across all tabs?
  • Do units match (thousands vs. millions vs. actuals)?

Step 5: Common Bugs by Model Type

DCF:

  • Discount rate applied to wrong period (mid-year vs. end-of-year convention)
  • Terminal value not discounted back correctly
  • WACC uses book values instead of market values
  • FCF includes interest expense (should be unlevered)
  • Tax shield double-counted

LBO:

  • Debt paydown doesn't match cash sweep mechanics
  • PIK interest not accruing to debt balance
  • Management rollover not reflected in returns
  • Exit multiple applied to wrong EBITDA (LTM vs. NTM)
  • Fees and expenses not deducted from Day 1 equity

Merger Model:

  • Accretion/dilution uses wrong share count (pre- vs. post-deal)
  • Synergies not phased in correctly
  • Purchase price allocation doesn't balance
  • Foregone interest on cash not included
  • Transaction fees not in sources & uses

3-Statement:

  • Working capital changes have wrong sign convention
  • Depreciation doesn't match PP&E schedule
  • Debt maturity schedule doesn't match principal payments
  • Dividends paid exceed net income without explanation

Step 6: Report

Generate a model audit report:

Summary:

  • Model type and overall assessment (Clean / Minor Issues / Major Issues)
  • Number of issues found by severity

Issue Log:

#TabCell/RangeSeverityCategoryDescriptionSuggested Fix
1Critical/Warning/InfoFormula/Logic/Balance/Hardcode

Severity Definitions:

  • Critical: Model produces wrong output (BS doesn't balance, formulas broken)
  • Warning: Model works but has risks (hardcodes, inconsistent formulas, edge case failures)
  • Info: Style and best practice suggestions (color coding, layout, naming)

Step 7: Output

  • Issue log table (in chat or Excel)
  • Annotated model with comments on flagged cells (if user provides the file)
  • Summary assessment with fix priority

Important Notes

  • Always check the BS balance first — if it doesn't balance, nothing else matters until it does
  • Hardcoded overrides are the #1 source of model errors — search aggressively for them
  • Sign convention errors (positive vs. negative for cash outflows) are extremely common
  • Models that "work" can still be wrong — sanity-check outputs against industry benchmarks
  • If the model uses VBA macros, note any macro-driven calculations that can't be audited from formulas alone
  • Don't change the model without asking — report issues and let the user decide how to fix

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.