Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fzyzcjy/frb-android-emulator-prepare
Use when preparing, installing, diagnosing, or explaining the host Android Emulator environment for flutter_rust_bridge local runtime validation, including Android SDK command-line tools, emulator packages, AVD creation, host emulator startup, and Docker-local ADB connectivity to the emulator TCP endpoint.
Passed 19 of 22 test cases with the skill, and 10 of 22 without it.
and 11 more in the full report
9 fixed10 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
What command should be used to launch the prepared FRB_API_35 AVD on host console port 5554 using the repository's environment script?
| Checked | Without skill | With skill |
|---|---|---|
| Invokes frb_dev_env.py script with android emulator subcommand. | Missed | Passed |
| Sets the port argument to 5554. | Passed | Passed |
The instructions your model reads when the skill loads.
Use this skill when a task requires a host Android Emulator for FRB local runtime validation.
FRB Android runtime validation currently supports a host Android Emulator path: host needs Java, Android SDK command-line tools, emulator, a system image, and an AVD; Docker runs FRB/Flutter commands through a Docker-local ADB server connected to the emulator TCP endpoint.
Do not install Android Emulator packages unless the user has explicitly asked to prepare or run an emulator. Installing the emulator changes host state and downloads large SDK packages.
Use standard Android Studio locations on macOS:
~/Library/Android/sdk
~/.android/avd
~/.android
Respect ANDROID_HOME if it is already set. Otherwise use ~/Library/Android/sdk. Do not invent repo-specific defaults such as /workspace, /tmp, or a user's personal artifacts directory.
Official references for this workflow:
sdkmanager command-line package manager: https://developer.android.com/tools/sdkmanageravdmanager command-line AVD manager: https://developer.android.com/tools/avdmanagerRun these before installing anything:
sw_vers
uname -m
which adb || true
adb version || true
echo "${ANDROID_HOME:-}"
test cases passed, vs 10 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.