Update to Ansight

{
  "name": "ansight-install-flutter",
  "description": "Install ansight_flutter with automatic simulator or emulator registration and one-shot CLI QR enrollment for physical devices. Add the package, initialize the runtime and instrumentation, expose enrollFromQrCode from a developer-only surface, configure required native privacy declarations, verify Flutter and native builds, and inspect the app through the Ansight CLI.",
  "included_files": [],
  "skill_md_contents": "---\nname: ansight-install-flutter\ndescription: Install ansight_flutter with automatic simulator or emulator registration and one-shot CLI QR enrollment for physical devices. Add the package, initialize the runtime and instrumentation, expose enrollFromQrCode from a developer-only surface, configure required native privacy declarations, verify Flutter and native builds, 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/flutter/ansight-app-inspection-flutter.md → [ansight-app-inspection-flutter](../ansight-app-inspection-flutter/SKILL.md)\n\n\n# Ansight Flutter Install Skill\n\nUse this skill for Flutter apps with Android and/or iOS targets.\n\n## Workflow\n\n1. Inspect `pubspec.yaml`, `main.dart`, target platforms, debug guard, and\n   existing developer menu.\n2. Add `ansight_flutter: 1.4.0-preview.1` and run `flutter pub get`.\n3. Initialize after `WidgetsFlutterBinding.ensureInitialized()` and before\n   `runApp(...)`:\n\n```dart\nif (kDebugMode) {\n  await Ansight.instance.initializeAndActivate(AnsightOptions.developer());\n  await AnsightFlutterInstrumentation.instance.install();\n}\n```\n\n4. Add a developer-only scanner action:\n\n```dart\nawait Ansight.instance.enrollFromQrCode(\n  clientName: 'My Flutter App',\n);\n```\n\n5. `scanPairingQrCode(...)` is an API alias. Use the payload connection API\n   when the app already owns a scanner.\n6. Keep widget and native tools behind `kDebugMode` or an equivalent explicit\n   developer variant. Prefer read-only access.\n7. Android requires no app camera permission for the SDK scanner. On iOS, add\n   `NSCameraUsageDescription` and `NSLocalNetworkUsageDescription`. Add no ATS\n   exception or unrelated permissions.\n8. Create or update `ansight-readme.md` with the scanner location, tool profile,\n   build checks, and CLI enrollment commands. Do not include an enrollment payload.\n9. Run `flutter analyze`, `flutter test`, and practical target builds.\n10. Start or reuse the resident CLI host. A simulator or emulator registers\n    automatically. For a physical device, issue one generic host QR and scan it\n    from the 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\n    the 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\nSimulator and emulator builds register automatically through native loopback.\nThe first physical-device scan registers the native app installation. Its random installation\nid and enrollment state remain in app-private storage, so later developer\nlaunches reconnect automatically.\n\n## Recommended Inspection Skills\n\nUse the main router to select the core inspection workflow. Add the Flutter\ncompanion only when widget or native-platform semantics are material:\n\n```text\nhttps://www.ansight.ai/skills/agents/ansight-app-inspection.md\nhttps://www.ansight.ai/skills/flutter/ansight-app-inspection-flutter.md\n```\n"
}