Diagnose application-to-funded fall-out stage-by-stage and name the worst fallout stage — fix it before buying more apps. Reach for this on a pull-through question.
Installs into .claude/skills of the current project.
Are you the author of Diagnose Pullthrough?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/mcorbett51090-diagnose-pullthrough)
---
name: diagnose-pullthrough
description: "Diagnose application-to-funded fall-out stage-by-stage and name the worst fallout stage — fix it before buying more apps. Reach for this on a pull-through question."
---
# Skill: Diagnose pull-through
Buying more applications into a leaking funnel wastes spend (§3 #1).
## Step 1 — Map the stages
App → approved → clear-to-close → funded, with the rate at each (§3 #1).
## Step 2 — Find the worst fallout
Lowest stage rate via `mortgage_lending_calc.py pullthrough` (§3 #1).
## Step 3 — Localize the cause
Cycle bottleneck, documentation, or a compliance step (route the compliance cause out, §3 #6).
## Step 4 — Fix the leak first
Then buy more apps — not before (§3 #1).
## Output
A stage-by-stage fallout read naming the worst fallout stage and the fix. Traverse Tree 1 in the decision-trees file.
