android
Workflow guide when working with Android builds or the mobile/ directory.
60
37%
Does it follow best practices?
Impact
100%
4.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/android/SKILL.mdQuality
Discovery
22%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 description is too vague to be effective for skill selection. It fails to specify what concrete actions or guidance it provides, relying on the generic term 'workflow guide.' While it mentions Android builds and the mobile/ directory, it lacks explicit trigger guidance and specific capabilities that would help Claude confidently select this skill over others.
Suggestions
Replace 'workflow guide' with specific actions like 'Guides building, testing, and debugging Android applications, configuring Gradle files, and managing APK outputs.'
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Android builds, Gradle configuration, APK generation, mobile/ directory structure, or mobile app compilation.'
Include more natural trigger terms users would say: 'APK', 'Gradle', 'Android Studio', 'mobile app build', 'emulator', '.apk', 'build.gradle'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('workflow guide') without listing any concrete actions. It doesn't specify what actions are performed—no mention of building, testing, debugging, configuring, or any other specific capability. | 1 / 3 |
Completeness | The 'what' is extremely weak ('workflow guide' is not a concrete capability description), and while 'when working with Android builds or the mobile/ directory' partially addresses 'when', there is no explicit 'Use when...' clause with clear triggers. The weak 'what' and only implied 'when' cap this at 1. | 1 / 3 |
Trigger Term Quality | It includes 'Android builds' and 'mobile/ directory' which are relevant keywords a user might mention, but misses common variations like 'APK', 'Gradle', 'mobile app', 'Android Studio', 'emulator', etc. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Android builds' and 'mobile/ directory' provides some specificity that distinguishes it from generic coding skills, but 'workflow guide' is so broad it could overlap with other Android or mobile development skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
52%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is extremely concise and token-efficient, providing a useful project-specific tip about using `./mach gradle` instead of `gradlew`. However, for a skill described as a 'workflow guide,' it is far too sparse — it lacks actual workflow steps, concrete examples, validation checkpoints, and references to related resources. It reads more like a single tip than a guide.
Suggestions
Add a multi-step workflow showing common Android build tasks (e.g., building, running tests, deploying) with concrete commands like `./mach gradle assembleDebug`.
Include at least one validation/verification step (e.g., how to confirm a successful build or check for errors).
Add concrete executable examples showing the `-p` flag usage, e.g., `./mach gradle -p mobile/android/app assembleDebug`.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean — only two sentences, both conveying non-obvious, project-specific information (use `./mach gradle` instead of `gradlew`, and the `-p` flag tip). No wasted tokens. | 3 / 3 |
Actionability | Provides a concrete command (`./mach gradle`) and mentions the `-p` argument, but lacks an executable example showing actual usage (e.g., a specific build or task command). A copy-paste-ready example would elevate this. | 2 / 3 |
Workflow Clarity | There is no sequenced workflow, no validation steps, and no guidance on what to do after running the command. For a skill described as a 'workflow guide,' the content is essentially a single tip rather than a workflow. | 1 / 3 |
Progressive Disclosure | The content is very short and well-organized with a clear heading, but for a skill meant to guide Android build workflows, there are no references to further documentation, common tasks, or troubleshooting resources that would be expected. | 2 / 3 |
Total | 8 / 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
- mozilla/enterprise-firefox
- Commit
cd457f4
- 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.