Use for any question or task about Appium mobile UI tests, even a quick fix, including tests that break after an Appium upgrade and suites that pass on Android but fail on iOS: one suite for iOS and Android (native or React Native) with XCUITest, UiAutomator2 and Espresso drivers, capabilities, clients in JS, Python, Java, Ruby or .NET, simulators, emulators and device farms.
89%
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 reference-link URLs are static documentation, but the CI workflow runs the third-party GitHub Action `reactivecircus/android-emulator-runner@v2`, an individual-maintained repository pinned only to a mutable tag, so it is a common/reputable unofficial operational dependency (medium); the `actions/*` steps are official GitHub actions and do not count.
reactivecircus/android-emulator-runner@v2
dependency · 1 site
The CI workflow in SKILL.md uses the third-party GitHub Action reactivecircus/android-emulator-runner@v2, an individual-maintained repository pinned only to a mutable tag (v2), making it an unverifiable external dependency.
SKILL.md
248
uses: reactivecircus/android-emulator-runner@v2