engage-sdk-integration

Integrates the Play Engage SDK into Android apps with generated boilerplate and verification.

2|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/IsKenKenYa/skills --skill engage-sdk-integration-iskenkenya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engage-sdk-integration
Source: https://github.com/IsKenKenYa/skills/tree/main/skills/android/play/engage-sdk-integration
Command: npx skills add https://github.com/IsKenKenYa/skills --skill engage-sdk-integration-iskenkenya

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Integrating Google's Play Engage SDK requires correctly wiring many moving parts—vertical-specific entities, cluster requests, WorkManager publishing, broadcast receivers, and manifest declarations—and small mistakes cause silent publishing failures or compile errors. This Skill walks an AI agent through the entire integration so the generated code follows the mandatory structure for each content vertical. ## Core Features & Use Cases - Guided vertical-aware integration: Identifies your app's vertical (food, watch, read, shopping, travel, TV, and more) and uses the matching entity schemas and client classes from bundled reference files. - Structured boilerplate generation: Creates Constants, ItemToEntityConverter, ClusterRequestFactory, EngageWorker, EngagePublisher, and EngageBroadcastReceiver classes with both static and dynamic receiver registration. - Entity mapping and data source wiring: Maps your app's local data models to Engage entities and connects real data sources to publish requests. - Debugging and verification: Enforces a self-verification checklist, runs Gradle compilation with sandbox-safe rules, and resolves common errors like namespace conflicts and missing imports via a troubleshooting guide. - Use Case: You are adding Google Play content recommendations to a recipe app. The Skill identifies the food vertical, generates the publishing worker and broadcast receiver, maps your Recipe model to RecipeEntity, updates Gradle and the manifest, and compiles until the build succeeds. ## Quick Start Ask the agent to integrate the Play Engage SDK into your Android app for your content vertical and let it generate and verify the 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 an Android app?

Identify your app's vertical, generate the Engage boilerplate classes (Constants, ItemToEntityConverter, ClusterRequestFactory, EngageWorker, EngagePublisher, EngageBroadcastReceiver), map your local models to Engage entities, then update build.gradle and AndroidManifest.xml. Compile with ./gradlew assembleDebug --no-daemon to verify.

How do I publish recommendation clusters with the Engage SDK?

Build a RecommendationCluster with a title and RecommendationClusterType, add converted entities, and call publishRecommendationClusters on your vertical's client class. Use WorkManager through an EngageWorker to handle publishing, retries, and status updates.

Does the Engage SDK support Android TV integrations?

Yes, TV integrations use the engage-tv library instead of engage-core and require TV-specific manifest permissions like WRITE_EPG_DATA. TV apps also use PlatformSpecificUri and must populate both contentRatings and legacy content rating fields.

Why does the Engage SDK build fail with a namespace conflict?

The conflict occurs because engage-core and engage-tv declare the same com.google.android.engage namespace. Remove the explicit engage-core dependency and keep only engage-tv, which transitively pulls in the compatible engage-core version.

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.

What image requirements does the Play Engage SDK enforce?

Play Engage enforces strict aspect ratios per vertical and entity type, such as 16:9 landscape, 1:1 square, or 2:3 portrait. Images not matching these ratios may be cropped or rejected, so verify URIs in your ItemToEntityConverter.