Android Release Validation

Name: Android Release Validation
Author: hitoshura25

Checked

hitoshura25·vlatest·devops·Apache-2.0

Automates Android release validation checks, ensuring build quality, compliance, and identifying potential issues before distribution.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Run this in your project

terminal

$ npx skills add hitoshura25/claude-devtools --skill android-release-validation -a claude-code

Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

hitoshura25

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned 27 Sept 2026

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned hitoshura25/claude-devtools at 7c15955eb9.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: 7c15955eb9
Manifest: skills/android-release-validation/SKILL.md
Scanned: 4 files, 1,449 lines

This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.

What each check looks for →

About this skill

What it does

This skill automates the validation of Android release builds. It checks for common issues like missing icons, incorrect package names, and unsigned APKs before a release is pushed to production. The tool aims to reduce errors and ensure consistent build quality across releases.

When to use it

Before submitting an app update to the Google Play Store.
When preparing a beta release for internal testing.
As part of a continuous integration/continuous delivery (CI/CD) pipeline for Android apps.
To quickly verify that a newly built APK meets all required criteria.

Key capabilities

APK signature verification
Icon presence and resolution checks
Package name validation
Manifest file analysis

Example prompts

"Validate the release build located at /path/to/app.apk."
"Run Android release validation on the latest APK in the builds directory."
"Check if app.apk is properly signed and has all required icons."

Tips & gotchas

The skill requires access to the APK file being validated. Ensure that the AI agent has appropriate permissions to read the file location specified in the prompt.