What problem does it solve? Integrating Google's Play Engage SDK requires correct entity mapping, cluster publishing, WorkManager scheduling, and dual broadcast receiver registration, and mistakes in any of these cause silent publishing failures or build errors. ## Core Features & Use Cases - Guided Integration Workflow: Walks through vertical selection (food, watch, read, shopping, travel, TV, and more), cluster type selection, and entity mapping from your app's local data models. - Boilerplate Code Generation: Produces the full set of required classes including Constants, ItemToEntityConverter, ClusterRequestFactory, EngageWorker, EngagePublisher, and EngageBroadcastReceiver with both static and dynamic registration. - Gradle and Manifest Setup: Supplies the correct engage-core or engage-tv dependencies and AndroidManifest receiver declarations, then helps debug build errors until the Gradle build succeeds. - Use Case: A food delivery app developer wants to publish recommendation and shopping cart clusters to Google Play surfaces; the skill generates the converter, worker, and receiver code mapped to their data models. ## Quick Start Ask the assistant to integrate the Play Engage SDK into your Android app for your content vertical and generate the publishing code.