Skip to content
cccskills
FreePublished on GitHub

credit-memo

Write a credit memo for a lending decision: borrower story, facility structure, repayment sources, financial-ratio spread with covenant headroom, risk factors with mitigants, risk-rating rationale, and a recommendation. Use when asked to write a credit memo, credit application, credit paper, loan write-up, or prepare a deal for credit committee. Produces a complete credit memo ready for committee review.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md5.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Credit Memo Skill

A credit memo has one job: let a committee member who has never met the borrower decide whether the bank gets its money back. This skill writes that document — the story, the structure, the numbers, and the risks — with the discipline that every risk carries a mitigant or an explicit acceptance, and every rating has a stated rationale.

What This Skill Produces

  • A borrower story (business, ownership, management, why they need the money)
  • A facility structure table (amount, tenor, pricing, security, guarantees, covenants)
  • Repayment sources: primary, secondary, tertiary — each tested
  • A financial-ratio spread with trends and covenant headroom
  • Risk factors, each paired with a mitigant or an explicit acceptance
  • Risk-rating rationale and a clear recommendation

Required Inputs

Ask for what's missing; from a thin brief, draft with every inferred figure labelled [assumed — verify]:

  • Borrower — business, ownership, years operating, management
  • Request — facility type, amount, tenor, purpose, proposed pricing and security
  • Financials — 2–3 years of revenue, EBITDA, debt, interest expense, working capital; projections if available
  • Existing exposure and relationship history
  • Proposed covenants and the institution's rating scale, if available

Credit Framework

Borrower story. What the business does, who owns and runs it, and why they need the money now — growth, refinance, working-capital cycle, or distress dressed as growth. The purpose must match the tenor and structure (don't fund long-term assets with short-term debt).

Repayment sources — the core of the memo:

  • Primary: operating cash flow. Test with DSCR = cash available for debt service ÷ total debt service. Common framing: ≥1.25x is conventional comfort; 1.0–1.25x is tight and needs a covenant fence; <1.0x means the deal relies on the secondary source — say so in those words.
  • Secondary: collateral. State value, valuation date and basis, advance rate, and realistic liquidation value under stress — not appraisal value.
  • Tertiary: guarantor/sponsor support. Verified net worth and liquidity, and the honest note that guarantees are a negotiating position, not cash.

Ratio spread. Show at least: leverage (Debt/EBITDA), DSCR, interest coverage, current ratio, and any sector-critical metric — 2–3 years of trend, not a snapshot. Frame thresholds as conventional reference points and calibrate to the institution's grid. For each proposed covenant, compute day-one headroom: (actual − required) ÷ required.

Risks and mitigants. Every risk gets a structural mitigant (covenant, security, guarantee, pricing) or an explicit acceptance with rationale ("accepted: single-customer concentration, mitigated partially by 3-year contract; residual risk accepted given…"). A mitigant-free risk list is a memo that hasn't finished its job.

Rating and recommendation. State the rating driver in one sentence (cash-flow strength, leverage, collateral quality, or sector) and what would move it a notch either way. Recommend: approve / approve with conditions (name them) / decline.

Output Format

Credit memo: [borrower / facility / date]

1. Recommendation & rating — up front: approve/conditions/decline, proposed rating, one-paragraph why. 2. Borrower story — business, ownership, management, purpose. 3. Facility structure — table: facility | amount | tenor | pricing | security | guarantees. 4. Repayment sources — primary / secondary / tertiary, each tested with numbers. 5. Financial spread — table: metric | FY-2 | FY-1 | current | proj | covenant | headroom. 6. Risks & mitigants — table: risk | mitigant or explicit acceptance | residual. 7. Conditions & covenants — with day-one headroom.

End with: "This memo is analytical support, not a credit decision. Approval authority, rating, and terms follow your institution's credit policy and applicable regulation."

Quality Checks

  • Purpose, tenor, and structure are consistent (no long assets on short money)
  • All three repayment sources are addressed; if primary DSCR <1.0x the memo says the deal leans on collateral
  • Collateral is valued on realistic liquidation basis with valuation date stated
  • Every risk has a mitigant or an explicit, reasoned acceptance — none is bare
  • Ratios show trend, not a single year; covenant headroom is computed
  • Rating rationale names its driver and the notch-mover in both directions
  • Assumed figures are labelled [assumed — verify]

Anti-Patterns

  • Do not list a risk without a mitigant or an explicit acceptance — bare risk lists are unfinished analysis
  • Do not let the borrower's narrative substitute for the numbers — reconcile story and spread, and flag where they disagree
  • Do not count a guarantee as a repayment source without verified guarantor liquidity
  • Do not use appraisal value as liquidation value
  • Do not bury the recommendation at the end — committee reads it first
  • Do not fabricate financials from a thin brief — label every inferred number

Example Trigger Phrases

  • "Write a credit memo."
  • "Write up this loan for credit committee."
  • "Prepare a deal for credit committee."
  • "Spread these financials and check covenant headroom."

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

The English summary is being prepared. Showing the original description.

mohitagw15856/pm-claude-skills1.5KUpdated Oct 23, 2026

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

The English summary is being prepared. Showing the original description.

mohitagw15856/pm-claude-skills1.5KUpdated Oct 23, 2026

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

The English summary is being prepared. Showing the original description.

mohitagw15856/pm-claude-skills1.5KUpdated Oct 23, 2026

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

The English summary is being prepared. Showing the original description.

mohitagw15856/pm-claude-skills1.5KUpdated Oct 23, 2026

Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.

The English summary is being prepared. Showing the original description.

mohitagw15856/pm-claude-skills1.5KUpdated Oct 23, 2026

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

The English summary is being prepared. Showing the original description.

mohitagw15856/pm-claude-skills1.5KUpdated Oct 23, 2026

See all skills by mohitagw15856

Report a problem with this skill