New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Android UI Journey Testing

by sickn33 in sickn33/agentic-awesome-skills

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

MITAuto-check passedMobile

Install Android UI Journey Testing

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill android-ui-journey-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills android-ui-journey-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/android-ui-journey-testing .claude/skills/android-ui-journey-testing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
android-ui-journey-testing
GitHub stars
47k
Used in
1 other repo
Token cost
~1.9k tokens
SKILL.md length
584 words
Files
1
Skills in repo
1,493
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 4 steps: Parse the Journey Specification → Sequential Step Evaluation → Handle Failures and Crashes → …
  • Tasks that involve Android development
  • SKILL.md covers Overview, When to Use, How It Works and Examples, plus 3 more sections
  • Calls adb; needs REDACTED_PASSWORD

What it does

Android UI Journey Testing is an agent skill from sickn33/agentic-awesome-skills. XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Mobile, covering Android development. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • Tasks that involve Android development

Example prompts

  • “/android-ui-journey-testing”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Parse the Journey Specification
  2. Sequential Step Evaluation
  3. Handle Failures and Crashes
  4. Generate JSON Report

What it can do on your machine

Read from SKILL.md and the folder at commit 680176d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • adb

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • REDACTED_PASSWORD

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Android UI Journey Testing loads about 1.9k tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 584 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~37
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit 680176d, republished under its MIT licence (© sickn33). 584 words, ~1,916 tokens.

