android-deployment
Configure App Distribution — Signing, Obfuscation, and App Bundles for Android. Use when configuring Release build types, setting up signing configs, enabling R8/ProGuard minification, adding ProGuard keep rules, or preparing an .aab for Play Store submission. (triggers: build.gradle.kts, proguard-rules.pro, signingConfigs, proguard, minifyEnabled, isMinifyEnabled, isShrinkResources, .aab, releaseKeystore)
84
80%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/android/android-deployment/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines its scope (Android app distribution configuration), provides explicit trigger guidance with a 'Use when...' clause, and includes a comprehensive list of specific trigger terms. It uses proper third-person voice and is concise yet thorough, making it easy for Claude to distinguish from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: configuring Release build types, setting up signing configs, enabling R8/ProGuard minification, adding ProGuard keep rules, and preparing .aab for Play Store submission. | 3 / 3 |
Completeness | Clearly answers both 'what' (Configure App Distribution — Signing, Obfuscation, and App Bundles for Android) and 'when' (explicit 'Use when...' clause listing five specific scenarios, plus a parenthetical triggers list). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including file names (build.gradle.kts, proguard-rules.pro), config keywords (signingConfigs, minifyEnabled, isMinifyEnabled, isShrinkResources), and file extensions (.aab). These are terms developers would naturally use when discussing these tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Android app distribution configuration specifically around signing, obfuscation, and app bundles. The trigger terms are very specific to this domain (proguard-rules.pro, signingConfigs, .aab) and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
60%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is concise and well-structured with good progressive disclosure, but it falls short on actionability by lacking executable code examples (e.g., build.gradle.kts signing config blocks, proguard-rules.pro snippets). The biggest weakness is the absence of a clear workflow sequence with validation steps for what is inherently a multi-step, error-prone process (signing, obfuscation, bundle generation).
Suggestions
Add executable build.gradle.kts code snippets for signingConfigs, release buildType with isMinifyEnabled/isShrinkResources, and a sample proguard-rules.pro with @Keep usage.
Provide a numbered workflow sequence: 1) Configure signing config, 2) Set up release build type, 3) Add ProGuard rules, 4) Build .aab, 5) Validate (e.g., test with `bundletool` or verify mapping.txt exists), with explicit validation checkpoints.
Add a concrete example of environment variable usage for keystore credentials (e.g., System.getenv() in build.gradle.kts) to make the 'NEVER commit keystores' guidance actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every line conveys actionable configuration guidance without explaining what Android, ProGuard, or R8 are. No unnecessary padding or concept explanations. | 3 / 3 |
Actionability | Provides specific configuration directives (isMinifyEnabled, isShrinkResources, @Keep annotations, mapping.txt upload) but lacks executable code examples — no build.gradle.kts snippets, no signingConfigs block, no proguard-rules.pro examples. The guidance is concrete in intent but not copy-paste ready. | 2 / 3 |
Workflow Clarity | There is no sequenced workflow for configuring app distribution. Steps like setting up signing, enabling minification, adding ProGuard rules, building the .aab, and validating the output are not ordered or connected. For a multi-step process involving signing and obfuscation, there are no validation checkpoints (e.g., verifying the signed bundle, testing ProGuard rules don't strip needed classes). | 1 / 3 |
Progressive Disclosure | The skill provides a concise overview with a clear, one-level-deep reference to 'references/implementation.md' for detailed signing and R8 information. Content is appropriately split between the overview and the reference file. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
19a1140
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.