On the bundled sample: 16 findings (15 errors, 1 warning) in 1 pom.xml from 16 rules, including oss.sonatype.org endpoints, gpg.skip true and a -SNAPSHOT dependency.

Who it’s for
Java library maintainers who publish to Maven Central and still have an OSSRH-era pom.xml from before the Central Portal.

What breaks, and when
Sonatype closed OSSRH to releases on 2025-06-30, so a deploy to oss.sonatype.org has nowhere to go; an unsigned bundle or one without sources and javadoc jars is rejected by Central validation.

What you get
• SKILL.md, an offline Node scanner and the 16-rule table
• file:line, severity and the reason for each blocker

See it first
The real output of the bundled example is on getreadystack.com/skills/maven-central-publish-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: “Is this project ready to publish to Maven Central? Check the pom.xml files. Don’t edit anything yet.”. Needs Node 16+.

What it does not do
It does not run Maven, resolve parent POMs or test your GPG key; no network calls, no edits without your OK.

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 “maven-central-publish-check.zip”.