android-emulator-skill
Production-ready scripts for Android app testing, building, and automation. Provides semantic UI navigation, build automation, log monitoring, and emulator lifecycle management. Optimized for AI agents with minimal token output.
Install with Tessl CLI
npx tessl i github:new-silvermoon/awesome-android-agent-skills --skill android-emulator-skill72
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
50%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description effectively communicates specific Android development capabilities with good technical detail and a clear niche. However, it critically lacks explicit trigger guidance ('Use when...') which would help Claude know when to select this skill, and could benefit from more natural user-facing keywords.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about Android app testing, building APKs, running emulators, or automating mobile UI tests'
Include common user terms and file extensions: 'APK', 'adb', 'gradle', '.apk', 'mobile testing', 'Android Studio'
Add natural language triggers users might say: 'run on emulator', 'build Android app', 'test mobile app'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'semantic UI navigation, build automation, log monitoring, and emulator lifecycle management'. These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Describes what the skill does well, but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'Android', 'app testing', 'building', 'emulator', but missing common user variations like 'APK', 'adb', 'gradle', 'mobile app', or file extensions users might mention. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on Android-specific tooling with distinct triggers like 'emulator', 'Android app', and 'UI navigation'. Unlikely to conflict with general coding or other mobile platform skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that provides actionable guidance for Android emulator automation. Its strengths are token efficiency and concrete executable commands. The main weaknesses are missing validation checkpoints in workflows (especially for build/install operations) and lack of progressive disclosure to separate detailed script documentation from the overview.
Suggestions
Add validation steps to the Quick Start workflow, e.g., 'Verify app launched: python scripts/screen_mapper.py | grep AppName'
Include error recovery guidance for common failures (emulator not booted, app crash, element not found)
Consider moving detailed script options to a separate REFERENCE.md and linking from the main skill file
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of basic concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context about what Android or emulators are. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready bash and Python commands in the Quick Start section. Each script is documented with specific options and clear use cases. | 3 / 3 |
Workflow Clarity | The Quick Start provides a clear numbered sequence, but lacks validation checkpoints or error recovery guidance. For operations like building and installing apps, there's no explicit 'verify success before proceeding' step. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is inline in one file. The script descriptions could benefit from linking to detailed documentation files for advanced usage rather than listing all options inline. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 12 / 16 Passed | |
- 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.