Use for any question or task about Maestro, even writing one short flow, or a mobile UI test format that product managers and other non-engineers can read and edit: .maestro/*.yaml with tapOn, inputText, assertVisible and swipe, for iOS, Android, Flutter, React Native and web, with nested flows and JavaScript hooks.
95%
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 instructed CI setup step that runs `reactivecircus/android-emulator-runner@v2`, a remote GitHub Action with an individual-owned repository and no strong first-party provenance, so it is a common/reputable unofficial dependency and the highest tier is medium; the Maestro installer domain and `actions/checkout` are official and do not raise the tier.
reactivecircus/android-emulator-runner@v2
dependency · 1 site
The CI workflow instructs using reactivecircus/android-emulator-runner@v2, a third-party GitHub Action from an individual-owned repository without first-party provenance.
SKILL.md
168
- uses: reactivecircus/android-emulator-runner@v2