Download SKILL.mdSave it as .claude/skills/android-ui-journey-testing/SKILL.md (or your agent's skills folder).
name
android-ui-journey-testing
description
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
category
testing
risk
critical
source
self
source_type
self
date_added
2026-06-18
author
Owais
tags
android, journey-testing, ui-verification, testing, adb, automation
tools
claude, cursor, gemini, antigravity

Android UI Journey Testing

Overview

This skill outlines the standard workflow for running XML-specified User Journey tests on Android applications. A "journey" is a sequenced set of user actions and state assertions designed to verify end-to-end functionality. The journey XML acts as the source of truth for the app's behavior. The executor proceeds sequentially, performing UI interactions, checking state assertions, and writing a standardized JSON outcome report.

When to Use

  • Use when evaluating an Android application's UI behavior against an XML test specification.
  • Use when automating multi-step user flows (e.g., login, checkout, navigation) and verifying expectations.
  • Use when running verification tests and generating standardized JSON test reports.
  • Use when debugging application flows on physical devices or emulators using ADB commands.

How It Works

mermaid
graph TD
    A[Parse Journey XML] --> B[Execute Action / Interaction]
    B --> C{Success?}
    C -- Yes --> D[Verify State Expectation / Assertion]
    C -- No/Crash --> G[Mark FAILED & Exit]
    D -- Passed --> E{More Steps?}
    D -- Failed --> G
    E -- Yes --> B
    E -- No --> F[Output JSON Summary]
Step 1: Parse the Journey Specification

Read and parse the XML test suite structure. The root node <journey> defines the test case name, and the <actions> block contains the sequence of test steps.

xml
<journey name="Search and Cart Flow">
   <description>Verify that searching for an item and adding it to the cart succeeds.</description>
   <actions>
      <action>Search for soda</action>
      <action>Tap the first search result</action>
      <action>Verify that the product detail screen is shown</action>
   </actions>
</journey>
Step 2: Sequential Step Evaluation

Process each <action> element in the exact order specified. Test steps are classified into two groups:

A. Interactive Actions (Taps, Swipes, Text Input)

Perform the physical UI interaction using ADB.

  • Tapping: Tap the center of the target element's bounds:
    bash
    adb shell input tap <x> <y>
  • Swiping/Scrolling: Swipe from coordinate to coordinate with a duration:
    bash
    adb shell input swipe <x1> <y1> <x2> <y2> <duration_ms>
  • Text Typing: Type text into the active input field:
    bash
    adb shell input text "<string>"

If the element is missing or the action cannot be performed, the action and the journey fail.

B. State Assertions (Expectation Verification)

Steps beginning with "verify", "check", or "ensure" represent state assertions.

  • Inspect the current screen (using screenshots or uiautomator dump) without interacting or scrolling.
  • Confirm all sub-assertions are met. For example, "Verify that the app is on the Home screen and the logo is visible" fails if the home screen is not displayed or the logo is missing.
Step 3: Handle Failures and Crashes

If the application crashes, exits, freezes, or fails an assertion:

  1. Immediately stop journey execution.
  2. Mark the failed step as FAILED.
  3. Mark any subsequent steps as SKIPPED.
  4. Document the exact reason for failure.
Show full SKILL.md (245 more words)Show less
Step 4: Generate JSON Report

Format the execution results into a standardized JSON schema and write it to the output log.

Examples

Example 1: Full Journey XML Specification
xml
<journey name="Login and Profile Edit">
   <description>Logs into the app, navigates to settings, and changes user profile information.</description>
   <actions>
      <action>Verify that the username input field is visible</action>
      <action>Tap the username input field</action>
      <action>Type "testuser" into the input</action>
      <action>Tap the password input field</action>
      <action>Type a redacted test password into the input</action>
      <action>Tap the "Login" button</action>
      <action>Verify that the Home dashboard is visible and user profile photo is shown</action>
   </actions>
</journey>
Example 2: Standard JSON Outcome Report
json
{
  "journey": "Login and Profile Edit",
  "results": [
    {
      "action": "Verify that the username input field is visible",
      "status": "PASSED",
      "commands": [],
      "comment": "Username input detected at bounds [100,200][980,300] via UI dump."
    },
    {
      "action": "Tap the username input field",
      "status": "PASSED",
      "commands": [
        "adb shell input tap 540 250"
      ],
      "comment": "Tapped center coordinates of username input."
    },
    {
      "action": "Type \"testuser\" into the input",
      "status": "PASSED",
      "commands": [
        "adb shell input text \"testuser\""
      ],
      "comment": "Username typed successfully."
    },
    {
      "action": "Tap the password input field",
      "status": "PASSED",
      "commands": [
        "adb shell input tap 540 370"
      ],
      "comment": "Tapped center of password input."
    },
    {
      "action": "Type a redacted test password into the input",
      "status": "PASSED",
      "commands": [
        "adb shell input text \"[REDACTED_PASSWORD]\""
      ],
      "comment": "Password typed successfully. The actual input value was not stored in the report."
    },
    {
      "action": "Tap the \"Login\" button",
      "status": "PASSED",
      "commands": [
        "adb shell input tap 540 500"
      ],
      "comment": "Login button clicked."
    },
    {
      "action": "Verify that the Home dashboard is visible and user profile photo is shown",
      "status": "FAILED",
      "commands": [],
      "comment": "Dashboard loaded but profile photo was missing from the UI header."
    }
  ]
}

Best Practices

  • ✅ Calculate Centers for Taps: When parsing element bounds like [x1,y1][x2,y2], always compute the middle coordinate: $$x_{center} = \frac{x_1 + x_2}{2}, \quad y_{center} = \frac{y_1 + y_2}{2}$$
  • ✅ Include Sleep Buffers: Always add a short delay (e.g., 1-2 seconds) after interactive actions (like button taps) to let layouts and transitions render before executing assertions.
  • ✅ Fail Fast: Stop the test immediately upon encountering the first failure. Continuing after a failure leads to invalid results.
  • ✅ Log Precise Commands Safely: Include non-sensitive raw commands (such as adb shell input tap) in the JSON output list for diagnostics. Redact text entered into password, OTP, token, payment, or personal-data fields; never persist the literal secret in reports, CI logs, or shared artifacts.

Limitations

  • The parser only evaluates the static screen hierarchy (e.g. uiautomator dump). Elements that require scrolling are marked as not visible unless a scrolling action is explicitly performed.
  • Non-standard UI components (like custom OpenGL canvas views) cannot be read via standard accessibility trees and may require screenshot analysis or hardcoded click maps.
  • Key events and text typing via ADB do not trigger standard soft keyboard events on all emulator images, which can lead to input validation issues.
  • @android-cli - General CLI tool syntax, package install, and device queries.
  • @android_ui_verification - Direct ADB script templates for general UI checks.

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/android-ui-journey-testing of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit 680176d

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Android UI Journey Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Android UI Journey Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Android UI Journey Testing this skillsickn33/agentic-awesome-skills47k1 repos~1.9kAutomated safety check: PassMIT
Compose Multiplatform Patternsmonta-app/ocpp-emulator1805 repos~2kAutomated safety check: PassApache-2.0
Kotlin Patternsgetknit/knit1325 repos~4.7kAutomated safety check: PassGPL-3.0
Stylesarindamxd/camerax-android1324 repos~2.3kAutomated safety check: PassApache-2.0
Jetpack Compose Expertaldefy/compose-skill596—~4.8kAutomated safety check: PassCustom licence
Verified Emailarindamxd/camerax-android1324 repos~4.7kAutomated safety check: PassApache-2.0

Similar skills

  • Compose Multiplatform Patterns

    monta-app/ocpp-emulator

    Compose Multiplatform and Jetpack Compose patterns for KMP projects — state management, navigation, theming, performance, and platform-specific UI.

    180 GitHub starsUsed in 5 repos~2k tokens
    MobileAuto-check passed

  • Kotlin Patterns

    getknit/knit

    Idiomatic Kotlin patterns, best practices, and conventions for building robust, efficient, and maintainable Kotlin applications with coroutines, null safety, and DSL builders.

    132 GitHub starsUsed in 5 repos~4.7k tokens
    MobileAuto-check passed

  • Styles

    arindamxd/camerax-android

    A skill your agent uses to integrate the Jetpack Compose Styles API into an Android project.

    132 GitHub starsUsed in 4 repos~2.3k tokens
    MobileAuto-check passed

  • Jetpack Compose Expert

    aldefy/compose-skill

    Guides Jetpack Compose and Compose Multiplatform work across Android, Desktop, iOS and web, plus Android TV, Material 3 motion, paging, navigation and design-to-code.

    596 GitHub stars~4.8k tokensUpdated 2 mo ago
    MobileAuto-check passed

  • Verified Email

    arindamxd/camerax-android

    Provides a complete workflow for implementing verified email retrieval on Android Credential Manager API.

    132 GitHub starsUsed in 4 repos~4.7k tokens
    MobileAuto-check passed

  • Compose UI

    Moustachauve/WLED-Android

    Best practices for building UI with Jetpack Compose, focusing on state hoisting, detailed performance optimizations, and theming.

    169 GitHub starsUsed in 3 repos~676 tokens
    MobileAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,493 skills in this repo

  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed

  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed

  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed

  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Categories

Questions about Android UI Journey Testing

What does Android UI Journey Testing do?

XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting. Android UI Journey Testing is an agent skill from sickn33/agentic-awesome-skills. XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.

When should I use Android UI Journey Testing?

Android UI Journey Testing fits situations like: tasks that involve Android development.

How do I install Android UI Journey Testing in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill android-ui-journey-testing -a claude-code`. Or copy the skill folder (skills/android-ui-journey-testing in sickn33/agentic-awesome-skills) into .claude/skills/android-ui-journey-testing in your project. Claude Code loads it when a task matches its description.

How do I install Android UI Journey Testing in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill android-ui-journey-testing -a codex`. Or copy the skill folder (skills/android-ui-journey-testing in sickn33/agentic-awesome-skills) into .agents/skills/android-ui-journey-testing in your project. Codex loads it when a task matches its description.

Can I use Android UI Journey Testing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill android-ui-journey-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/android-ui-journey-testing, .gemini/skills/android-ui-journey-testing, .github/skills/android-ui-journey-testing and .opencode/skills/android-ui-journey-testing in your project.

What does Android UI Journey Testing need to run?

Going by SKILL.md and its folder, Android UI Journey Testing needs the command-line tools its instructions call (adb) and credentials named REDACTED_PASSWORD.

Does Android UI Journey Testing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Android UI Journey Testing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Android UI Journey Testing use?

Android UI Journey Testing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Android UI Journey Testing use?

About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Android UI Journey Testing?

Skills that share tags, products or a category with Android UI Journey Testing: Compose Multiplatform Patterns (monta-app/ocpp-emulator, 180 stars), Kotlin Patterns (getknit/knit, 132 stars), Styles (arindamxd/camerax-android, 132 stars) and Jetpack Compose Expert (aldefy/compose-skill, 596 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Android UI Journey Testing?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,379 GitHub stars. The repository holds 1,493 skills in this directory. The repository was last updated on October 9, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.