On the bundled sample: 13 findings (9 errors, 4 warnings) in 1 file from 9 rules, including a fully unstructured Dbtr address and Ctry ITA instead of IT.

Who it’s for
Payments engineers at banks and fintechs who generate pacs.008 or pain.001 XML and own the address mapping.

What breaks, and when
A malformed hybrid address may be rejected rather than repaired, and AdrLine past character 70 is truncated on the wire. Swift deferred the November 2026 cutover in August 2026; a new date is due by December 2026.

What you get
• SKILL.md, an offline Node scanner and the 9-rule table
• file:line, the party and the value that broke each rule

See it first
The real output of the bundled example is on getreadystack.com/skills/iso20022-cbpr-address-check/ — free, no sign-up, so you see what it finds before you pay.

Install in 30 seconds
Unzip into ~/.claude/skills/, then ask Claude Code: “We send pacs.008 payment files to our bank. Are the postal addresses in these XML files ready for the structured address change? Don’t edit anything yet.”. Needs Node 16+.

What it does not do
Not a full XSD validation: postal addresses only, unprefixed tags only.

FAQ
Q: How is this different from asking Claude without the skill?
A: The skill carries a dated rule table and a scanner that reads every file, so Claude quotes the exact date and line instead of guessing from memory.
Q: How do I get the files?
A: In your Whop library after paying: the lesson “iso20022-cbpr-address-check.zip”.