Is native-android-test-visually safe to install?

SaferSkills independently audited native-android-test-visually (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/native-android-test-visually/SKILL.md · 1 file

skills/native-android-test-visually/SKILL.md3.0 KB · Markdown

name: native-android-test-visually

description: 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.

license: Apache-2.0

metadata:

author: Lukas Hinterleitner

version: "0.1.0"

platform: android

framework: native-android

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 installDebug task and how

to pick a build variant/flavor, launching the activity with am start / monkey, finding the applicationId, the "activity displayed" signal, and logcat scoped to the app's pid — read references/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.md or 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.

native-android-test-visually— agent skill

Is native-android-test-visually safe to install?

Native Android visual test

When to use

How it works

Bundled scripts

Audit the pieces. Scan the whole. Decide.