What does this skill do, and when should you use it?
This skill provides implementation, integration, and configuration guidance for Google Mobile Ads SDK rewarded ads in Android and iOS mobile applications. It first requires the platform and ad placement to be identified, then directs the client to the relevant platform guide. Its workflow covers loading the ad, registering event callbacks, adding an opt-in UI, showing the ad, and verifying the implementation. It explicitly excludes rewarded interstitial ads.
Identifies whether the project is Android or iOS; confirms the target file for ad placement; reads references/android-rewarded.md or references/ios-rewarded.md; and guides the user through loading the ad, registering ad event callbacks, adding an opt-in UI element, showing the ad, and verifying the implementation.
- An Android developer needs to add ads that users explicitly choose to watch for in-app rewards.
- An iOS developer needs platform-specific guidance for configuring Google Mobile Ads SDK rewarded ads.
- A team wants a checklist covering ad loading, callbacks, opt-in UI, display, and verification.
- A developer is unsure which target file should contain the rewarded ad implementation.
How do you install this skill?
- Before adoption, verify that the documented Android/iOS GMA SDK APIs still match the project's current SDK versions, and add initialization, test-ad units, lifecycle, idempotent reward, and failure/retry handling.
- Separately assess ad-SDK data collection, consent, regional compliance, and mainland-China reachability; these areas are not covered by the skill.
- Android requires moving all UI work from SDK callbacks to the main thread; this assertion was not execution-tested in this static review.
- Local filesystem
Install the repository's skill collection with npx skills add google/skills. Select this skill during installation. The source does not document a separate command, client directory layout, or version-management procedure for installing only this skill.
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-rewarded" ~/.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:
- Integrate Google Mobile Ads SDK rewarded ads into my Android app.
In a client where the skill is loaded, use a prompt such as: “Integrate Google Mobile Ads SDK rewarded ads into my Android app.” State whether the project is Android or iOS and identify the target file for the ad placement; the skill should ask when either detail is unclear. Do not use it for rewarded interstitial ads. The source does not include the contents of the platform reference guides, so their detailed implementation steps are undocumented here.
What are this skill's strengths and limitations?
- Covers rewarded ad implementation for both Android and iOS.
- Uses a clear five-step workflow.
- Requires placement review and an explicit user opt-in before showing the ad.
- The supplied source does not include the Android or iOS reference-guide contents or code examples.
- No test suite, automated verification script, or SDK version requirement is documented.
- The scope excludes rewarded interstitial ads.
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 Rewarded Ads Guide this page ✓ Google · Official | 47 · Use with care | ★ 21k | 12d ago | Apache-2.0 |
| Google Mobile Ads Banner Integrator ✓ Google · Official | 47 · 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 Interstitial Integration Guide ✓ Google · Official | 41 · Not recommended | ★ 21k | 12d ago | Apache-2.0 |
| Google Mobile Ads Next-Gen Migration Assistant ✓ Google · Official | 46 · Use with care | ★ 21k | 12d ago | Apache-2.0 |
How did FollowSkills review this skill?
The skill requires confirmation of the platform, target file, and user opt-in for rewarded ads; it does not explain ad data flows, privacy/compliance handling, dependency versions, permission boundaries, reward-grant security, or rollback. No prompt injection, credential theft, covert exfiltration, or destructive default is evident.
Android and iOS cover the basic load, callback, display, and build-verification sequence, and Android flags callback threading. However, there are no complete reproducible examples, initialization prerequisites, lifecycle guidance, retry policy, duplicate-display handling, or robust abnormal-input feedback, and SDK versions are unspecified; static evidence supports only a modest score.
The name and description clearly target Google Mobile Ads rewarded ads on Android or iOS and explicitly exclude rewarded interstitials. The workflow asks for clarification when the platform is unclear, but it does not define broader non-fit cases, project-environment requirements, Chinese-language support, or mainland-China reachability, limiting trigger precision and environment-fit evidence.
The skill has a clear SKILL.md, separate Android and iOS reference files, version 1.0.0 metadata, a category, and a progressive workflow. Repository context supplies Apache-2.0 licensing, installation, issue reporting, and contribution paths. Points are deducted for no changelog, named maintenance responsibility, SDK compatibility matrix, FAQ, complete examples, or explicit update policy.
The core sequence covers loading, event callbacks, user choice, showing the ad, and build checks; Android API signatures and platform-specific cautions add practical value for basic integration. However, missing initialization context, test-ad configuration, complete code, reward consistency, and show-failure handling mean substantial project-specific rework remains.
The files provide concrete Android API signatures, a threading assertion, build commands, and official-document fallback paths, giving limited auditability. This review is static only: there is no executed evidence, committed test suite, or corroboration across sources, and the referenced external documentation is not included; the static ceiling therefore applies.
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 →