[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75XVT0ED04PQWJSHZBXSH7C":3,"skill-same:01M75XVT0ED04PQWJSHZBXSH7C":47},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M75XVT0ED04PQWJSHZBXSH7C","orca-emulator-android",null,"Control an Android emulator \u002F device from inside Orca using the `orca` CLI. Use for listing\u002Fbooting AVDs, taps, swipes, typing, hardware buttons (incl. Back and Recents), rotation, app install\u002Flaunch, runtime permissions, the accessibility tree, and logcat — driving a real adb-connected device or emulator. Cross-platform (Windows, Linux, macOS). Complements the orca-emulator (iOS) and orca-cli skills.","dalholm\u002Fagent-config","dalholm","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F426083?v=4","01M75XSWW6K9ZQVVBVH200SG1M","Mikael Dalholm","01M75XSWWXF3943MSDFYCW683Y",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdalholm\u002Fagent-config\u002Fblob\u002Fmain\u002Fdeprecated\u002Fskills\u002Forca-emulator-android\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: orca-emulator-android\ndescription: >\n  Control an Android emulator \u002F device from inside Orca using the `orca` CLI.\n  Use for listing\u002Fbooting AVDs, taps, swipes, typing, hardware buttons (incl. Back\n  and Recents), rotation, app install\u002Flaunch, runtime permissions, the accessibility\n  tree, and logcat — driving a real adb-connected device or emulator. Cross-platform\n  (Windows, Linux, macOS). Complements the orca-emulator (iOS) and orca-cli skills.\nlicense: Apache-2.0\n---\n\n# Orca Emulator (Android)\n\nThis file is a discovery stub, not the usage guide. The full, version-matched Orca Android\nemulator reference is served by the `orca` binary itself — kept out of this file on purpose\nso it can never drift from the binary that will actually run your commands.\n\nEngage Orca whenever you drive an adb-connected Android emulator or device from inside the\nOrca app: listing\u002Fbooting AVDs, taps, swipes, typing, hardware buttons (including Back and\nRecents), rotation, app install\u002Flaunch, runtime permissions, the accessibility tree, and\nlogcat. It is cross-platform (Windows, Linux, macOS) and complements the orca-emulator (iOS)\nand orca-cli skills.\n\n## Resolve the CLI for this session\n\nChoose the executable once and reuse it for every later command:\n\n- If the `ORCA_CLI_COMMAND` environment variable is set, use its value. Orca exports this\n  for managed WSL sessions.\n- Otherwise, in a dev checkout whose session exposes `ORCA_DEV_REPO_ROOT`, use `orca-dev`.\n- Otherwise, on Linux outside an Orca-managed terminal, use `orca-ide`. Never run bare\n  `orca` there — outside Orca's terminals it normally resolves to the\n  GNOME Orca screen reader (`\u002Fusr\u002Fbin\u002Forca`) and starts speech on the user's machine.\n- Otherwise, use `orca`.\n\nBelow, `ORCA` is a placeholder for the executable you resolved. Substitute it before\nrunning anything; do not create a shell variable or run `ORCA` literally. This works the\nsame way in POSIX shells, PowerShell, and cmd.exe.\n\nIf the selected executable cannot run, report its exact error and stop. Do not fall through\nto another executable, which could silently target a different Orca build.\n\n## Load the full guide before running Orca commands\n\n```text\nORCA skills get orca-emulator-android\n```\n\nThat prints the complete, version-matched guide for the exact binary that will handle your\nnext commands — booting AVDs, taps and swipes, typing, hardware buttons, app lifecycle,\npermissions, the accessibility tree, and logcat. Read it first, then run the specific\ncommand you need.\n\nDon't guess subcommands or flags from memory or from a cached copy of this stub. They\nchange between Orca releases, and this file deliberately no longer lists them. Confirm the\napp is up with `ORCA status --json` (start it with `ORCA open --json` if needed), and\nprefer `--json` for agent-driven calls.\n\n## If an older Orca does not recognize `skills get`\n\nUse this fallback only when the selected binary explicitly reports that `skills get` is an\nunknown command. Another failure is not proof of an older binary; report it rather than\nguessing or changing executables. For a confirmed pre-guide binary, use only this bounded,\nread-only bootstrap to orient. Do not dead-end and do not invent commands:\n\n```text\nORCA status --json\nORCA emulator devices --json\n```\n\nThen tell the user that updating Orca restores the full, version-matched guide via\n`ORCA skills get orca-emulator-android`. Beyond these commands, ask the user rather than\nguessing a command surface this older binary may not support.\n","# Orca Emulator (Android)\n\nThis file is a discovery stub, not the usage guide. The full, version-matched Orca Android\nemulator reference is served by the `orca` binary itself — kept out of this file on purpose\nso it can never drift from the binary that will actually run your commands.\n\nEngage Orca whenever you drive an adb-connected Android emulator or device from inside the\nOrca app: listing\u002Fbooting AVDs, taps, swipes, typing, hardware buttons (including Back and\nRecents), rotation, app install\u002Flaunch, runtime permissions, the accessibility tree, and\nlogcat. It is cross-platform (Windows, Linux, macOS) and complements the orca-emulator (iOS)\nand orca-cli skills.\n\n## Resolve the CLI for this session\n\nChoose the executable once and reuse it for every later command:\n\n- If the `ORCA_CLI_COMMAND` environment variable is set, use its value. Orca exports this\n  for managed WSL sessions.\n- Otherwise, in a dev checkout whose session exposes `ORCA_DEV_REPO_ROOT`, use `orca-dev`.\n- Otherwise, on Linux outside an Orca-managed terminal, use `orca-ide`. Never run bare\n  `orca` there — outside Orca's terminals it normally resolves to the\n  GNOME Orca screen reader (`\u002Fusr\u002Fbin\u002Forca`) and starts speech on the user's machine.\n- Otherwise, use `orca`.\n\nBelow, `ORCA` is a placeholder for the executable you resolved. Substitute it before\nrunning anything; do not create a shell variable or run `ORCA` literally. This works the\nsame way in POSIX shells, PowerShell, and cmd.exe.\n\nIf the selected executable cannot run, report its exact error and stop. Do not fall through\nto another executable, which could silently target a different Orca build.\n\n## Load the full guide before running Orca commands\n\n```text\nORCA skills get orca-emulator-android\n```\n\nThat prints the complete, version-matched guide for the exact binary that will handle your\nnext commands — booting AVDs, taps and swipes, typing, hardware buttons, app lifecycle,\npermissions, the accessibility tree, and logcat. Read it first, then run the specific\ncommand you need.\n\nDon't guess subcommands or flags from memory or from a cached copy of this stub. They\nchange between Orca releases, and this file deliberately no longer lists them. Confirm the\napp is up with `ORCA status --json` (start it with `ORCA open --json` if needed), and\nprefer `--json` for agent-driven calls.\n\n## If an older Orca does not recognize `skills get`\n\nUse this fallback only when the selected binary explicitly reports that `skills get` is an\nunknown command. Another failure is not proof of an older binary; report it rather than\nguessing or changing executables. For a confirmed pre-guide binary, use only this bounded,\nread-only bootstrap to orient. Do not dead-end and do not invent commands:\n\n```text\nORCA status --json\nORCA emulator devices --json\n```\n\nThen tell the user that updating Orca restores the full, version-matched guide via\n`ORCA skills get orca-emulator-android`. Beyond these commands, ask the user rather than\nguessing a command surface this older binary may not support.\n",{"name":5,"license":15,"description":24},"Control an Android emulator \u002F device from inside Orca using the `orca` CLI. Use for listing\u002Fbooting AVDs, taps, swipes, typing, hardware buttons (incl. Back and Recents), rotation, app install\u002Flaunch, runtime permissions, the accessibility tree, and logcat — driving a real adb-connected device or emulator. Cross-platform (Windows, Linux, macOS). Complements the orca-emulator (iOS) and orca-cli skills.\n","main","bd256ee77a3cf48a6958120332e210d1d93989f2","deprecated\u002Fskills\u002Forca-emulator-android","https:\u002F\u002Fgithub.com\u002Fdalholm\u002Fagent-config","https:\u002F\u002Fgithub.com\u002Fdalholm","https:\u002F\u002Fnyehandel.se","Programming is an eternal journey, you will never be fully educated. Keep being curious, it will do you good.","2026-09-05 19:32:52",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add dalholm\u002Fagent-config --skill orca-emulator-android",{"tool":39,"command":40},"bunx","bunx skills add dalholm\u002Fagent-config --skill orca-emulator-android",{"tool":42,"command":43},"pnpm","pnpm dlx skills add dalholm\u002Fagent-config --skill orca-emulator-android","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdalholm\u002Fagent-config\u002Fblob\u002Fmain\u002Fdeprecated\u002Fskills\u002Forca-emulator-android\u002FSKILL.md",true,[],[48],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M75XVXW6H05QXYVZN1C9HYF0","orca-emulator","Control a mobile (iOS) emulator \u002F simulator stream from inside Orca using the `orca` CLI. Use for taps, gestures, typing, hardware buttons, camera injection, permissions, accessibility tree, and more — all while seeing the live view in Orca's emulator pane. Prefer this over raw `npx serve-sim` or direct simctl when running agents inside Orca (the orca surface handles device scoping, helper lifecycle, and worktree context). Complements the orca-cli skill for terminals, worktrees, and the built-in browser.","https:\u002F\u002Fgithub.com\u002Fdalholm\u002Fagent-config\u002Fblob\u002Fmain\u002Fdeprecated\u002Fskills\u002Forca-emulator\u002FSKILL.md",[],[]]