CtrlK
BlogDocsLog inGet started
Tessl Logo

android-ui-journey-testing

XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.

66

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

92%

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

The content is highly actionable with a clear, validated workflow and no padding, but it keeps all detail — including two lengthy examples — inline rather than progressively disclosing it via reference files.

Suggestions

Move the full Example 2 JSON outcome report and/or the full Example 1 journey XML into a references/ file, linking to them from a concise inline excerpt to reduce SKILL.md length.

Consider extracting the ADB command reference (tap/swipe/text syntax) into a short references/cheatsheet so the main body stays a focused overview.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it defines only skill-specific terms ('journey', 'source of truth') and avoids explaining basic Android/ADB concepts.

3 / 3

Actionability

Provides fully executable ADB commands (input tap/swipe/text), complete XML and JSON examples, and an explicit tap-center formula — copy-paste ready.

3 / 3

Workflow Clarity

A clear 4-step sequence reinforced by a mermaid diagram includes explicit fail-fast handling (FAILED/SKIPPED) and assertion verification as validation checkpoints.

3 / 3

Progressive Disclosure

Sections are well organized, but at over 50 lines the two full inline examples (complete journey XML and full JSON report) could be split into reference files; no bundle structure is present to offload detail.

2 / 3

Total

11

/

12

Passed

Description

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.

The description is specific and distinct but incomplete: it conveys concrete capabilities without any explicit 'when to use' trigger, and its keyword phrasing is more technical than natural.

Suggestions

Append a 'Use when...' clause naming natural triggers, e.g. 'Use when testing Android app UI flows end-to-end, or when the user mentions journey tests, UI verification, or ADB-driven test automation.'

Soften jargon toward user-spoken terms — pair 'assertion verification' with 'checking expected screen state' and 'interactive step execution' with 'tapping and typing through screens'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'interactive step execution', 'assertion verification', and 'JSON outcome reporting' — rather than vague language.

3 / 3

Completeness

It clearly states what the skill does but offers no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 2 per the rubric.

2 / 3

Trigger Term Quality

Relevant keywords (Android, UI, testing, JSON) appear, but the phrasing leans technical ('assertion verification', 'interactive step execution') and lacks natural user-spoken variations.

2 / 3

Distinctiveness Conflict Risk

The XML-specified Android UI journey testing niche is specific and unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
sickn33/antigravity-awesome-skills
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.