On the bundled sample: 6 findings (6 errors, 0 warnings) in 1 file from 12 rules, including a missing buyer SIREN and a VAT key of 12 where the SIREN gives 43.

Who it’s for
For developers and finance-IT teams who generate UBL, CII or Factur-X invoices for French B2B customers from an ERP or billing app.

What breaks, and when
Without the BT-24 profile URN the PDP cannot decide the flow; a missing buyer SIREN or delivery address breaks the reform’s mandatory mentions, and art. L441-10 wants the 40 EUR recovery indemnity on every B2B invoice.

What you get
• SKILL.md, an offline Node scanner and the 12-rule table

See it first
The real output of the bundled example is on getreadystack.com/skills/france-einvoice-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 export UBL invoices for our French B2B customers. Will these XML files pass a PDP under the French e-invoicing reform, and what mentions are missing? Don’t edit anything yet.”. Needs Node 16+.

What it does not do
Not tax advice; no full Schematron, no PDF parsing, no INSEE lookup.

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 “france-einvoice-check.zip”.