credit-decisioning

Govern consumer credit AI decisioning with deny-by-default, auditable workflows.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/paulmalmquist/Consulting_app --skill credit-decisioning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: credit-decisioning
Source: https://github.com/paulmalmquist/Consulting_app/tree/main/.skills/credit-decisioning
Command: npx skills add https://github.com/paulmalmquist/Consulting_app --skill credit-decisioning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consumer credit decisioning is prone to governance gaps, opaque reasoning, and inconsistent output formats that complicate compliance and audits. This Skill enforces a deny-by-default governance model, traceable reasoning, and format-locked outputs to support auditable underwriting.

Core Features & Use Cases

  • Deny-by-default governance with strict knowledge boundaries and go/no-go decisioning policy.
  • Citation chains that map every assertion to a specific document passage for traceability.
  • Schema-locked outputs that align with compliance and audit requirements, including decision logs and policy references.

Quick Start

Provide a loan application and let the system generate a traceable decision with citations and a format-locked output.

Frequently Asked Questions about credit-decisioning

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

FAQPage Schema
How do I enforce an auditable AI credit decisioning workflow for loan origination?

You enforce auditable AI credit decisioning by applying a deny-by-default governance model with strict knowledge boundaries. The workflow maps every assertion to specific source documents via citation chains, producing traceable underwriting outcomes for compliance reviews.

What is deny-by-default governance in consumer credit underwriting?

Deny-by-default governance in credit underwriting applies strict knowledge boundaries and go/no-go policies. It defaults to rejecting applications unless explicitly approved, ensuring opaque AI reasoning cannot bypass policy governance during loan origination.

How do I generate format-locked outputs for compliance audits?

You generate format-locked outputs by schema-locking decision logs and policy references to audit requirements. This ensures consistent credit decisioning reports that compliance reviewers can validate against the walled garden of ingested documents.

Does this credit decisioning workflow require citation chains for every assertion?

Yes, citation chains are required for every AI assertion to map reasoning to specific document passages. This traceability prevents governance gaps and ensures all loan origination decisions remain fully auditable during compliance reviews.

Can I use this approach for risk management tasks beyond loan origination?

Yes, this approach applies to policy governance and audit-trail tasks across risk management. The walled garden of ingested documents and format-locked outputs support broader consumer credit compliance workflows beyond standard underwriting.

What are the limitations of using a walled garden for AI credit decisioning?

A walled garden limits AI credit decisioning to only ingested documents, preventing external data integration. This constraint ensures audit trail integrity but requires complete document ingestion beforehand for accurate risk management.