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.

Quality

73%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.github/skills/android-emulator-skill/SKILL.md

Quality

Discovery

67%

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 effectively communicates specific Android development capabilities with good technical detail and a clear domain focus. However, it 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 beyond technical terminology.

Suggestions

Add a 'Use when...' clause with trigger scenarios like 'Use when the user asks about Android app testing, running emulators, building APKs, or debugging Android applications'

Include common user terms and file extensions: 'APK', 'adb', 'gradle', '.apk', 'Android Studio', 'device testing'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'semantic UI navigation, build automation, log monitoring, and emulator lifecycle management' along with 'testing, building, and automation'.	3 / 3
Completeness	Clearly describes WHAT it does (Android testing, building, automation with specific capabilities), but lacks an explicit 'Use when...' clause or trigger guidance for WHEN Claude should select this skill.	2 / 3
Trigger Term Quality	Includes relevant terms like 'Android', 'app testing', 'building', 'emulator', but missing common user variations like 'APK', 'adb', 'gradle', 'device', or file extensions users might mention.	2 / 3
Distinctiveness Conflict Risk	Clear niche focused specifically on Android app development workflows with distinct triggers like 'emulator', 'Android app', 'UI navigation' that are unlikely to conflict with general coding or other mobile platform skills.	3 / 3
	Total	10 / 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/error-handling workflows for build operations and lack of progressive disclosure to separate detailed script documentation.

Suggestions

Add validation checkpoints to the Quick Start workflow, e.g., 'If screen_mapper.py shows no elements, verify app launched successfully with app_launcher.py --list'

Include error handling guidance for build_and_test.py failures with a feedback loop (build -> check errors -> fix -> rebuild)

Consider linking to separate reference files for detailed script documentation (e.g., 'See [SCRIPTS_REFERENCE.md](SCRIPTS_REFERENCE.md) for complete option documentation')

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/python commands in the Quick Start section. Each script is documented with specific options and clear usage patterns that are immediately executable.	3 / 3
Workflow Clarity	The Quick Start provides a clear numbered sequence, but lacks validation checkpoints. For operations like building and testing apps, there's no explicit feedback loop for handling build failures or test errors before proceeding.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections, but all documentation is inline in a single file. The script descriptions could benefit from linking to separate detailed documentation files for advanced usage, especially for complex scripts like build_and_test.py.	2 / 3
	Total	10 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: new-silvermoon/awesome-android-agent-skills
Commit: 3f68e39

Reviewed: 17 days ago

Table of Contents

Discovery Implementation Validation

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.