7 prompts that run the applied risk judgment calls on your own numbers: VaR breach triage, wrong way risk pricing, the funding ladder gap, the hedge defence, a fat tail fit the data has to earn, and an input check that catches the model taking a desk assumption on faith. For risk managers, model validation leads, and CROs.
Free — runs in your own ClaudeTechnical setup · 4 steps7 ready-to-run prompts
Three minutes, four steps, nothing to install by hand
Claude sets it up for you. You just paste.
Never used Claude? It is free and takes 30 seconds to open. Copy the instruction below, paste it into Claude, and it reads this page and walks you through everything, one question at a time.
1
Tell Claude how to talk to you
One tap. It changes how much Claude explains, and how slowly it goes. You can change it any time.
2
Copy your setup instruction
A short instruction plus a link to this page lands on your clipboard. First copy asks for your email once. That unlocks every button across the whole library.
3
Open Claude in a new tab
Free account, no card, 30 seconds. This tab stays open so you can come back.
Claude reads this page, asks one question about your work, then guides you step by step until your first output is right. If anything looks wrong, tell Claude what you see, and it fixes it with you.
▸Prefer the full prompt instead of the link? (optional)
Set me up with The FRM Part II Risk Judgment Pack in my own Claude. There is nothing to install and nothing to download: this is a prompt pack I run inside Claude on my own data.
Guide: https://consultance.ai/library/frm-risk-judgment-pack
What it does: 7 prompts that run the applied risk judgment calls on your own numbers: VaR breach triage, wrong way risk pricing, the funding ladder gap, the hedge defence, a fat tail fit the data has to earn, and an input check that catches the model taking a desk assumption on faith. For risk managers, model validation leads, and CROs.
I am comfortable copy-pasting and following instructions, but I am not a developer.
Rules:
- Plain English. Define jargon the first time it appears (repo, env var, port, dependency).
- One step at a time. Exact command in a code block. Tell me which app to paste it into (Terminal on Mac, PowerShell on Windows).
- One sentence per command explaining what it does and what success looks like.
- After each command, wait. I will tell you the output before you move on.
- If a tool is missing (git, node, docker, python), give me the one-line install for my OS first.
- If something errors, diagnose before the next step. Do not skip.
First message: ask only "What is your operating system, macOS, Windows, or Linux?" Then start step 1.
Setup steps from the public guide (adapt them to me, do not just paste them at me):
1. Start a new Claude project and pin Claude Opus 5. Prompt 01 sets up the desk and asks what you are running and where the data sits.
2. Load your P&L series, position file, and risk factor history the way prompt 01 asks, then run 02 through 06 in order.
3. Run prompt 07 last and never skip it. It re-reports every conclusion as inputs only and flags anything taken from a desk instead of re-estimated.
4. Treat a refusal as a result. If prompt 06 declines to fit a tail because the sample is too small, that is the correct answer, not a failed run.
Stop when I have run the first prompt on my own data and confirmed the output looks right.
Step 2 · run it on your data
Step 1 set it up. These 7 prompts do the work.
the vault
The 7 prompts
Grab the whole pack as one file, or tap any prompt below to copy it on its own. Placeholders that look like {{THIS}} get swapped for your own numbers — and if you ran Step 1, Claude fills them in for you.
One .md file · all 7 prompts, numbered, in order · nothing left out.
You are my risk desk, acting as four people on every answer: a market risk manager, a credit risk analyst, a treasury ALM lead, and an independent model validation reviewer.
Ask me and wait:
1. What am I running? (A) a VaR breach post mortem (B) counterparty exposure on one name or book (C) a funding and liquidity review (D) a hedge decision (E) a full validation pass across all of it
2. Where is the data? (A) I upload the P&L series, position file, and risk factor history (B) I paste the series (C) the Claude add-in for Excel on the risk workbook
3. Context: portfolio, book size, confidence level and holding period, and the committee this goes to?
Confirm the setup, then wait for my files. On every answer: state the assumption doing the work, the input it depends on, and what would have to be true for the conclusion to flip. Never report a number without naming the input that drives it. Flag anything you cannot tie to my data. End with: "Decision support, not a validation opinion. A named risk officer signs."
Using the data from prompt 01, take each VaR breach in the period and classify it: a genuine tail event the model was never meant to capture, or a model failure. For each, show the realised loss against the VaR, the risk factor moves that drove it, and whether the factor move sat inside the model's calibration window. Do not let a cluster of breaches pass as bad luck without testing independence. Output one table plus the classification reasoning for each breach. A named risk officer signs.
Price the counterparty exposure on the book from prompt 01 with wrong way risk explicitly modelled, not bolted on. Identify where exposure and counterparty credit quality are driven by the same factor, state the correlation you are assuming and where it came from, and show expected exposure with and without the wrong way adjustment. If the data cannot support a correlation estimate, say so and stop rather than assume zero. A named risk officer signs.
Build the funding and liquidity ladder from my data, then attack it. Find the maturity bucket where the gap is covered only by an assumption: rollover at current rates, an undrawn facility, or a deposit that is modelled as sticky. For each, state the assumption, the bucket it rescues, and the stress that breaks it. Report the first bucket that fails under stress, not the average. A named treasury officer signs.
Given the hedge choices in my data, price each one and then argue against the cheapest. State the basis risk, the residual exposure it leaves, and the scenario where the cheaper hedge underperforms the expensive one badly enough to matter. Conclude with a recommendation and the single input that would change it. Do not present cost as the deciding factor on its own. A named risk officer signs.
Fit the loss distribution in my data. Report the tail parameter, the sample size in the tail, and the confidence interval around the estimate. If the number of tail observations is too small to support the fitted parameter, refuse to report a fitted tail and say what data would be needed instead. Then identify the single correlation or dependence assumption carrying the largest share of the resulting capital number, and show the capital figure with that assumption moved to a plausible worst case. A named risk officer signs.
Re run the conclusions from prompts 02 through 06, but this time report only the inputs, not the answers.
For every number you produced: name the input, state whether you re estimated it from my data or took it as given from a desk, a vendor, or my own file, and give the date of the underlying data.
Then flag every input you accepted without re estimating, and re run any conclusion that depended on one. Volatility, correlation, recovery rates, and rollover assumptions are the usual offenders.
Report any conclusion that changes. If none change, say so explicitly and list what you checked. A named risk officer signs.
Got the prompts. Want them wired into your actual stack? We map that on a free AI audit.
7 prompts that run the applied risk judgment calls on your own numbers: VaR breach triage, wrong way risk pricing, the funding ladder gap, the hedge defence, a fat tail fit the data has to earn, and an input check that catches the model taking a desk assumption on faith
Path A · free
You just did it
The setup rail and every prompt above are free and stay free. The cost is your time, and the risk of wiring it wrong on live data.
• Run last quarter's numbers first. Live data is not a test bed.
• Nothing here uploads to us. It runs in your own Claude account, on your own machine.
• A named human reviews and signs every output before it reaches a board, lender, or client.
• Mask account numbers and names to the minimum the task needs.
the fine print
Straight answers on ownership
Prompt set authored by consultance.ai. This is decision support, not a validation opinion, a regulatory filing, or investment advice, and it does not satisfy an independent validation requirement on its own. Tail estimates from small samples stay unstable regardless of phrasing. A named risk officer signs every number before it reaches a committee, a regulator, or a board. Your data stays in your own Claude tenant, we never see it.
Want this running in your business, not just your laptop? We build it and hand you the keys.
The FRM Part II Risk Judgment Pack is a finance and data build in the consultance.ai AI Build Library. 7 prompts that run the applied risk judgment calls on your own numbers: VaR breach triage, wrong way risk pricing, the funding ladder gap, the hedge defence, a fat tail fit the data has to earn, and an input check that catches the model taking a desk assumption on faith. For risk managers, model validation leads, and CROs. It fits Market and credit risk managers, model validation and model risk leads, treasury ALM, and CROs who sign off on numbers that go to a committee and want the assumption behind each one named before they do. Setup difficulty is Technical, with 4 plain-English steps.
What does The FRM Part II Risk Judgment Pack do?
7 prompts that run the applied risk judgment calls on your own numbers: VaR breach triage, wrong way risk pricing, the funding ladder gap, the hedge defence, a fat tail fit the data has to earn, and an input check that catches the model taking a desk assumption on faith. For risk managers, model validation leads, and CROs.
Who is The FRM Part II Risk Judgment Pack for?
It fits Market and credit risk managers, model validation and model risk leads, treasury ALM, and CROs who sign off on numbers that go to a committee and want the assumption behind each one named before they do.
How hard is The FRM Part II Risk Judgment Pack to set up?
Technical to set up — one guided setup instruction covering 4 plain-English steps, plus 7 ready-to-run prompts on the resource page.
How would consultance.ai build this out?
The pack is seven prompts you run by hand on one book at a time. Consultance wires it into your own environment: your risk warehouse and position files connected under governed access, the input check running on every model output rather than when someone remembers, and an evidence trail your validation function can read. Reply "wire it" for a 30-minute slot.
What are the licensing terms?
Prompt set authored by consultance.ai. This is decision support, not a validation opinion, a regulatory filing, or investment advice, and it does not satisfy an independent validation requirement on its own. Tail estimates from small samples stay unstable regardless of phrasing. A named risk officer signs every number before it reaches a committee, a regulator, or a board. Your data stays in your own Claude tenant, we never see it.
Want this built into your workflow?
The FRM Part II Risk Judgment Pack is the starting point. On a free AI audit we map where it fits your stack and what consultance.ai would build around it.