On the bundled docker-compose.yml: 17 findings (1 error, 11 warnings, 5 info) in 1 file from 17 rules - the archived MinIO image, port 9000 vs 8333, MINIO_ROOT_* keys, two bucket notifications.

Who it’s for
For platform and DevOps teams who run MinIO in docker-compose or Kubernetes and are moving to SeaweedFS.

What breaks, and when
The minio/minio repository is archived and the last community release is RELEASE.2025-10-15T17-29-55Z, so the image gets no updates; on SeaweedFS the MINIO_* keys are not read and bucket notifications stop.

What you get
• SKILL.md, an offline Node scanner (scripts/scan.js) and the 17-rule table

See it first
The real output of the bundled example is on getreadystack.com/skills/minio-seaweedfs-migration-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 want to move our object storage from MinIO to SeaweedFS. What in this repo has to change? Don’t edit anything yet.”. Needs Node 16+.

What it does not do
It does not start containers, call MinIO or SeaweedFS, or copy data; it reads text files 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 “minio-seaweedfs-migration-check.zip”.