How to use the Play Engage SDK Integration agent skill

What the engage-sdk-integration skill makes the agent do

An agent skill is a folder of instructions and reference files that an AI agent loads when your request matches the skill's description. This one covers the Play Engage SDK. When it is active, the agent acts as a guide for adding the SDK to an Android app and for debugging existing Engage code.

The agent first asks which vertical your app belongs to and whether the integration is for mobile or TV. It then asks which cluster type you want to publish from the cluster types supported for that vertical. It asks you to share your local data model, such as a data class or JSON snippet, and maps it to the matching Engage entities.

From there, the skill generates a set of boilerplate classes: Constants, ItemToEntityConverter, ClusterRequestFactory, EngageWorker, a publisher class, and EngageBroadcastReceiver. It also walks through Gradle and AndroidManifest.xml changes and ends with a compile-and-verify checklist.

• Maps your data models to Engage entities and suggests the field values for each request.
• Generates a converter, request factory, WorkManager worker, publisher and broadcast receiver.
• Suggests build.gradle and AndroidManifest.xml updates, including the receiver and service declarations.
• Helps resolve import failures, namespace conflicts and compile errors.

Install the skill in Claude

You can install the skill in two ways. Download the ZIP file from the skill's page in this directory. Then choose one of the options below.

For a personal setup available across your projects, unzip the download into your user skills folder at ~/.claude/skills/. For a setup that only applies to one project, unzip it into the .claude/skills/ folder inside that project.

If you use the Claude apps, you can instead upload the ZIP under Settings → Capabilities → Skills.

• Personal: unzip into ~/.claude/skills/
• Project only: unzip into .claude/skills/ inside your project folder
• Claude apps: upload the ZIP under Settings → Capabilities → Skills

Check your project before you start

The skill expects an Android project that uses Gradle, with either build.gradle or build.gradle.kts. The generated code depends on the Google Play Engage SDK dependency and on WorkManager, which the generated worker uses. You need Android Studio or another Gradle toolchain so you can compile the result.

The skill's core dependency is shown below. The agent will suggest the exact lines for your build file, so check the version it proposes against the Engage documentation for your project.

• Android project using Gradle (build.gradle or build.gradle.kts)
• Google Play Engage SDK dependency (engage-core)
• WorkManager dependency for the generated worker
• Android Studio or a Gradle toolchain to compile

Trigger the skill with natural requests

You do not need a special command. Describe what you want in plain language that mentions Engage or the Play Engage SDK, and the agent will load the skill when the request matches its description. The skill's description mentions adding Engage SDK support, generating publishing code, mapping data classes to entities, and fixing SDK-related errors.

Good requests name your app type and your goal. The more detail you give, such as your data model and the content vertical, the fewer questions the agent needs to ask.

• Add Play Engage SDK publishing to my food delivery app.
• Map my Recipe data class to an Engage entity for the food vertical.
• Generate the EngageWorker and EngageBroadcastReceiver for my audio app.
• I get an import failure after adding engage-core. Help me fix it.
• Check my Engage integration against the verification checklist.

Work through a typical integration

Expect the agent to go step by step. It identifies the vertical and cluster, asks for your data model and your real data source, suggests the entity mapping, and then generates the code into a new directory named to match your codebase's conventions.

The skill also requires two registrations for the broadcast receiver. It must be declared statically in AndroidManifest.xml inside the application tag, and registered dynamically by calling EngageBroadcastReceiver.register(context) in your Application class or main Activity. Both are required for the integration to work.

Finally, the agent asks you to compile the project. The skill's rules call for the Gradle command below, with the --no-daemon flag on every compilation. Repeat until the build succeeds.

• Confirm the vertical, cluster type and client class.
• Provide your local model and data source.
• Review the generated mapping in ItemToEntityConverter.
• Check that image URIs match the vertical's aspect ratios, such as 16:9, 1:1 or 2:3.
• Make sure empty data lists are handled, for example by deleting the cluster instead of publishing empty data.

Safety notes: scripts, network and review

According to the skill's review, it runs no scripts and makes no network calls. Its instructions are text that guides the agent and the code it writes. You should still review every generated file yourself.

The generated code must be checked and compiled by you. The skill does not produce a finished, tested integration. Also note that the skill refers to schema, pattern and troubleshooting files that were not included in the files reviewed. Make sure those referenced files are present in your download before relying on the skill's full workflow.

• Runs scripts: no
• Uses network: no
• Review all generated classes, manifest entries and Gradle changes before shipping.
• Confirm the referenced files (schemas, patterns, troubleshooting) are in your copy of the skill.