Use whenever an Android app needs UI tests in Google's Espresso: onView with perform and check, automatic synchronization instead of sleeps, IdlingResource for app async work, ./gradlew connectedAndroidTest and JUnit XML results.
90%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
The decisive boundary is the CI workflow in Step 7, which instructs the user to add `reactivecircus/android-emulator-runner@v2`, a third-party GitHub Action that is fetched and executed during the pipeline; it is community-maintained, not first-party, and uses a mutable tag, so it is common/reputable unofficial (medium), while `actions/checkout` is GitHub-official and the developer.android.com links are documentation only.
reactivecircus/android-emulator-runner@v2
dependency · 1 site
The plugin's CI workflow (Step 7) instructs users to use the third-party GitHub Action `reactivecircus/android-emulator-runner@v2`, which is fetched and executed at runtime during the pipeline.
SKILL.md
260
- uses: reactivecircus/android-emulator-runner@v2