CtrlK
BlogDocsLog inGet started
Tessl Logo

android-emulator-qa

Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A tight, action-oriented reference that sequences emulator QA workflows with concrete adb commands and verification loops. It assumes Claude's competence, externalizes helper utilities appropriately, and avoids concept padding.

DimensionReasoningScore

Conciseness

Lean command lists with brief, load-bearing context (e.g. 'Avoid edges ... to reduce accidental back gestures'); no explanation of what adb or an emulator is, so every token earns its place.

3 / 3

Actionability

Provides copy-paste-ready, executable commands with placeholders (e.g. 'adb -s <serial> exec-out screencap -p > /tmp/emu.png') plus real helper script invocations, hitting the top anchor.

3 / 3

Workflow Clarity

Numbered sequences in Quick start, Coordinate picking, and Logs include explicit checkpoints (resolve activity before launch) and a feedback loop (swipe, re-dump, re-search when a node is missing).

3 / 3

Progressive Disclosure

Well-organized into logical sections with helper logic externalized to two real one-level-deep scripts (scripts/ui_pick.py, scripts/ui_tree_summarize.py) referenced by path; no nested references and easy navigation.

3 / 3

Total

12

/

12

Passed

Description

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.

A concise, third-person description that names specific adb-driven capabilities and pairs them with an explicit 'Use when' trigger. It cleanly answers what the skill does and when to invoke it without fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture' — matching the anchor for several specific actions rather than a single domain mention.

3 / 3

Completeness

Explicitly answers both what (adb-driven launch/input/inspection/capture) and when via the 'Use when validating Android feature flows in an emulator' trigger, satisfying the top anchor.

3 / 3

Trigger Term Quality

Natural terms a user would say are present ('validating Android feature flows in an emulator', 'screenshots', 'logcat'); technical terms like 'adb' and 'UI-tree' are appropriate to the niche and not generic jargon.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (Android emulator QA via adb) with distinct triggers, making overlap with unrelated skills unlikely.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
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.