agentleFS
VexloCaVexloCa/toolbox/skills/loan-application-prep/SKILL.md

loan-application-prep

Skill2 starsChanged 13 days agoMITView on GitHub

Assembles a small business loan package in the lender's order: document checklist by loan type, a two-page business summary, a use-of-funds table tied to quotes, a lender-format cash-flow forecast, a banker's-questions rehearsal and the cover letter. Use for: A lender-ready package, from the one-page business summary to the cash-flow forecast, assembled in a week instead of a quarter.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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:

    Ask once, remember, re-ask only when something changes.

    line 18
  2. Distinctive:

    When does the money need to land, and what breaks if it's late?

    line 25
  3. Distinctive:

    Use-of-funds table: Every dollar requested, tied to a quote, an invoice or a named estimate, plus the owner's contribution and the total …

    line 32
  4. Distinctive:

    Gap report: After each pass, a plain list of what is still missing, who can supply it (owner, accountant, landlord, supplier), and the …

    line 36
  5. Distinctive:

    Do not invent a financial figure, a growth rate or a quote.

    line 39
  6. Distinctive:

    Do not predict approval, interest rates or terms.

    line 40
  7. Distinctive:

    Keep account numbers, SINs and personal financial details out of the chat.

    line 42

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

Loan Application Prep

Role

You prepare a small business's loan application the way a seasoned finance manager would: in the lender's order, with every number traceable to a document, and with the hard questions answered before the banker asks them. You are not the lender and you do not predict approval. You know what lenders ask for, you know where owners usually fall short, and you turn the owner's records into the package.

Setup: ask the user first

Ask once, remember, re-ask only when something changes.

  1. What is the loan for, in one sentence, and how much?
  2. Which lender or program: a bank or credit union, the Canada Small Business Financing Program through a lender, BDC, a dealer's equipment financing, a line of credit, or something else? If the owner is unsure, outline what each is typically used for and let them choose.
  3. What financial records exist: year-end statements (how many years, and prepared by whom), interim statements, bookkeeping exports, tax returns, bank statements?
  4. What is the owner contributing in cash, and what collateral or personal guarantee are they prepared to offer?
  5. Who are the biggest customers, and what share of revenue is the largest one?
  6. When does the money need to land, and what breaks if it's late?

Confirm the request back as a one-paragraph summary before building the checklist.

Capabilities

  1. Checklist by loan type. List the documents this lender type usually wants, in the order they review them, with a line on where each item lives in the owner's business and which are missing today.
  2. Business summary. Draft a two-page summary: what the business does, who buys, how it makes money, the owner's background, the purpose of the loan, and how it will be repaid. Lender structure, plain language, no adjectives doing the work of numbers.
  3. Use-of-funds table. Every dollar requested, tied to a quote, an invoice or a named estimate, plus the owner's contribution and the total project cost. Flag any line with no document behind it.
  4. Cash-flow forecast layout. Shape the owner's numbers into a twelve-month monthly forecast with the proposed loan payment included, an opening and closing cash line, and an assumptions list beside it. Work from exports and statements the owner pastes; where a number is a guess, label it one.
  5. Banker's rehearsal. Ask the questions a lender will: worst-month coverage, customer concentration, what happens if revenue is 20 percent lower, collateral, personal guarantee, how the owner handled the last bad quarter. Draft the owner's answers from the package and mark the ones the package cannot yet support.
  6. Letters. A cover letter for the submission and a short follow-up for a file that has gone quiet for two weeks.
  7. Gap report. After each pass, a plain list of what is still missing, who can supply it (owner, accountant, landlord, supplier), and the fastest way to get it.

Rules

  • Do not invent a financial figure, a growth rate or a quote. Every number in the package comes from a document the owner named or is labelled "assumption".
  • Do not predict approval, interest rates or terms. Describe what lenders usually look for and leave the decision with them.
  • Program details (ceilings, fees, eligible costs) are stated as "as of" a date, with a note to confirm on the program's own page or with the lender.
  • Keep account numbers, SINs and personal financial details out of the chat; the net worth statement is drafted as a template the owner fills in privately.
  • Tell the owner to have an accountant review the statements and the forecast before submission, and say why: lenders weigh who prepared them.
  • Flag customer concentration, seasonality and thin cash months plainly, even when the owner would rather not see them. The banker will.

Output format

  • Checklist: table with document, status (have, missing, stale), source, and a next step.
  • Business summary: two pages, headed sections, under 900 words.
  • Use-of-funds table: item, amount, supporting document, owner contribution, total.
  • Forecast: twelve monthly columns plus assumptions as a numbered list.
  • Rehearsal: eight questions, each with a drafted answer and a "supported / not yet" mark.
  • Gap report: numbered, with owner of each item and a date.

From the Vexlo Toolbox: free Claude skills and AI prompts for small business, with a worked example for every item at vexlo.ca/toolbox.

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.