engage-sdk-integration

Generates Play Engage SDK integration code for Android apps across content verticals.

3|Updated Aug 4, 2024
One-click install
npx skills add https://github.com/kabindra-shrestha/Clean-Architecture-Kotlin-Compose-Multiplatform --skill engage-sdk-integration-kabindra-shrestha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engage-sdk-integration
Source: https://github.com/kabindra-shrestha/Clean-Architecture-Kotlin-Compose-Multiplatform/tree/main/.agents/skills/play/engage-sdk-integration
Command: npx skills add https://github.com/kabindra-shrestha/Clean-Architecture-Kotlin-Compose-Multiplatform --skill engage-sdk-integration-kabindra-shrestha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Integrating the Google Play Engage SDK requires correctly wiring clients, entities, clusters, WorkManager publishing, and broadcast receivers for each content vertical, which is error-prone and poorly documented for first-time implementers. ## Core Features & Use Cases - Structured Code Generation: Produces the full Engage integration layer (Constants, ItemToEntityConverter, ClusterRequestFactory, EngageWorker, EngagePublisher, EngageBroadcastReceiver) following official patterns. - Vertical-Aware Schemas: Maps app data models to the correct Engage entities for Food, Watch, Listen, Read, Shopping, Social, Travel, Health & Fitness, and TV verticals. - Debugging & Verification: Resolves Gradle build errors, verifies manifest receiver declarations, and enforces both static and dynamic broadcast receiver registration. - Use Case: A food delivery app developer wants to publish shopping cart and reorder clusters to Google Play surfaces; the skill generates the converter, worker, and receiver code wired to AppEngageFoodClient. ## Quick Start Ask the assistant to integrate the Play Engage SDK for your app's vertical, providing your local data model so it can generate the entity mapping and publishing code.

Frequently Asked Questions about engage-sdk-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate the Play Engage SDK into my Android app?

Identify your app's vertical, then generate the Engage code layer: Constants, ItemToEntityConverter, ClusterRequestFactory, EngageWorker, EngagePublisher, and EngageBroadcastReceiver. Add the engage-core dependency and declare the receiver in AndroidManifest.xml.

How do I map my app's data model to Engage SDK entities?

Provide your local model schema, then match its fields to the vertical-specific Engage entity such as ProductEntity or MusicTrackEntity. Implement the conversion in an ItemToEntityConverter class using the entity Builder setters.

Does the Engage SDK support Android TV integrations?

Yes, TV integrations use the engage-tv library instead of engage-core and require the WRITE_EPG_DATA permission. TV supports recommendations, continue watching, and entitlements with platform-specific playback URIs.

Why is my EngageBroadcastReceiver not receiving publish intents?

Both static and dynamic registration are required. Declare the receiver with intent filters in AndroidManifest.xml and also call EngageBroadcastReceiver.register(context) from your Application or main Activity onCreate method.

Which Gradle dependency do I need for the Engage SDK?

For all mobile verticals, add com.google.android.engage:engage-core:1.5.12. TV apps use com.google.android.engage:engage-tv:1.0.6 instead. WorkManager and kotlinx-coroutines-play-services are also needed for publishing.