What does this skill do, and when should you use it?
This skill is for developers migrating Android applications from the legacy Google Mobile Ads SDK to the GMA Next-Gen SDK. It provides Gradle configuration checks, a per-file migration workflow, and mapping tables for imports, classes, and method signatures. The guidance covers initialization, banner, native, interstitial, rewarded, preloading, response information, and Ad Manager migrations. It also highlights application ID handling, initialization order, and UI-thread requirements for callbacks.
Guides replacement of play-services-ads with ads-mobile-sdk, updates to minSdk and compileSdk, and global exclusion of legacy ad dependencies; directs source changes using API and method mapping tables; requires using the APPLICATION_ID value from AndroidManifest.xml during initialization; documents replacements for banner, native, interstitial, rewarded, preloading, and response-information APIs; and recommends running gradle build -x test to verify the build.
- An Android developer maintaining an application that still uses the legacy Google Mobile Ads SDK and needs a migration plan.
- An engineer upgrading the ads SDK who needs to reconcile changed imports, class names, and method signatures.
- A team using banner, native, interstitial, rewarded, or preloading APIs that needs format-specific migration references.
- A developer troubleshooting initialization order, callback threading, application ID, or duplicate-symbol issues during migration.
How do you install this skill?
- Do not fetch an unpinned latest SDK version without confirmation; record and review the exact version.
- Global exclusion of legacy play-services-ads dependencies may affect other modules or mediation adapters; inspect the dependency graph and retain a rollback path first.
- The initialization callback type is documented inconsistently and must be checked against the actual SDK API and compilation results.
- Add validation that does not skip tests, failure diagnostics, complete examples, and Chinese-environment guidance.
- Shell / CLI
- Network access
- Local filesystem
Gradlecurlsed
Install the repository’s skill collection with: npx skills add google/skills. Select the target skill during installation. The repository contains about 90 skills; this entry corresponds to skills/ads/google-mobile-ads-android-migrate-to-next-gen/SKILL.md. The README does not document client-specific installation steps.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/google/skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/skills/ads/google-mobile-ads-android-migrate-to-next-gen" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Once installed, send your agent any of these to trigger it:
- Check and migrate this Android project using the Google Mobile Ads Next-Gen migration checklist.
In an Agent Skills-compatible client, provide an Android GMA project and request migration from com.google.android.gms:play-services-ads to com.google.android.libraries.ads.mobile.sdk:ads-mobile-sdk. Example: “Check and migrate this Android project using the Google Mobile Ads Next-Gen migration checklist.” Apply the resulting recommendations to Gradle, AndroidManifest.xml, and source files, then run gradle build -x test. The source does not define a client-specific trigger syntax.
What are this skill's strengths and limitations?
- Includes detailed mappings for legacy and Next-Gen imports, classes, and method signatures.
- Clearly states Gradle, initialization, threading, and dependency-exclusion requirements.
- Covers multiple ad formats, preloading, response information, and Ad Manager APIs.
- Released under Apache-2.0; the repository is under active development.
- Provides migration guidance and reference tables, not an automated migration script.
- The supplied source includes no test suite, sample project, or platform validation results.
- Some steps require Maven access and an existing Android/Gradle project environment.
- Users must handle switching callback UI operations to the UI thread themselves.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Google Mobile Ads Next-Gen Migration Assistant this page ✓ Google · Official | 46 · Use with care | ★ 21k | 12d ago | Apache-2.0 |
| Google Mobile Ads SDK Starter ✓ Google · Official | 43 · Not recommended | ★ 21k | 12d ago | Apache-2.0 |
| Google Mobile Ads Rewarded Ads Guide ✓ Google · Official | 47 · Use with care | ★ 21k | 12d ago | Apache-2.0 |
| Google Mobile Ads Interstitial Integration Guide ✓ Google · Official | 41 · Not recommended | ★ 21k | 12d ago | Apache-2.0 |
| Google Mobile Ads Banner Integrator ✓ Google · Official | 47 · Use with care | ★ 21k | 12d ago | Apache-2.0 |
Compared with continuing to use the legacy Google Mobile Ads SDK or manually researching each difference, this skill provides direct legacy-to-Next-Gen mappings for APIs, callbacks, and configuration. It does not cover migration from other advertising SDKs.
How did FollowSkills review this skill?
The material shows no malware, credential theft, or covert exfiltration, and the migration scope is generally limited to the Android ads SDK. However, it instructs the agent to fetch an unpinned latest dependency version via curl and to exclude legacy dependencies globally, without requiring confirmation, explaining data flows, or providing rollback steps, so points are deducted.
The workflow clearly covers Gradle configuration, per-file migration, and a build check. However, the initialization callback type is inconsistent between the mapping table and method signature, the dependency version is not pinned, tests are explicitly skipped, and abnormal-input diagnostics and recovery guidance are thin, so the score remains below the static-review ceiling.
The intended audience and migration scenario are clear, and the API and method tables provide broad coverage. Still, prerequisites, non-fit boundaries, trigger conditions, and handling of project-specific configurations are under-specified. Chinese-language support is not documented, and version retrieval depends on an external Maven service, so environment-fit evidence is limited.
The skill has metadata versioning, readable sections, a checklist, and mapping tables. Repository README, Apache-2.0 licensing, and official-organization provenance provide basic governance evidence. It lacks concrete examples, FAQs, known limitations, a changelog, and clearly assigned maintenance and update procedures, so points are deducted.
The mappings and migration rules can directly support part of the API refactor and establish a clear core objective. However, there is no complete end-to-end example, directly applicable patch, or verified representative output; the prescribed build also skips tests, leaving substantial manual validation and rework.
The file contains auditable migration rules, signatures, and mappings, with repository version and licensing context. It provides no citations, committed tests, key-path CI coverage, or third-party execution evidence, so conclusions rely mainly on a single documentation source and receive a conservative score.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →