Agent skill · dynatrace
dt-setup-android
Instruments an existing Android project (Kotlin or Java) with the Dynatrace Mobile Agent for basic monitoring. Covers zero-to-first-event setup only: Gradle plugin, agent config, and user privacy opt-in. Do not use for advanced Dynatrace configuration beyond initial instrumentation.
What it needs
About 7k tokens when loaded.
What this skill does
Android Dynatrace Instrumentation Scope: Basic setup only — from zero to first event. For anything beyond initial instrumentation (custom actions, crash grouping, data privacy policies, etc.) refer to the Dynatrace documentation directly. Phase 1: Preflight Before doing anything else, check that the current directory is an Android project root by looking for settings.gradle.kts or settings.gradle. If neither exists, stop and tell the user this is not an Android project root, and ask them to navigate to the correct directory. Then verify the following minimum requirements. If any are not met, stop and inform the user of what needs to be upgraded before proceeding: Requirement Minimum --------------------------- ------- Gradle 7.0.2 Android Gradle Plugin (AGP) 7.0 JVM Java 11 Run ./gradlew --version (or gradlew.bat --version on Windows). The output covers both Gradle and the actual JVM Gradle is using (the Daemon JVM line), which may differ from the system Java when the project is opened in Android Studio or IntelliJ. Do not use java -version — it may report a different JDK than what the build actually runs on. The AGP version is declared in the root build file. Phase 2: Detect existing setup If a dynatrace { } block or a configure<com.dynatrace.tools.android.dsl.DynatraceExtension> { } block (also written as configure<DynatraceExtension> { } when the class is imported) is found anywhere in the build files, read it and extract if present: applicationId (the value passed to applicationId(...) or applicationId '...') beaconUrl (the value passed to beaconUrl(...) or beaconUrl '...') Save these as pre-filled values to carry into Phase 3. If either value is absent or uses a placeholder (e.g. YOURAPPLICATIONID), treat it as not found. Proceed to Phase 3. Phase 3: Collect inputs First, ask only for: 1. applicationId — Dynatrace application ID. Tell the user this can be found in their Dynatrace tenant, inside the mobile application they have already created. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills dynatrace/dt-setup-android