Update to Ansight

{
  "name": "ansight-install-android",
  "description": "Install the native Android Ansight SDK with automatic emulator registration and one-shot CLI QR enrollment for physical devices. Add the aggregate dependency, initialize from Application, expose the SDK scanner from a developer-only surface, keep remote tools development-only, verify the Gradle build, and inspect the app through the Ansight CLI.",
  "included_files": [],
  "skill_md_contents": "---\nname: ansight-install-android\ndescription: Install the native Android Ansight SDK with automatic emulator registration and one-shot CLI QR enrollment for physical devices. Add the aggregate dependency, initialize from Application, expose the SDK scanner from a developer-only surface, keep remote tools development-only, verify the Gradle build, and inspect the app through the Ansight CLI.\n---\n\n## OpenAI plugin integration\n\nRun Ansight CLI commands using the execution tools in ChatGPT Work or Codex on the machine that owns the resident host. If this environment cannot execute commands or reach that host, explain the missing prerequisite and do not claim a live inspection succeeded. A remote workspace or cloud agent does not automatically have access to the developer’s local host. Resolve relative helper paths from this skill’s directory. When this workflow references another bundled skill, read its local SKILL.md completely before following it.\n\nUse these bundled files for the canonical skill URLs referenced below; keep public URLs when writing documentation for the user’s app:\n\n- https://www.ansight.ai/skills/agents/ansight-app-inspection.md → [ansight-app-inspection](../ansight-app-inspection/SKILL.md)\n- https://www.ansight.ai/skills/android/ansight-app-inspection-android.md → [ansight-app-inspection-android](../ansight-app-inspection-android/SKILL.md)\n\n\n# Ansight Android Install Skill\n\nUse this skill for native Android Kotlin or Java apps.\n\n## Outcome\n\nThe finished app must:\n\n- include `ai.ansight:ansight-android` in a local-development build;\n- initialize Ansight once from `Application.onCreate()`;\n- register automatically on an emulator and expose\n  `Ansight.enrollFromQrCode(activity)` from a developer-only UI for physical devices;\n- reconnect automatically after the first successful scan;\n- keep broad or mutating remote tools out of distributable builds; and\n- require no generated JSON, build secret, certificate, or manual app registration.\n\n## Workflow\n\n1. Identify the app module, `Application` class, debug variant, and existing developer menu.\n2. Add the aggregate dependency, normally:\n\n```kotlin\ndependencies {\n    debugImplementation(\"ai.ansight:ansight-android:1.4.0-preview.1\")\n}\n```\n\n3. Initialize from `Application.onCreate()`:\n\n```kotlin\nclass MyApplication : Application() {\n    override fun onCreate() {\n        super.onCreate()\n        if (BuildConfig.DEBUG) {\n            Ansight.initializeAndActivateDeveloperMode(\n                application = this,\n                clientName = \"Android App\",\n            )\n        }\n    }\n}\n```\n\n4. Add a developer-only action that owns an `Activity`:\n\n```kotlin\nAnsight.enrollFromQrCode(activity)\n```\n\n5. Do not add a camera permission. The SDK uses Google Code Scanner. The\n   aggregate SDK merges ordinary network access and clear-text development\n   traffic into the manifest.\n6. Keep reflection, secure-storage access, writes, and deletes disabled unless\n   the requested development workflow requires them.\n7. Create or update `ansight-readme.md` with the scanner location, build\n   verification command, and CLI enrollment commands. Do not add an enrollment\n   payload or token to it.\n8. Run `./gradlew :app:assembleDebug` and relevant tests.\n9. Start or reuse the resident CLI host. An emulator registers automatically.\n   For a physical device, issue one generic host QR and scan it from the\n   developer-only surface:\n\n```sh\nansight host run\nansight pairing issue --qr\nansight session list --connected --app-id <app-id> --json\nansight app tools <session-id> --detail summary --include-unavailable --max-results 50 --json\n```\n\n   Do not require `ansight app register` before the first connection. After the\n   SDK supplies its real App ID, optionally link the discovered app to the\n   repository with `ansight app register <app-id> --codebase <repository-path>`.\n\n## Enrollment Behavior\n\nAn emulator registers automatically through loopback. For a physical device,\nthe developer runs `ansight pairing issue --qr` against the resident host and\nscans the terminal QR once. The first connection registers the app installation and stores a random\ninstallation id and enrollment state in app-private preferences. Later\ndeveloper launches reconnect automatically while the registration remains\nactive.\n\nIf the app already owns a scanner, pass its result through the SDK payload-text\nconnection API instead of adding a second scanner.\n\n## Recommended Inspection Skills\n\nUse the main router to select the core inspection workflow. Add the native\nAndroid companion only when Android platform semantics are material:\n\n```text\nhttps://www.ansight.ai/skills/agents/ansight-app-inspection.md\nhttps://www.ansight.ai/skills/android/ansight-app-inspection-android.md\n```\n"
}