android-deployment
Configure release signing, R8 obfuscation, and App Bundle publishing for Android. Use when setting up signing configs, enabling minification, adding ProGuard keep rules, or preparing for Play Store submission.
58
68%
Does it follow best practices?
Impact
—
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 a specific Android release preparation domain with concrete actions and explicit trigger guidance. It uses third person voice, includes highly relevant natural keywords, and has a well-structured 'Use when' clause that covers the key scenarios. The description is concise yet comprehensive, making it easy for Claude to distinguish this skill from others.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Configure release signing', 'R8 obfuscation', 'App Bundle publishing', 'signing configs', 'enabling minification', 'adding ProGuard keep rules', and 'Play Store submission'. | 3 / 3 |
Completeness | Clearly answers both 'what' (configure release signing, R8 obfuscation, App Bundle publishing for Android) and 'when' (explicit 'Use when' clause with specific triggers: setting up signing configs, enabling minification, adding ProGuard keep rules, preparing for Play Store submission). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'release signing', 'R8', 'obfuscation', 'App Bundle', 'signing configs', 'minification', 'ProGuard', 'keep rules', 'Play Store'. These cover both technical and common user terminology for Android release preparation. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche focused on Android release/publishing pipeline. Terms like 'R8 obfuscation', 'ProGuard keep rules', 'App Bundle', and 'Play Store submission' are very specific and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
37%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 avoids unnecessary explanation, but it critically lacks actionability—there are no executable code snippets, Gradle configuration examples, or concrete commands. The workflow is presented as unordered guidelines rather than a clear sequence with validation steps, which is problematic for a multi-step deployment process involving signing, obfuscation, and publishing.
Suggestions
Add concrete Gradle code snippets for signing config setup, R8 enablement, and App Bundle building (e.g., a complete `signingConfigs` block and `buildTypes` block).
Provide a sequenced workflow: 1) Configure signing → 2) Enable R8/shrinking → 3) Add ProGuard rules → 4) Build release bundle → 5) Verify with `bundletool` or test install → 6) Upload to Play Console.
Include a minimal but complete ProGuard/R8 rules example showing @Keep usage and a sample keep rule, rather than just describing the approach abstractly.
Add a validation checkpoint such as verifying the signed AAB with `jarsigner -verify` or testing the release build on a device before submission.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what R8, ProGuard, or App Bundles are, correctly assuming Claude's competence. Every bullet point conveys a specific, non-obvious directive. | 3 / 3 |
Actionability | The skill provides only high-level directives without any concrete code, commands, or executable examples. There are no Gradle snippets for signing configs, no example ProGuard rules, and no build commands—just abstract instructions like 'enable isMinifyEnabled = true' without showing where or how. | 1 / 3 |
Workflow Clarity | There is no sequenced workflow for the multi-step process of configuring signing, enabling R8, adding ProGuard rules, and publishing. Steps are presented as unordered bullet points with no validation checkpoints (e.g., verifying the signed bundle, testing the release build). | 1 / 3 |
Progressive Disclosure | The skill references 'references/implementation.md' for detailed signing and R8 information, which is a good structural choice. However, no bundle files are provided, so the reference is unverifiable, and the single reference covers two distinct topics that could benefit from clearer signaling. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
556618c
- 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.