loan-application-explanation

Generate Reg B/ECOA-compliant loan decision explanations with reason codes.

1|1|Updated Feb 19, 2026

Search Tags:#compliance #explanation #loan #adverse action #ECOA #Reg B

Ready to run

npx skills add https://github.com/GoldenZero/skills --skill loan-application-explanation-goldenzero

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: loan-application-explanation
Source: https://github.com/GoldenZero/skills/tree/main/skills/loan-application-explanation
Command: npx skills add https://github.com/GoldenZero/skills --skill loan-application-explanation-goldenzero

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

This Skill provides clear, compliant explanations for loan approval or denial decisions, ensuring regulatory adherence and borrower transparency.

Core Features & Use Cases

Adverse Action Notices: Generates notices compliant with Reg B/ECOA.
Decision Transparency: Explains credit decisions and conditions to applicants.
Reason Code Generation: Produces Reg B/ECOA-compliant reason codes.
Use Case: When a loan officer needs to explain to a borrower why their application was denied, this skill can generate a clear, compliant explanation detailing the specific factors that led to the decision.

Quick Start

Explain my loan application in simple words and next steps.

Frequently Asked Questions about loan-application-explanation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate compliant adverse action notices for loan denials under Reg B?▼

Compliant adverse action notices for loan denials are generated by parsing application data and credit reports to rank contributing factors by materiality, producing borrower-facing narratives with regulatory reason codes required under Reg B and ECOA.

What is the best way to explain loan approval conditions to a borrower transparently?▼

Explaining loan approval conditions transparently involves ranking decision factors by materiality from policy overlays and decision outputs, then composing clear borrower-facing narratives that detail the specific conditions and contributing factors.

How do I map ECOA reason codes to specific loan application deficiencies?▼

ECOA reason codes are mapped to loan application deficiencies by parsing application data, credit reports, and decision outputs to rank factors by materiality, ensuring the generated codes accurately reflect the specific reasons for the credit decision.

Can I create internal audit trails for loan decisions to meet ECOA compliance requirements?▼

Internal audit trails for loan decisions meeting ECOA compliance requirements are created by parsing application data and policy overlays to document the ranked contributing factors and regulatory reason codes that drove the final approval or denial.

Do I need credit report data to generate compliant loan denial explanations?▼

Credit report data is needed to generate compliant loan denial explanations, as the Skill parses credit reports alongside application data and decision outputs to accurately rank contributing factors by materiality for the borrower-facing narrative.

Why does my loan application explanation lack specific regulatory reason codes?▼

A loan application explanation may lack regulatory reason codes if the input application data, credit reports, or decision outputs are incomplete, preventing the system from ranking factors by materiality to produce compliant Reg B reason codes.