On one 13-line README it printed 6 findings (4 errors, 2 warnings) from 10 rules, each with file:line and the rule’s official source.

Who it’s for
For maintainers of open-source encryption libraries and the US companies that publish crypto code on GitHub.

What breaks, and when
BIS removed License Exception TSU / EAR 740.13(e) for source code in the 20 September 2016 rule (81 FR 64656); notices that still cite it, or call 5D002 source EAR99, point at rules that no longer apply.

What you get
• A scanner Claude runs over every Markdown file - not a guess from memory

See it first
The real output of the bundled example is on getreadystack.com/skills/encryption-export-notice-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 publish an encryption library on GitHub and our README has an old export control section. Can you check whether it still matches the current BIS rules? Don’t edit anything yet.”. Needs Node 16+.

What it does not do
Reads Markdown only; it does not classify your product, file with BIS or NSA, or give legal advice.

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 “encryption-export-notice-check.zip”.