How to use the Google Mobile Ads banner setup agent skill

What is an agent skill, and what does this one do?

An agent skill is a folder of instructions that an AI agent can load when a task matches the skill's description. This skill is named google-mobile-ads-banner and is published by google/skills under the Apache-2.0 licence. Its main file, SKILL.md, tells the agent to set up banner ads for the Google Mobile Ads SDK, referred to as GMA.

• Determines the platform (Android, iOS or Unity) and asks you if it is unclear.
• Reads the matching platform guide: references/android-banner.md, references/ios-banner.md or references/unity-banner.md.
• Defaults to the Large Anchored Adaptive banner type when you just say "banner".
• Works through five steps in order: define the ad view, set the ad size, register for ad load events, load the banner ad, and verify the implementation.
• Reminds you to replace the test ad unit ID with your own after the banner is working.

How do you install the skill?

You can install the skill in either of two ways. Download the ZIP from the skill's page on our directory and unzip it into one of these locations:

• Personal skills folder: ~/.claude/skills/
• A single project: the .claude/skills/ folder inside your project
• Or, in the Claude apps, go to Settings → Capabilities → Skills and upload the ZIP.

What do you need before you start?

The skill gives instructions but does not install the ads SDK or build tools for you. Check these requirements first.

• The Google Mobile Ads SDK for your target platform (Android, iOS or Unity).
• A project build environment for that platform.
• A Google AdMob account and ad unit ID for production use. Test IDs work without one, so you can start development without it.

How do you trigger the skill with a request?

You do not need to name the skill. Describe the task in plain language that mentions banner ads and a mobile app. The skill's description covers setting up banner ads in Android, iOS or Unity apps.

• "Add a banner ad to the bottom of my Android home screen."
• "Set up a Google Mobile Ads banner in my SwiftUI app." (The skill is written for iOS, so name the platform.)
• "Integrate a banner ad into my Unity game using the Google Mobile Ads SDK."
• "Make the banner ad a large anchored adaptive banner and use test IDs for now."

What does the agent do during setup?

Once triggered, the agent follows the platform guide in order. The steps are defining the ad view, setting the ad size, registering for ad load events, loading the banner, and verifying the result. For iOS, the guide uses the test ad unit ID ca-app-pub-3940256099942544/2435281174 and suggests a width of 375 for testing, noting that device width is also a common approach. For Unity, the guide lists separate test IDs for Android and iOS anchored adaptive banners.

Review the code the agent writes against the platform guide, since the agent follows those files.

What are the safety notes?

This skill runs no scripts and makes no network requests of its own. It is made of Markdown instructions that guide the agent's code changes. You are still responsible for the code the agent writes and for the ad unit IDs it uses.

The skill does not cover interstitial or rewarded ads. Ask for those separately or use another resource.

• Test ad unit IDs are for development only. Replace them with your own AdMob ad unit IDs before release.
• The agent may leave test IDs in place if you ignore its reminder, so check this before you ship.

What tips help you get the best results?

Name your platform and your build tool, since the skill asks when it is unclear. Keep the default large anchored adaptive banner unless you have a reason to change it. The iOS guide notes that if large anchored adaptive banners look too tall, the agent can use currentOrientationAnchoredAdaptiveBanner(width:) instead.

• State the platform in your first message.
• Ask the agent to verify the implementation at the end.
• Search your project for the test ad unit ID before you release.