/google-mobile-ads-android-migrate-to-next-gen
Migrates Android applications from the old, legacy Google Mobile
$ npx -y skills add google/skills --skill google-mobile-ads-android-migrate-to-next-gen --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/google-mobile-ads-android-migrate-to-next-gen
Context preview
The summary Claude sees to decide when to auto-load this skill.
Migrates Android applications from the old, legacy Google Mobile
SKILL.md
google-mobile-ads-android-migrate-to-next-gen.SKILL.mdname: google-mobile-ads-android-migrate-to-next-gen
description: Migrates Android applications from the old, legacy Google Mobile
Ads (GMA) SDK (com.google.android.gms:play-services-ads) to the new GMA
Next-Gen SDK (com.google.android.libraries.ads.mobile.sdk:ads-mobile-sdk).
Provides comprehensive mapping tables for imports, classes, and method
signatures to help determine migration steps. Use when migrating an existing
Android codebase from the old, legacy GMA SDK to GMA Next-Gen SDK.
metadata:
version: 1.1.0
category: GoogleAds
AI Migration Agent Instructions for the Google Mobile Ads SDK
Migration Workflow
Use this checklist to track your migration progress:
- **Configure Gradle**:
- [ ] Replace `com.google.android.gms:play-services-ads` with the latest
stable version of `com.google.android.libraries.ads.mobile.sdk:ads-mobile-sdk`. If you cannot access Maven directly, run the following command to fetch the latest version. The version returned in the `latest` tag is the latest version of the GMA Next-Gen SDK:
curl -sS https://dl.google.com/dl/android/maven2/com/google/android/libraries/ads/mobile/sdk/ads-mobile-sdk/maven-metadata.xml | sed -n 's/.*<latest>\(.*\)<\/latest>.*/\1/p'
- [ ] Update `minSdk` (24+) and `compileSdk` (34+).
- [ ] Exclude `play-services-ads` and `play-services-ads-lite` from all
dependencies globally in the app-level build file to avoid duplicate symbol errors.
- [ ] Sync Gradle before moving on to the next step.
- **Per-File Migration**:
- [ ] Refactor the codebase following the API Mapping and Method Mapping
tables to migrate imports, class names, and method signature to GMA Next-Gen SDK.
- **Verify and Build**:
- [ ] Run `gradle build -x test` to confirm a successful clean build.
Resolve any GMA SDK related compile errors.
Core Migration Rules
- **App ID Usage**: **Always** use the value of the
`com.google.android.gms.ads.APPLICATION_ID` meta-data tag from `AndroidManifest.xml` for the `applicationId` in `InitializationConfig`.
- *Constraint*: Preserve the `<meta-data>` tag in the manifest; it is
still required for publishers using the User Messaging Platform SDK.
- **Initialization Sequence**:
1. Call `MobileAds.initialize()` on a background thread. 2. Ensure `initialize()` is called **before** any other SDK methods. 3. If using `RequestConfiguration`, bundle it into `InitializationConfig.Builder.setRequestConfiguration()`. **Do not** call `MobileAds.setRequestConfiguration()` before initialization.
- **UI Threading**: **MANDATORY**: Callbacks in GMA-Next Gen SDK are invoked
on a background thread. **ALL UI-RELATED OPERATIONS** (e.g., Toasts, View updates, Fragment transactions) **MUST** be wrapped in `runOnUiThread {}` or `Dispatchers.Main.launch {}` within GMA SDK callbacks. SKIPPING THIS STEP WILL CAUSE THE APPLICATION TO CRASH.
- **Mediation**: Classes implementing
`com.google.android.gms.ads.mediation.Adapter` MUST continue using `com.google.android.gms.ads`.
Format Specifics
Banner Ads
- Use `com.google.android.libraries.ads.mobile.sdk.banner.AdView` for loading
GMA Next-Gen SDK banners.
- The following API checks if a banner is collapsible:
`adView.getBannerAd().isCollapsible()`.
Native Ads
- **NativeAdLoader**: `NativeAdLoader` is abstract and cannot be instantiated.
It is used statically (e.g., `NativeAdLoader.load(...)`).
- The following APIs are now set on the `NativeAdRequest.Builder`:
- `.setCustomFormatIds(customFormatIds: List<String>)`
- `.disableImageDownloading()`
- `.setMediaAspectRatio(mediaAspectRatio: NativeMediaAspectRatio)`
- `.setAdChoicesPlacement(adChoicesPlacement: AdChoicesPlacement)`
- `.setVideoOptions(videoOptions: VideoOptions)`
- **Removal**: Delete all "Mute This Ad" logic; it is unsupported in GMA
Next-Gen SDK.
- **MediaView**: `NativeAd` no longer has a direct `mediaView` variable; use
`registerNativeAd(nativeAd, mediaView)` to associate the ad with the view.
Ad preloading
- Unless specified in the mapping table, ad preloading methods in the GMA
Next-Gen SDK retain the same API signatures and parameters as the Old SDK.
API Mapping
This table covers the main classes and their GMA Next-Gen SDK equivalents.
| Feature | Old SDK Import (`com.google.android.gms.ads...`) | GMA Next-Gen SDK Import (`com.google.android.libraries.ads.mobile.sdk...` ) | |:---------------------------|:-------------------------------------------------------------------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Core** | | | | Initialization | `MobileAds` | `MobileAds`, `initialization.InitializationConfig` | | Initialization Listener | `initialization.OnInitializationCompleteListener` | `initialization.OnAdapterInitializationCompleteListener`
Read more
name: google-mobile-ads-android-migrate-to-next-gen description: Migrates Android applications from the old, legacy Google Mobile Ads (GMA) SDK (com.google.android.gms:play-services-ads) to the new GMA Next-Gen SDK (com.google.android.libraries.ads.mobile.sdk:ads-mobile-sdk). Provides comprehensive mapping tables for imports, classes, and method signatures to help determine migration steps. Use when migrating an existing Android codebase from the old, legacy GMA SDK to GMA Next-Gen SDK. metadata: version: 1.1.0 category: GoogleAds
AI Migration Agent Instructions for the Google Mobile Ads SDK
Migration Workflow
Use this checklist to track your migration progress:
- **Configure Gradle**:
- [ ] Replace `com.google.android.gms:play-services-ads` with the latest
stable version of `com.google.android.libraries.ads.mobile.sdk:ads-mobile-sdk`. If you cannot access Maven directly, run the following command to fetch the latest version. The version returned in the `latest` tag is the latest version of the GMA Next-Gen SDK:
curl -sS https://dl.google.com/dl/android/maven2/com/google/android/libraries/ads/mobile/sdk/ads-mobile-sdk/maven-metadata.xml | sed -n 's/.*<latest>\(.*\)<\/latest>.*/\1/p'
- [ ] Update `minSdk` (24+) and `compileSdk` (34+).
- [ ] Exclude `play-services-ads` and `play-services-ads-lite` from all
dependencies globally in the app-level build file to avoid duplicate symbol errors.
- [ ] Sync Gradle before moving on to the next step.
- **Per-File Migration**:
- [ ] Refactor the codebase following the API Mapping and Method Mapping
tables to migrate imports, class names, and method signature to GMA Next-Gen SDK.
- **Verify and Build**:
- [ ] Run `gradle build -x test` to confirm a successful clean build.
Resolve any GMA SDK related compile errors.
Core Migration Rules
- **App ID Usage**: **Always** use the value of the
`com.google.android.gms.ads.APPLICATION_ID` meta-data tag from `AndroidManifest.xml` for the `applicationId` in `InitializationConfig`.
- *Constraint*: Preserve the `<meta-data>` tag in the manifest; it is
still required for publishers using the User Messaging Platform SDK.
- **Initialization Sequence**:
1. Call `MobileAds.initialize()` on a background thread. 2. Ensure `initialize()` is called **before** any other SDK methods. 3. If using `RequestConfiguration`, bundle it into `InitializationConfig.Builder.setRequestConfiguration()`. **Do not** call `MobileAds.setRequestConfiguration()` before initialization.
- **UI Threading**: **MANDATORY**: Callbacks in GMA-Next Gen SDK are invoked
on a background thread. **ALL UI-RELATED OPERATIONS** (e.g., Toasts, View updates, Fragment transactions) **MUST** be wrapped in `runOnUiThread {}` or `Dispatchers.Main.launch {}` within GMA SDK callbacks. SKIPPING THIS STEP WILL CAUSE THE APPLICATION TO CRASH.
- **Mediation**: Classes implementing
`com.google.android.gms.ads.mediation.Adapter` MUST continue using `com.google.android.gms.ads`.
Format Specifics
Banner Ads
- Use `com.google.android.libraries.ads.mobile.sdk.banner.AdView` for loading
GMA Next-Gen SDK banners.
- The following API checks if a banner is collapsible:
`adView.getBannerAd().isCollapsible()`.
Native Ads
- **NativeAdLoader**: `NativeAdLoader` is abstract and cannot be instantiated.
It is used statically (e.g., `NativeAdLoader.load(...)`).
- The following APIs are now set on the `NativeAdRequest.Builder`:
- `.setCustomFormatIds(customFormatIds: List<String>)`
- `.disableImageDownloading()`
- `.setMediaAspectRatio(mediaAspectRatio: NativeMediaAspectRatio)`
- `.setAdChoicesPlacement(adChoicesPlacement: AdChoicesPlacement)`
- `.setVideoOptions(videoOptions: VideoOptions)`
- **Removal**: Delete all "Mute This Ad" logic; it is unsupported in GMA
Next-Gen SDK.
- **MediaView**: `NativeAd` no longer has a direct `mediaView` variable; use
`registerNativeAd(nativeAd, mediaView)` to associate the ad with the view.
Ad preloading
- Unless specified in the mapping table, ad preloading methods in the GMA
Next-Gen SDK retain the same API signatures and parameters as the Old SDK.
API Mapping
This table covers the main classes and their GMA Next-Gen SDK equivalents.
| Feature | Old SDK Import (`com.google.android.gms.ads...`) | GMA Next-Gen SDK Import (`com.google.android.libraries.ads.mobile.sdk...` ) | |:---------------------------|:-------------------------------------------------------------------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Core** | | | | Initialization | `MobileAds` | `MobileAds`, `initialization.InitializationConfig` | | Initialization Listener | `initialization.OnInitializationCompleteListener` | `initialization.OnAdapterInitializationCompleteListener`
This repository contains Agent Skills for Google products and technologies, including Google Cloud. This repository is under active development.
Repo: google/skills
Other skills on google-skills.
- /data-manager-api-audience-ingestion
Guides developers through managing (adding, removing, and clearing) audience members for Google products using the Data Manager API and its associated client libraries. Use this skill when the user wants to upload audience members, remove specific users, or clear/replace an
Open skill - /data-manager-api-event-ingestion
Guides developers through implementing event and conversion ingestion to Google products using the Data Manager API /v1/events/ingest endpoint and its associated client libraries. Use this skill when the user wants to upload offline conversions, enhanced conversions for leads,
Open skill - /data-manager-api-setup
Guides developers through client library installation and authentication setup steps for the Data Manager API. Use this skill when a user is getting started with the Data Manager API and needs to setup their local environment, install the client library, or setup access to the
Open skill - /google-ads-api-account-diagnostics
Diagnoses Google Ads account performance issues such as conversion loss (value or volume), low lead flow/volume, and lost impression share (opportunities) due to ad rank, bids, or budgets. Use when troubleshooting sudden performance drops, analyzing campaign impression share
Open skill - /google-ads-api-mcp-setup
Guides developers through downloading, configuring, and installing the official open-source Google Ads MCP Server. Use this skill when a user wants to connect their AI assistant (such as Gemini, Claude Code, or Cursor) to their Google Ads account to query campaigns or retrieve
Open skill - /google-ads-api-quickstart
Guides developers through Google Ads API quickstart: credential setup, choosing from 6 client libraries/REST, configuring environments, and running a "retrieve campaigns" script. Troubleshoots common setup errors: USER_PERMISSION_DENIED, login_customer_id issues, and
Open skill

