Native android test visually
Skill lukas-hinterleitner/visual-app-skills/skills/native-android-test-visually
Agent skills for visually testing mobile apps on Android — run a Flutter, React Native, or native Android app on an emulator/device, capture real screenshots via adb, read logs, optionally diff against a Figma design, and verify the UI rendered correctly. Works with Claude Code and other coding agents.
npx -y skills add lukas-hinterleitner/visual-app-skills --skill native-android-test-visuallyAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Build, install, and run a native Android app (Kotlin or Java, Jetpack Compose or Views, Gradle) on a connected device or emulator, capture real screenshots via adb, read logcat, and verify the visible UI and runtime behavior match what a recent code change intended. Use whenever the user asks to "test the app", "run it on the emulator", "see the visual changes", "verify a UI fix", "check if my change works/renders", or otherwise wants empirical on-device confirmation that a native Android change rendered correctly — even when they don't say "screenshot" or "logs". Handles the Gradle install task (and build variants/flavors), launching the activity, waiting for the first frame, navigating with adb input, capturing the screen, reading logcat scoped to the app, and reporting a concrete verdict with evidence. Optionally diffs against a Figma reference when one is provided.
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
3.0 KB, 486 tokens by cl100k_base, as published. Nobody here has run it
Native Android visual test
Interactive, on-device verification of a native Android app (Kotlin/Java,
Jetpack Compose or classic Views) — the "did my last change actually render
correctly" check. Installs the app via Gradle, launches the activity, captures
real screenshots via adb, reads logcat, and gives a concrete verdict.
When to use
- "Test the app / run it on the emulator / see the visual changes."
- "Did my Compose/layout fix work? Does this screen render correctly now?"
- "Compare this screen to the Figma design." (optional Figma add-on)
- Any request for empirical, on-device confirmation of a visual or runtime change — even without the words "screenshot" or "logs".
How it works
- Follow
references/capture-loop.md— the universal procedure: preflight, launch in the background, wait for the first real frame, screenshot, capture logs, analyze the PNG against the change, report a verdict. - For the native-Android specifics — the Gradle
installDebugtask and how to pick a build variant/flavor, launching the activity witham start/monkey, finding theapplicationId, the "activity displayed" signal, and logcat scoped to the app's pid — readreferences/native-android.md. - To navigate the UI before screenshotting, see
references/driving-the-ui.md. - When something looks off, see
references/troubleshooting.md. - (Optional) compare to a Figma design →
references/figma-comparison.md(requires the Figma MCP server; skip entirely if you don't use Figma). - App built with a cross-platform framework instead? See
references/other-frameworks.mdor use the matching skill.
Bundled scripts
scripts/check-devices.sh, launch.sh, snap.sh, capture-logs.sh,
stop.sh wrap the common adb/Gradle commands with device disambiguation.
capture-loop.md shows how they fit together. Note that a native Gradle install
does not launch the app — see the framework reference for the am start step.
What ships with it: 8 files
10.0 KB alongside SKILL.md
evals/
- evals.json1.6 KB
references/
- scripts20 B