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.
82
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 a strong skill description that clearly defines its scope around Android release configuration and publishing. It uses precise, domain-specific terminology that Android developers would naturally use, and includes an explicit 'Use when...' clause with well-chosen trigger scenarios. The description is concise yet comprehensive, covering the key capabilities without unnecessary verbosity.
| 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) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a user would say: 'release signing', 'R8', 'obfuscation', 'App Bundle', 'signing configs', 'minification', 'ProGuard', 'keep rules', 'Play Store'. These are the exact terms Android developers use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche in Android release/publishing configuration. The specific terms like 'R8', 'ProGuard', 'App Bundle', and 'Play Store' make it very 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-organized with appropriate progressive disclosure, but it lacks executable code examples (e.g., a Gradle `signingConfigs` block or `build.gradle.kts` snippet) and a clear sequential workflow for the multi-step deployment setup process. The anti-patterns section adds value but the overall actionability suffers from the absence of concrete, copy-paste ready configuration.
Suggestions
Add executable Gradle code examples for signing config setup, R8 enablement, and AAB build commands (e.g., a complete `signingConfigs` block and `buildTypes` block in `build.gradle.kts`).
Structure the content as a numbered workflow: (1) configure signing, (2) enable R8/minification, (3) add ProGuard rules, (4) validate with a release build, (5) verify mapping.txt generation — with explicit validation checkpoints at each stage.
Include a sample ProGuard/R8 rules file snippet showing minimal keep rules alongside the `@Keep` annotation recommendation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every bullet point conveys actionable information without explaining basic Android concepts Claude already knows. No padding or unnecessary context. | 3 / 3 |
Actionability | Provides specific guidance (e.g., `isMinifyEnabled = true`, use `@Keep` annotations, upload `mapping.txt`) but lacks executable code examples such as a Gradle signing config block or a sample ProGuard rules file. The instructions describe what to do rather than providing copy-paste ready snippets. | 2 / 3 |
Workflow Clarity | There is no sequenced workflow for the multi-step process of configuring signing, enabling R8, and preparing for Play Store submission. Steps are presented as unordered bullet points with no validation checkpoints or feedback loops for verifying the build configuration works correctly. | 1 / 3 |
Progressive Disclosure | The skill is a concise overview with a clear one-level-deep reference to `references/implementation.md` for detailed signing and R8 information. Content is well-organized into logical sections (Build Configuration, Proguard/R8, Anti-Patterns, References). | 3 / 3 |
Total | 9 / 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
4c72e76
- 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.