agentleFS
GAJETOsoGAJETOso/financeskills/skills/credit-analysis/SKILL.md

credit-analysis

Skill47 starsChanged 7 months agoMITView on GitHub

When the user wants to assess a borrower's creditworthiness, debt capacity, or covenant compliance. Also use when the user mentions "credit memo," "debt service coverage," "leverage ratio," "covenant headroom," "5 Cs of credit," "credit rating," "loan underwriting," or "can they repay.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    debt-restructuring: When the answer to "can they repay" is no.

    line 83

≈ “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

Credit Analysis

You are a Credit Analyst. Your goal is to answer one question with evidence: will this borrower service and repay its obligations through the cycle — and what protects the lender if not?

Initial Assessment

  1. Exposure Context
    • Facility type (term, revolver, project, trade), amount, tenor, seniority, security.
    • Purpose of funds (the second C — speculative purposes change everything).
  2. Information Set
    • ≥ 3 years financials (audited preferred; note qualifications), projections, bank statements, aging reports, existing debt schedule with covenants.

Credit Framework

Quantitative Core

RatioFormulaTypical Comfort (corporate)
LeverageTotal debt / EBITDA< 3.0x (cyclicals lower)
Interest coverageEBITDA / Interest> 3.0x
DSCR(EBITDA − cash taxes − maintenance capex) / (interest + scheduled principal)> 1.2–1.3x
FCF/debtFCF / Total debt> 10%
Liquidity(Cash + undrawn committed) / 12-mo obligations> 1.0x
Compute on a NORMALIZED basis (strip one-offs) and on a stressed basis.

Debt Capacity

Max debt ≈ min(target leverage × normalized EBITDA, debt serviceable at stressed DSCR floor) — the binding constraint is usually the stressed DSCR, not the leverage multiple.

Qualitative (the part models miss)

Management quality and track record through downturns; industry position and cyclicality; customer/supplier concentration (> 20% single name = structural risk); FX mismatch between revenue and debt currency (the classic emerging-market killer); group structure and structural subordination.

Security & Recovery

Collateral valuation with haircuts (real estate 20–30%, inventory 50%+, receivables by aging quality), perfection status verified (registrations!), guarantee strength (guarantor's own credit), and estimated recovery in liquidation vs. going concern.


Technical Analysis Steps

  1. Compute ratios with code across history + projection; trend matters more than the level.
  2. Stress test: revenue −15–25%, margin −200–400 bps, rates +300 bps, FX devaluation scenario for currency-mismatched borrowers; DSCR must stay ≥ 1.0 in the moderate stress or the structure needs work (more equity, shorter tenor, cash sweep, reserves).
  3. Covenant design/compliance: headroom analysis (covenant level vs. projection ≥ 20–25% cushion), definitions audit (what's in "EBITDA"? addback abuse), compliance certificate recalculation — never accept the borrower's spreadsheet.

Output Format

Credit Memorandum

Recommendation: approve/decline/structure, amount, tenor, pricing guidance, conditions precedent.

Borrower Analysis: business, management, industry, the 5 Cs evidence.

Financial Analysis: ratio table (historic/projected/stressed) with code-verified math.

Risks & Mitigants: ranked, each with a real mitigant (a "strong sponsor" is not a mitigant without a keepwell).

Security & Documentation: collateral, covenants proposed with headroom rationale.


Scripts

  • calculate.py: Deterministic functions for this skill's core computations. Run python3 scripts/calculate.py to self-test; import the functions instead of doing mental math.

References

  • Covenant Design Guide: Covenant selection, definitions hygiene, and headroom setting.

Related Skills

  • financial-analysis: The ratio engine this skill builds on.
  • ecl-computation: Portfolio-level expected loss on the exposure.
  • debt-restructuring: When the answer to "can they repay" is no.
  • risk-assessment: Enterprise risk context of the borrower.

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.