engage-sdk-integration

Generate Android boilerplate code for Google Play Engage SDK integrations.

Updated Jul 6, 2026
One-click install
npx skills add https://github.com/shirulot/codex-skill --skill engage-sdk-integration-shirulot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engage-sdk-integration
Source: https://github.com/shirulot/codex-skill/tree/main/engage-sdk-integration
Command: npx skills add https://github.com/shirulot/codex-skill --skill engage-sdk-integration-shirulot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires androidx.work:work-runtime-ktx, org.jetbrains.kotlinx:kotlinx-coroutines-core, org.jetbrains.kotlinx:kotlinx-coroutines-play-services, and includes references (resource) components.

What problem does it solve?

This Skill simplifies the complex integration of the Google Play Engage SDK into Android applications, ensuring developers follow mandatory structural requirements and avoid common implementation pitfalls.

Core Features & Use Cases

  • Structured Boilerplate Generation: Automatically generates necessary classes like EngageWorker, ClusterRequestFactory, and ItemToEntityConverter based on project-specific schemas.
  • Vertical-Specific Guidance: Provides tailored integration paths for various verticals such as Food, Watch, Listen, and TV, including schema mapping and manifest configuration.
  • Debugging & Validation: Offers a systematic workflow for resolving Gradle sync errors, import issues, and runtime publishing failures.

Quick Start

Use the engage-sdk-integration skill to generate the boilerplate code for a new Food vertical integration in my Android project.

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 Google Play Engage SDK into my Android app?

Integrate the Google Play Engage SDK by generating necessary boilerplate classes like EngageWorker and ClusterRequestFactory, mapping project-specific schemas, and validating Android manifest configurations for static and dynamic broadcast receivers.

How do I set up WorkManager for Play Engage SDK content publishing?

Set up WorkManager for Play Engage SDK publishing by generating an EngageWorker class using work-runtime-ktx and kotlinx-coroutines. This Skill creates the boilerplate to satisfy WorkManager-based publishing requirements and handle background content tasks.

Does the Play Engage SDK support Food, Watch, and Listen verticals?

The Play Engage SDK supports Food, Watch, and Listen verticals through specific schema mappings. This Skill generates tailored integration paths and entity-to-model converters for each vertical, ensuring your content matches the required publishing schemas.

What is the best way to debug Google Play Engage SDK publishing failures?

Debug Play Engage SDK publishing failures by systematically resolving Gradle sync errors, import issues, and runtime exceptions. This Skill provides a validation workflow to check manifest configurations and entity-to-model mappings to identify common integration pitfalls.

Why does my Play Engage SDK broadcast receiver fail to register in the Android manifest?

Play Engage SDK broadcast receiver registration fails when static or dynamic manifest configurations are incomplete. This Skill validates your Android manifest setup against mandatory structural requirements and generates the correct receiver boilerplate.