android

Coordinate Android NDK compilation, JNI bridge management, and automated device testing.

13|1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Generous-Corp/pulp --skill android-generous-corp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android
Source: https://github.com/Generous-Corp/pulp/tree/main/.agents/skills/android
Command: npx skills add https://github.com/Generous-Corp/pulp --skill android-generous-corp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires adb, emulator, cmake, ninja, and includes scripts (resource) components.

What problem does it solve?

This skill streamlines the complex Android development lifecycle for the Pulp framework, bridging the gap between C++ core development and Android platform-specific requirements like JNI, Vulkan rendering, and audio HAL integration.

Core Features & Use Cases

  • Platform Orchestration: Automates build, deploy, and smoke testing workflows for Android targets.
  • Diagnostic Tooling: Provides a unified interface for verifying SDK/NDK environments, emulator state, and device connectivity.
  • Use Case: When iterating on C++ audio engine changes, use this skill to perform a full cycle of cross-compilation, APK deployment, and automated smoke testing to ensure no regressions in audio or rendering occur on the Android target.

Quick Start

Run the android smoke test script to validate the current build against the connected emulator or device.

Frequently Asked Questions about android

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

FAQPage Schema
How do I automate cross-compilation and deployment for a C++ Android NDK project?

Automate C++ Android cross-compilation and deployment by coordinating NDK builds, APK packaging, and automated device testing. This workflow bridges C++ core development with Android platform requirements using CMake and Ninja for build orchestration.

Do I need ADB and a configured emulator to run automated Android build and smoke tests?

Yes, automated Android build and smoke tests require a configured Android SDK, NDK, and ADB environment. The diagnostic tooling verifies emulator state and device connectivity before executing platform-specific build and lifecycle validation tasks.

How does JNI bridge management work when integrating C++ audio engines with Android targets?

JNI bridge management for C++ audio engines on Android targets connects native code with the Android audio HAL. It facilitates cross-platform development workflows by validating JNI bindings during automated deployment and smoke testing cycles.

What's the best way to verify SDK and NDK environments before running Vulkan rendering tests on Android?

Verify SDK and NDK environments through a unified diagnostic interface that checks toolchain configuration, emulator state, and device connectivity. This ensures Vulkan rendering and audio HAL integrations are validated against properly connected Android targets.

Can I use CMake to build and validate C++ Vulkan rendering applications on Android emulators?

Yes, CMake coordinates cross-platform Android development workflows for C++ Vulkan rendering applications. The system uses CMake and Ninja to compile NDK targets, deploys APKs to emulators, and runs automated smoke tests for lifecycle validation.

Why does my Android NDK build fail when deploying C++ audio and rendering applications to a device?

Android NDK build failures during deployment of C++ audio and rendering applications often stem from unverified SDK, NDK, or ADB environments. The diagnostic tooling identifies emulator state and device connectivity issues before executing build workflows.