On one 17-line compose.yaml it printed 6 findings (3 errors, 3 warnings) from 10 rules, each with file:line and the Podman fix.

Who it’s for
For developers and platform teams replacing Docker Desktop with Podman or rootless Podman on their laptops, CI runners and dev containers.

What breaks, and when
The day Docker Desktop is uninstalled, /var/run/docker.sock, docker-credential-desktop, the docker.internal names and the docker-desktop context are gone; the stack fails.

What you get
• A scanner Claude runs over every compose file, Dockerfile, devcontainer.json…

See it first
The real output of the bundled example is on getreadystack.com/skills/docker-desktop-to-podman-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’re uninstalling Docker Desktop and moving the team to rootless Podman next sprint. Can you go through our compose files, Dockerfiles and scripts and tell me what will stop working? Don’t edit anything yet.”. Needs Node 16+.

What it does not do
Reads text files only; it does not start Podman or check Kubernetes manifests.

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 “docker-desktop-to-podman-check.zip”.