On one 40-line app/build.gradle.kts it printed 14 findings (10 errors, 4 warnings) from 25 rules, each with file:line and the free replacement.

Who it’s for
For Android maintainers who want their app in F-Droid while the Play build keeps Firebase and Play Services.

What breaks, and when
While one non-free artifact sits on an unflavoured line, fdroidserver’s scanner rejects the build; apps built on AdMob are not found in the F-Droid repo at all.

What you get
• A scanner Claude runs over every .gradle, .kts and .toml file - not a guess…

See it first
The real output of the bundled example is on getreadystack.com/skills/fdroid-inclusion-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 publish our Android app on F-Droid but it uses Firebase and Google Play Services. Can you go through our Gradle files and tell me what they would reject and what a foss build would need instead? Don’t edit anything yet.”. Needs Node 16+.

What it does not do
Reads Gradle text only; it does not run Gradle, resolve transitive dependencies or scan .aar/.jar binaries.

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 “fdroid-inclusion-check.zip”.