[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D4C77ZRJNKAMFJFJKKK3MN":3,"skill-same:01M7D4C77ZRJNKAMFJFJKKK3MN":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7D4C77ZRJNKAMFJFJKKK3MN","android-dev",null,"Build, run, inspect, and lightly automate Android apps with the android-emulator MCP tools.","zai-org\u002FZCode","zai-org","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F223098841?v=4","01M7D3Y10287Y0CNVHSNZ4GD03","Z.ai","01M7D3Y10SKN81G21P442YTCYP",8689,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fzai-org\u002FZCode\u002Fblob\u002Fmain\u002Fapps\u002Fzcode-cli\u002Fpackages\u002Fandroid-emulator-plugin\u002Fskills\u002Fandroid-dev\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: android-dev\ndescription: Build, run, inspect, and lightly automate Android apps with the android-emulator MCP tools.\n---\n\n# Android Dev\n\nUse this skill when the user wants you to create, modify, build, run, debug, screenshot, or inspect an Android app in the desktop Android Emulator or on a USB-connected Android device.\n\n## ZCode Tool Names\n\nThis skill assumes the MCP server is configured in zcode as `android_emulator`. In zcode, MCP tools are exposed to the model as `mcp__android_emulator__\u003Ctool>`.\n\nIf the server is configured with a different name, use the corresponding visible `mcp__\u003Cserver>__...` tool names from the active zcode tool list.\n\n## Default Workflow\n\n1. Call `mcp__android_emulator__android_preflight` first.\n\t   - If the required environment is not ready, follow `INSTALL_ENVIRONMENT.md` before continuing. Missing emulator-only checks do not block a selected ready USB device target.\n\t   - Environment setup is done with the fixed macOS shell or Windows PowerShell procedure in that file; do not improvise unrelated install commands.\n\t   - Do not accept Android SDK licenses, enter passwords, wipe emulator data, or delete AVDs on the user's behalf. Stop and ask the user for those cases.\n2. Discover the project with `mcp__android_emulator__android_discover_project`.\n   - If no Android project exists and the user wants a new app, call `mcp__android_emulator__android_create_app`.\n   - Prefer editing Kotlin\u002FCompose files directly after project creation.\n   - `mcp__android_emulator__android_create_app` refuses to overwrite generated files by default; only pass `overwrite: true` after explicit user confirmation.\n   - Read `warnings` in the discovery result before building and repair missing `gradle.properties`, `local.properties`, or Gradle wrapper issues.\n3. Build and launch with `mcp__android_emulator__android_build_and_run`.\n   - Pass `module`, `variant`, or `applicationId` when discovery is ambiguous.\n   - Use a selected `serial` when the user wants a specific USB device or emulator. Use `mcp__android_emulator__android_start_emulator` only when a new GUI emulator is needed, then pass its returned `serial` to follow-up tools.\n   - Read the returned `output` first for compile errors; use the returned log path only when more detail is needed.\n4. Verify the app visually with `mcp__android_emulator__android_screenshot`.\n5. For runtime checks, use `mcp__android_emulator__android_open_url`, `mcp__android_emulator__android_launch_app`, `mcp__android_emulator__android_terminate_app`, and `mcp__android_emulator__android_logs`.\n6. For UI automation, call `mcp__android_emulator__android_ui_status` first.\n   - Prefer `mcp__android_emulator__android_ui_describe` or `mcp__android_emulator__android_ui_resolve` before tapping coordinates.\n   - `mcp__android_emulator__android_ui_tap`, `mcp__android_emulator__android_ui_swipe`, `mcp__android_emulator__android_ui_type_text`, and `mcp__android_emulator__android_ui_keyevent` use ADB\u002FUI Automator based backends.\n   - If UI automation is unavailable, continue with build\u002Frun\u002Fscreenshot checks and say UI automation is unavailable.\n\n## Tool Notes\n\n- This MVP intentionally uses Android Emulator's own desktop window for rendering. Do not create or expect a custom emulator window.\n- `mcp__android_emulator__android_preflight` is a pure diagnostic check. Use `INSTALL_ENVIRONMENT.md` for guided environment setup when it reports missing dependencies.\n- The target MCP tools accept `serial` for a specific USB device or emulator and `avd` for the fallback emulator to start only when no target is ready. `mcp__android_emulator__android_start_emulator` starts a new GUI emulator and does not reuse existing targets.\n- Keep emulator interactions through MCP tools instead of raw `adb`\u002F`emulator` commands unless a tool does not cover the operation.\n- `mcp__android_emulator__android_create_app` generates a minimal Kotlin + Jetpack Compose app suitable for model-driven iteration.\n- `mcp__android_emulator__android_build_app` only builds. `mcp__android_emulator__android_build_and_run` builds, reuses the selected Android target by serial or starts a GUI emulator when needed, installs, and launches the app.\n- Android SDK path, default AVD, API level, build-tools version, system image variant\u002FABI, and JDK major version come from plugin user config and are exposed to the MCP server as `ANDROID_PLUGIN_*` environment variables.\n\n## Project Requirements\n\nWhen creating or repairing a project manually, make sure these files exist before building:\n\n- `settings.gradle` or `settings.gradle.kts`\n- root `build.gradle` or `build.gradle.kts`\n- `app\u002Fbuild.gradle` or `app\u002Fbuild.gradle.kts`\n- `gradle.properties` with `android.useAndroidX=true`\n- `local.properties` with `sdk.dir=\u003CAndroid SDK path>` when the SDK is not otherwise discoverable\n- a Gradle wrapper (`gradlew` \u002F `gradlew.bat`) or `gradle` available on `PATH`\n\n## Build Troubleshooting\n\n- If Gradle reports `android.useAndroidX property is not enabled`, create or update `gradle.properties` with `android.useAndroidX=true`.\n- If `android_preflight` reports `Gradle` as `not found`, follow the quick Gradle fix in `INSTALL_ENVIRONMENT.md`; do not reinstall the Android SDK when Gradle is the only missing check.\n- If `android_preflight` reports no AVDs but a USB device is ready, continue by passing that device `serial` to target tools.\n- If Gradle cannot find the Android SDK, create `local.properties` in the Android Gradle root with `sdk.dir=\u003CAndroid SDK path>`.\n- If `.\u002Fgradlew` or `gradlew.bat` is missing, install Gradle and run `gradle wrapper --gradle-version 8.9`, or let `android_build_app` attempt wrapper generation when `gradle` is available.\n- If `sdkmanager` or `avdmanager` cannot find Java after installing Homebrew `openjdk@\u003Cconfigured JDK major>`, export the matching `JAVA_HOME` from `INSTALL_ENVIRONMENT.md` and retry. Use the optional symlink step only after user confirmation.\n- On Windows, if SDK package installation fails because Android SDK licenses are not accepted, ask the user for explicit approval before running `sdkmanager.bat --licenses`, then retry the same package installation command.\n- On Windows, if emulator acceleration is unavailable, ask the user to enable virtualization\u002FWHPX or finish Android Emulator driver setup in Android Studio Device Manager, then rerun `android_preflight`.\n- If system image downloads time out, prefer the `default` image first and retry the exact `sdkmanager --install` command with a longer timeout before switching to larger `google_apis` images.\n\n## Extension Point\n\nThe Android backend is deliberately isolated. P0 uses Android SDK tools, ADB\u002FUI Automator, and Gradle. Future backends can map the same public operations to Android Studio semantic tools, a UI Automator helper APK, Appium\u002Fuiautomator2, or another automation bridge without changing the skill workflow.\n","# Android Dev\n\nUse this skill when the user wants you to create, modify, build, run, debug, screenshot, or inspect an Android app in the desktop Android Emulator or on a USB-connected Android device.\n\n## ZCode Tool Names\n\nThis skill assumes the MCP server is configured in zcode as `android_emulator`. In zcode, MCP tools are exposed to the model as `mcp__android_emulator__\u003Ctool>`.\n\nIf the server is configured with a different name, use the corresponding visible `mcp__\u003Cserver>__...` tool names from the active zcode tool list.\n\n## Default Workflow\n\n1. Call `mcp__android_emulator__android_preflight` first.\n\t   - If the required environment is not ready, follow `INSTALL_ENVIRONMENT.md` before continuing. Missing emulator-only checks do not block a selected ready USB device target.\n\t   - Environment setup is done with the fixed macOS shell or Windows PowerShell procedure in that file; do not improvise unrelated install commands.\n\t   - Do not accept Android SDK licenses, enter passwords, wipe emulator data, or delete AVDs on the user's behalf. Stop and ask the user for those cases.\n2. Discover the project with `mcp__android_emulator__android_discover_project`.\n   - If no Android project exists and the user wants a new app, call `mcp__android_emulator__android_create_app`.\n   - Prefer editing Kotlin\u002FCompose files directly after project creation.\n   - `mcp__android_emulator__android_create_app` refuses to overwrite generated files by default; only pass `overwrite: true` after explicit user confirmation.\n   - Read `warnings` in the discovery result before building and repair missing `gradle.properties`, `local.properties`, or Gradle wrapper issues.\n3. Build and launch with `mcp__android_emulator__android_build_and_run`.\n   - Pass `module`, `variant`, or `applicationId` when discovery is ambiguous.\n   - Use a selected `serial` when the user wants a specific USB device or emulator. Use `mcp__android_emulator__android_start_emulator` only when a new GUI emulator is needed, then pass its returned `serial` to follow-up tools.\n   - Read the returned `output` first for compile errors; use the returned log path only when more detail is needed.\n4. Verify the app visually with `mcp__android_emulator__android_screenshot`.\n5. For runtime checks, use `mcp__android_emulator__android_open_url`, `mcp__android_emulator__android_launch_app`, `mcp__android_emulator__android_terminate_app`, and `mcp__android_emulator__android_logs`.\n6. For UI automation, call `mcp__android_emulator__android_ui_status` first.\n   - Prefer `mcp__android_emulator__android_ui_describe` or `mcp__android_emulator__android_ui_resolve` before tapping coordinates.\n   - `mcp__android_emulator__android_ui_tap`, `mcp__android_emulator__android_ui_swipe`, `mcp__android_emulator__android_ui_type_text`, and `mcp__android_emulator__android_ui_keyevent` use ADB\u002FUI Automator based backends.\n   - If UI automation is unavailable, continue with build\u002Frun\u002Fscreenshot checks and say UI automation is unavailable.\n\n## Tool Notes\n\n- This MVP intentionally uses Android Emulator's own desktop window for rendering. Do not create or expect a custom emulator window.\n- `mcp__android_emulator__android_preflight` is a pure diagnostic check. Use `INSTALL_ENVIRONMENT.md` for guided environment setup when it reports missing dependencies.\n- The target MCP tools accept `serial` for a specific USB device or emulator and `avd` for the fallback emulator to start only when no target is ready. `mcp__android_emulator__android_start_emulator` starts a new GUI emulator and does not reuse existing targets.\n- Keep emulator interactions through MCP tools instead of raw `adb`\u002F`emulator` commands unless a tool does not cover the operation.\n- `mcp__android_emulator__android_create_app` generates a minimal Kotlin + Jetpack Compose app suitable for model-driven iteration.\n- `mcp__android_emulator__android_build_app` only builds. `mcp__android_emulator__android_build_and_run` builds, reuses the selected Android target by serial or starts a GUI emulator when needed, installs, and launches the app.\n- Android SDK path, default AVD, API level, build-tools version, system image variant\u002FABI, and JDK major version come from plugin user config and are exposed to the MCP server as `ANDROID_PLUGIN_*` environment variables.\n\n## Project Requirements\n\nWhen creating or repairing a project manually, make sure these files exist before building:\n\n- `settings.gradle` or `settings.gradle.kts`\n- root `build.gradle` or `build.gradle.kts`\n- `app\u002Fbuild.gradle` or `app\u002Fbuild.gradle.kts`\n- `gradle.properties` with `android.useAndroidX=true`\n- `local.properties` with `sdk.dir=\u003CAndroid SDK path>` when the SDK is not otherwise discoverable\n- a Gradle wrapper (`gradlew` \u002F `gradlew.bat`) or `gradle` available on `PATH`\n\n## Build Troubleshooting\n\n- If Gradle reports `android.useAndroidX property is not enabled`, create or update `gradle.properties` with `android.useAndroidX=true`.\n- If `android_preflight` reports `Gradle` as `not found`, follow the quick Gradle fix in `INSTALL_ENVIRONMENT.md`; do not reinstall the Android SDK when Gradle is the only missing check.\n- If `android_preflight` reports no AVDs but a USB device is ready, continue by passing that device `serial` to target tools.\n- If Gradle cannot find the Android SDK, create `local.properties` in the Android Gradle root with `sdk.dir=\u003CAndroid SDK path>`.\n- If `.\u002Fgradlew` or `gradlew.bat` is missing, install Gradle and run `gradle wrapper --gradle-version 8.9`, or let `android_build_app` attempt wrapper generation when `gradle` is available.\n- If `sdkmanager` or `avdmanager` cannot find Java after installing Homebrew `openjdk@\u003Cconfigured JDK major>`, export the matching `JAVA_HOME` from `INSTALL_ENVIRONMENT.md` and retry. Use the optional symlink step only after user confirmation.\n- On Windows, if SDK package installation fails because Android SDK licenses are not accepted, ask the user for explicit approval before running `sdkmanager.bat --licenses`, then retry the same package installation command.\n- On Windows, if emulator acceleration is unavailable, ask the user to enable virtualization\u002FWHPX or finish Android Emulator driver setup in Android Studio Device Manager, then rerun `android_preflight`.\n- If system image downloads time out, prefer the `default` image first and retry the exact `sdkmanager --install` command with a longer timeout before switching to larger `google_apis` images.\n\n## Extension Point\n\nThe Android backend is deliberately isolated. P0 uses Android SDK tools, ADB\u002FUI Automator, and Gradle. Future backends can map the same public operations to Android Studio semantic tools, a UI Automator helper APK, Appium\u002Fuiautomator2, or another automation bridge without changing the skill workflow.\n",{"name":5,"description":7},"main","fec975905a2abd4c07e35c40d51fa097a2258ec9","apps\u002Fzcode-cli\u002Fpackages\u002Fandroid-emulator-plugin\u002Fskills\u002Fandroid-dev",2710,"https:\u002F\u002Fgithub.com\u002Fzai-org\u002FZCode","https:\u002F\u002Fzcode.z.ai\u002F","https:\u002F\u002Fgithub.com\u002Fzai-org","https:\u002F\u002Fwww.zhipuai.cn\u002Fen","ChatGLM, GLM-4.5, CogVLM, CodeGeeX, CogView, CogVideoX | CogDL, AMiner | Zhipu.ai (Z.ai)","2026-11-13 16:21:40",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add zai-org\u002FZCode --skill android-dev",{"tool":40,"command":41},"bunx","bunx skills add zai-org\u002FZCode --skill android-dev",{"tool":43,"command":44},"pnpm","pnpm dlx skills add zai-org\u002FZCode --skill android-dev","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzai-org\u002FZCode\u002Fblob\u002Fmain\u002Fapps\u002Fzcode-cli\u002Fpackages\u002Fandroid-emulator-plugin\u002Fskills\u002Fandroid-dev\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"INSTALL_ENVIRONMENT.md","REFERENCE","参考文档",13302,"https:\u002F\u002Fgithub.com\u002Fzai-org\u002FZCode\u002Fblob\u002Fmain\u002Fapps\u002Fzcode-cli\u002Fpackages\u002Fandroid-emulator-plugin\u002Fskills\u002Fandroid-dev\u002FINSTALL_ENVIRONMENT.md",[55,62,69,76,83,90],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7D57RTFKZH4SFFWF6NXSQ62","plugin-mcp-ping","E2E workspace Plugin skill marker","https:\u002F\u002Fgithub.com\u002Fzai-org\u002FZCode\u002Fblob\u002Fmain\u002Fpackages\u002Fdesktop\u002Ftest\u002Fe2e\u002Ffixtures\u002Fplugin-mcp-skill\u002Fe2e-plugin-mcp-ping\u002Fskills\u002Fplugin-mcp-ping\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7D57NRW93T0ETX2QPQY3JCP","e2e-ext-compat-plain","PLM-EXT-STORE fixture skill for e2e-ext-compat-plain.","https:\u002F\u002Fgithub.com\u002Fzai-org\u002FZCode\u002Fblob\u002Fmain\u002Fpackages\u002Fdesktop\u002Ftest\u002Fe2e\u002Ffixtures\u002Ffs\u002Fplugins\u002Fplugin-store-extension-compat\u002Fstore-market\u002Fplugins\u002Fe2e-ext-compat-plain\u002Fskills\u002Fe2e-ext-compat-plain\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7D57JYKJK5A4VW7Y5MYEA7R","e2e-ext-compat-ok","PLM-EXT-STORE fixture skill for e2e-ext-compat-ok.","https:\u002F\u002Fgithub.com\u002Fzai-org\u002FZCode\u002Fblob\u002Fmain\u002Fpackages\u002Fdesktop\u002Ftest\u002Fe2e\u002Ffixtures\u002Ffs\u002Fplugins\u002Fplugin-store-extension-compat\u002Fstore-market\u002Fplugins\u002Fe2e-ext-compat-ok\u002Fskills\u002Fe2e-ext-compat-ok\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7D57FZQKN28QJJ0HVG93ACN","e2e-ext-compat-installed","PLM-EXT-STORE fixture skill for e2e-ext-compat-installed.","https:\u002F\u002Fgithub.com\u002Fzai-org\u002FZCode\u002Fblob\u002Fmain\u002Fpackages\u002Fdesktop\u002Ftest\u002Fe2e\u002Ffixtures\u002Ffs\u002Fplugins\u002Fplugin-store-extension-compat\u002Fstore-market\u002Fplugins\u002Fe2e-ext-compat-installed\u002Fskills\u002Fe2e-ext-compat-installed\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7D57C9W30WJ3NJDAYX2MN0J","e2e-ext-compat-future","PLM-EXT-STORE fixture skill for e2e-ext-compat-future.","https:\u002F\u002Fgithub.com\u002Fzai-org\u002FZCode\u002Fblob\u002Fmain\u002Fpackages\u002Fdesktop\u002Ftest\u002Fe2e\u002Ffixtures\u002Ffs\u002Fplugins\u002Fplugin-store-extension-compat\u002Fstore-market\u002Fplugins\u002Fe2e-ext-compat-future\u002Fskills\u002Fe2e-ext-compat-future\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7D579KKRR6D2GPVW4J4QWVT","e2e-store-skill-b","E2E store fixture skill b","https:\u002F\u002Fgithub.com\u002Fzai-org\u002FZCode\u002Fblob\u002Fmain\u002Fpackages\u002Fdesktop\u002Ftest\u002Fe2e\u002Ffixtures\u002Ffs\u002Fplugins\u002Fplugin-extension-reads\u002Fstore-market\u002Fplugins\u002Fe2e-ext-store-b\u002Fskills\u002Fe2e-store-skill-b\u002FSKILL.md",[],[]]