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

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/testing_and_automation/android-emulator-skill/SKILL.md

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with a copy-paste Quick Start and a well-organized script catalog pointing to real bundle files, but its workflows lack explicit validation checkpoints—important given the included batch/destructive operations—and the inlined option lists slightly duplicate '--help'.

Suggestions

Add explicit validation checkpoints to the Quick Start workflow (e.g. verify the app launched and is foreground before mapping; confirm the screen map found the target element before tapping) to lift workflow clarity above the cap.

Trim the inlined per-script option lists to the one or two most-used flags and defer the rest to '--help' to reduce redundancy and tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is a lean script catalog with concrete commands and assumes Claude's competence; the 'Key Design Principles' section mildly restates capabilities already shown, leaving minor trimmable over-explanation short of the 'every token earns its place' anchor.	4 / 5
Actionability	The Quick Start gives copy-paste-ready commands covering five common cases (health check, launch, map, tap, enter text) and each script lists concrete options, matching the 'fully executable, covers common cases' anchor.	5 / 5
Workflow Clarity	The Quick Start is a clear numbered sequence (check env → launch → map → tap → enter text) but has no validation checkpoints, and the skill includes batch/destructive operations (build_and_test/connectedCheck, uninstall APK), so workflow clarity is capped at 3 per the rubric guideline.	3 / 5
Progressive Disclosure	Well-organized categorized overview (Build, Navigation, Emulator Lifecycle) with one-level-deep references to real scripts (e.g. scripts/app_launcher.py); the inlined per-script option lists are mildly redundant with the noted '--help', leaving a minor organization gap short of the top anchor.	4 / 5
	Total	16 / 20 Passed

Description

75%Weight 40%Scale 1-5

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 is specific and distinctive with a clear Android-emulator niche, but it omits any 'Use when...' trigger guidance, capping completeness at 3, and lacks synonyms/file extensions that would push trigger-term quality to the top anchor.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases, e.g. 'Use when testing or building Android apps, driving an emulator, or navigating app UIs by element text/id.'

Include natural synonyms and file extensions users would say—'APK', '.apk', 'adb'—to improve trigger-term coverage toward the comprehensive anchor.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions—'semantic UI navigation, build automation, log monitoring, and emulator lifecycle management'—covering the Android testing/building/automation domain comprehensively, matching the 'comprehensive coverage' anchor.	5 / 5
Completeness	The 'what' is clearly stated (testing/building/automation of Android apps) but there is no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Good natural-term coverage ('Android app testing', 'build automation', 'log monitoring', 'emulator') but missing common synonyms and file extensions users would say (APK, .apk, adb), so it falls short of the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Android emulator/app automation with accessibility-driven navigation) with distinct triggers and minimal overlap risk with unrelated skills, matching the 'clear niche' anchor.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: new-silvermoon/awesome-android-agent-skills
Path: .github/skills/testing_and_automation/android-emulator-skill/SKILL.md
Commit: 82900ea

Reviewed: 1 day 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.