Traces a reconciliation break back to the source GL entry and subledger transaction, then writes a one-sentence diagnosis explaining what differs and why. It pulls posting metadata from both sides via MCP servers, diffs attributes like FX rates, posting dates, and account mappings, and outputs a structured root cause with an owner and recommended action. Use this after gl-recon has flagged the break but before you write any adjustments. The real value is speed: instead of manually pulling trade IDs and journal entries from two systems, you get "Subledger used WM/R 4pm rate; GL used Bloomberg close" in one shot. It won't fix the break, but it will tell you whether to monitor, escalate, or suppress.
npx skills add https://github.com/anthropics/financial-services --skill break-trace