Help us improve
Share bugs, ideas, or general feedback.
From test-android-apps
Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.
npx claudepluginhub robinebers/converted-plugins --plugin test-android-appsHow this skill is triggered — by the user, by Claude, or both
Slash command
/test-android-apps:android-emulator-qaThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Validate Android app flows in an emulator using adb for launch, input, UI-tree inspection, screenshots, and logs.
Translates PRD intent, roadmap items, or product discussions into implementation-ready capability plans exposing constraints, invariants, interfaces, and unresolved decisions before multi-service work.
Share bugs, ideas, or general feedback.
Validate Android app flows in an emulator using adb for launch, input, UI-tree inspection, screenshots, and logs.
adb devices./gradlew :<module>:install<BuildVariant> --console=plain --quiet./gradlew tasks --all | rg installadb -s <serial> shell cmd package resolve-activity --brief <package>adb -s <serial> shell am start -n <package>/<activity>adb -s <serial> exec-out screencap -p > /tmp/emu.pngadb -s <serial> shell input tap <x> <y>adb -s <serial> shell input swipe <x1> <y1> <x2> <y2>adb -s <serial> shell input text "hello"adb -s <serial> shell input keyevent 4adb -s <serial> exec-out uiautomator dump /dev/ttyAlways compute tap coordinates from the UI tree, not screenshots.
adb -s <serial> exec-out uiautomator dump /dev/tty > /tmp/ui-settings.xmlx y) from bounds:
bounds="[x1,y1][x2,y2]"python3 <path-to-skill>/scripts/ui_pick.py /tmp/ui-settings.xml "Settings"scrollable elements:
adb -s <serial> shell input tap <x> <y>Use this helper to create a compact, readable overview before inspecting full XML.
adb -s <serial> exec-out uiautomator dump /dev/tty > /tmp/ui-full.xmlpython3 <path-to-skill>/scripts/ui_tree_summarize.py /tmp/ui-full.xml /tmp/ui-summary.txt/tmp/ui-summary.txt to choose likely targets, then compute exact bounds from full XML.adb -s <serial> logcat -cadb -s <serial> shell pidof -s <package>adb -s <serial> logcat --pid <pid>adb -s <serial> logcat -b crashadb -s <serial> logcat -d > /tmp/logcat.txtadb -s <serial> shell pm list packagesadb -s <serial> shell pm list packages | rg <company_or_app_id>adb -s <serial> shell cmd package resolve-activity --brief <package>