Inspect apk
Skill jason0404/Jason-Android-Marketplace/plugins/android-artifact-inspector/skills/inspect-apk
A Claude Code marketplace for Android development, featuring code review, localization management, and APK/AAB release artifact inspection tools.
npx -y skills add jason0404/Jason-Android-Marketplace --skill inspect-apkAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Inspect an Android APK for release metadata, permissions, components, native libraries, size and security concerns
SKILL.md
1.3 KB, as published. Nobody here has run it
Inspect the user's APK as an untrusted build artifact. Do not install or run it.
Workflow
- Confirm the
.apkpath exists and record file name and file size. - Locate Android SDK tooling cross-platform: try tools available in PATH, then locations discoverable through
ANDROID_HOME, then any path supplied by the user. Never hard-code a macOS path. - Invoke
android-apk-analyzer. - Use
apkanalyzerwhere available to gather package/version, manifest data, permissions, DEX/resources/files, ABI libraries and major size contributors. - Invoke
android-apk-signing-verifierwhen signature confirmation is requested or needed for release delivery. - Invoke
android-artifact-report-generatorwhen the user requests a report or final deliverable.
Rules
- Report only fields confirmed through tool output.
- Treat tokens, credentials and sensitive metadata as redacted content.
- List unavailable SDK tools as verification limitations.
- Never modify the input APK.
Output
Provide the inspected artifact, tools used/unavailable, confirmed metadata, findings ordered by severity, verification steps and report path when generated.