engage-sdk-integration

Generate Play Engage SDK integration code with Gradle, manifest, and WorkManager wiring.

1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/premex-ab/claude-marketplace --skill engage-sdk-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engage-sdk-integration
Source: https://github.com/premex-ab/claude-marketplace/tree/main/plugins/android-engage-sdk-integration/skills/engage-sdk-integration
Command: npx skills add https://github.com/premex-ab/claude-marketplace --skill engage-sdk-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Integrating the Play Engage SDK into an Android app is error-prone because it requires strict entity/cluster structure, correct Gradle/manifest wiring, and careful broadcast + WorkManager publishing flow.

Core Features & Use Cases

  • Vertical & cluster-aligned integration: Guides you to select the correct vertical, entities, and client class, then map your local models to the required Engage entities and request payloads.
  • Boilerplate code generation patterns: Produces the recommended integration building blocks (Constants, converters, request factory, WorkManager worker/publisher, and a BroadcastReceiver).
  • Publishing flow correctness & debugging: Includes step-by-step Gradle/manifest updates and an explicit debugging/retry mindset, including recoverable vs non-recoverable publish errors.
  • Critical registration guidance: Stresses that both static <receiver> registration and dynamic EngageBroadcastReceiver.register(context) are required for reliable intent handling.

Quick Start

Use the engage-sdk-integration skill to generate the required Play Engage integration skeleton for your app, including WorkManager publishing and an EngageBroadcastReceiver that is both statically declared and dynamically registered in your Application.

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?

To integrate the Play Engage SDK, you map local models to required Engage entities using an ItemToEntityConverter, wire Gradle and the AndroidManifest, and orchestrate publishing via WorkManager and a BroadcastReceiver.

How do I generate Engage-compliant Android code for cluster publish requests?

You generate cluster publish requests by selecting your vertical, entities, and cluster from a local model schema, then using an EngageWorker and EngagePublisher to build the recommended integration boilerplate.

Why does my Play Engage BroadcastReceiver fail to handle publishing intents?

Play Engage BroadcastReceiver intent handling fails if you miss the critical registration guidance requiring both static <receiver> declaration in the manifest and dynamic EngageBroadcastReceiver.register(context) in your Application class.

How do I debug recoverable vs non-recoverable Play Engage publish errors?

Debug Play Engage publish errors by applying an explicit debugging and retry mindset to your WorkManager orchestration, differentiating between recoverable errors that warrant rescheduling and non-recoverable failures requiring code fixes.

Do I need WorkManager to publish entities with the Play Engage SDK?

Yes, WorkManager is required for Play Engage SDK publishing orchestration, utilizing an EngageWorker and EngagePublisher pattern to ensure background reliability for your cluster and entity publish requests.

What's the best way to map local data models to Play Engage entities?

The best way to map local data models to Play Engage entities is using the ItemToEntityConverter pattern, which safely translates your existing schema into the strict entity and cluster structures required by the SDK.