Agent skill

Play Billing Library Version Upgrade

by arindamxd in arindamxd/camerax-android

A skill your agent uses when upgrading or migrating an Android project from any legacy Google Play Billing Library (PBL) version to the latest stable version of PBL.

Apache-2.0Auto-check passedDevelopment

Install Play Billing Library Version Upgrade

skills CLI
$ npx skills add arindamxd/camerax-android --skill play-billing-library-version-upgrade -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install arindamxd/camerax-android play-billing-library-version-upgrade --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/arindamxd/camerax-android.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/play-billing-library-version-upgrade .claude/skills/play-billing-library-version-upgrade && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
play-billing-library-version-upgrade
GitHub stars
132
Used in
5 other repos
Token cost
~1.4k tokens
SKILL.md length
682 words
Files
4 (incl. references)
Skills in repo
21
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when upgrading or migrating an Android project from any legacy Google Play Billing Library (PBL) version to the latest stable version of PBL.

  • Works in 4 steps: Intent Message → Discovery \& Situational Awareness → Contextual Document Mapping \& Planning → …
  • Migrating an Android project from any legacy Google Play Billing Library (PBL) version to the latest stable version of PBL
  • SKILL.md covers Phase 0: Intent Message, Phase 1: Discovery \&…, Phase 2: Contextual Document… and Phase 3: Instructions for…, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Play Billing Library Version Upgrade is an agent skill from arindamxd/camerax-android. Use this skill when upgrading or migrating an Android project from any legacy Google Play Billing Library (PBL) version to the latest stable version of PBL.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `references/android/google/play/billing/release-notes.md`, `references/migration-logic.md` and `references/version-checklist.md`).

It sits in Development, covering Code migrations. It works with Android and Gradle. The repository describes itself as: A Play Store camera app showing Jetpack CameraX APIs in Kotlin — install it, use it, copy the patterns. The licence is Apache-2.0.

When your agent uses it

  • Migrating an Android project from any legacy Google Play Billing Library (PBL) version to the latest stable version of PBL
  • Tasks that involve Code migrations

Example prompts

  • “/play-billing-library-version-upgrade”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Intent Message
  2. Discovery \& Situational Awareness
  3. Contextual Document Mapping \& Planning
  4. Instructions for Execution

What it can do on your machine

Read from SKILL.md and the folder at commit 7c36352. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • developer.android.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Play Billing Library Version Upgrade loads about 1.4k tokens when it runs, and up to ~23k if it reads all its reference files. Until then it costs about 48 tokens; SKILL.md has 682 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~48
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~23k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from arindamxd/camerax-android at commit 7c36352, republished under its Apache-2.0 licence (© arindamxd). 682 words, ~1,411 tokens.

Download SKILL.mdSave it as .claude/skills/play-billing-library-version-upgrade/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
play-billing-library-version-upgrade
description
Use this skill when upgrading or migrating an Android project from any legacy Google Play Billing Library (PBL) version to the latest stable version of PBL.
license
Complete terms in LICENSE.txt
metadata.author
Google LLC
metadata.last-updated
2026-08-06
metadata.keywords
android, play billing, play billing library, pbl, upgrade, migration, deprecation, google play

Phase 0: Intent Message

Reporting Action: Before proceeding, immediately tell the user: "I will upgrade Play Billing Library to the latest version."

Phase 1: Discovery & Situational Awareness

  1. Primary Check (Build Version) : Locate the project's billing dependency (e.g., com.android.billingclient:billing) in build.gradle, build.gradle.kts, or libs.versions.toml.
  2. Initial Compilation Test: Attempt to sync and build the project immediately.
  3. Fallback Discovery (Effective Version) :
    • Trigger: Only if the build fails immediately, scan the source code for deprecated artifacts.
    • Logic : The presence of deprecated APIs indicates the "Effective Version" ---defined as the version where those specific APIs were last available, not when they were introduced.
    • Example : If SkuDetails is present, treat the baseline as PBL v7 or earlier (regardless of the version string in build.gradle).
  4. Identify Target & Path : Access the version tool or release notes to find the latest stable version and calculate a [Direct/Stepped] migration path based on the Effective Version baseline.
  • Calculate Migration Path :
    • If the Effective Version is within 2 major versions of the target: Plan a Direct Migration.
    • If it is more than 2 major versions behind: Plan a Stepped Migration. Migrate by two major versions at a time (e.g., v4 -> v6 -> v8) until you are within two versions of the target.
  • Reporting Action: Before proceeding, tell the user: "I've detected you are effectively on PBL [Current] and the latest is [Target]. I am planning a [direct/stepped] migration path."

Phase 2: Contextual Document Mapping & Planning

For every major version jump identified in your path, you MUST synthesize instructions from:

  • Migration Guide (where [X] is the target major version).
  • Release Highlights : The "Deprecations" and "Breaking Changes" sections of the relevant Release Notes.
  • Developer Documentation: Consult your knowledge of the Google Play Billing documentation regarding the relevant features used in this app (e.g., Subscriptions, One-Time Products).
  • Develop the Plan: Identify every specific code change required (API removals, class replacements, logic shifts) and print this out as a checklist.

Phase 3: Instructions for Execution

Reporting Action: For each of the following steps, give a brief explanation of what you will be doing prior to execution, and a brief summary of what you accomplished afterwards.

Step 1: SDK & Environment Alignment
  • Action : Update build.gradle to meet SDK requirements (e.g., "PBL 9 requires compileSdk 35").
  • Gradle Version: Verify if the new library requires a newer Android Gradle Plugin (AGP) or Kotlin version.
Show full SKILL.md (295 more words)Show less
Step 2: Intent-based Refactoring

Analyze the intent of the existing code rather than performing purely textual string replacement.

  • Action : You MUST follow all deprecation instructions and refactor patterns from both the references/migration-logic.md section, the official migration guides, and the general documentation pages identified in Phase 2.
  • Verification : Verify you are doing all steps from all documentation and then making sure you follow the specific directions from the checklist in the references.
Step 3: Sequential Verification (Only applicable for Stepped Migrations)
  1. Upgrade to the first major intermediate version in your path.
  2. Run ./gradlew assembleDebug to verify no intermediate breaking changes were missed.
  3. Repeat until you reach the final target version.
Step 4: Final Validation Checklist
  1. Smart Checklist Verification:
  2. Open references/version-checklist.md and locate the Smart Version-Specific Checklist.
  3. Action: For every version between your [Detected Effective Version] and [Detected New Version], verify that every item has been addressed in the code using "Find in Files" or structural analysis.
  4. Tests : Run all unit and implementation tests (./gradlew test).
  5. Clean Build : Verify the project completes a full clean build: ./gradlew clean assembleDebug. Then, run ./gradlew sync and ./gradlew build so that the user can immediately test the new version manually.

Final Report

Explain the "Why" to the developer:

  • "I updated your SDK to [Version] because PBL [Version] requires it for [Reason from docs]."
  • "I removed your custom retryConnection() logic because it is now handled natively by the library using enableAutoServiceReconnection()."
  • "Successfully upgraded from PBL [Old] to PBL [New] and verified with unit tests. Based on an analysis of features in the latest library and this application's current feature set, I suggest exploring [New Feature] (e.g., Prepaid Plans or Installments) from the latest release because it is now available but not yet implemented."

© arindamxd, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in .agents/skills/play-billing-library-version-upgrade of arindamxd/camerax-android.

  • SKILL.md
  • references/android/google/play/billing/release-notes.md
  • references/migration-logic.md
  • references/version-checklist.md

Open the folder on GitHubat commit 7c36352

Used in 5 other repositories

We found 9 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 5 other GitHub owners. This page covers the copy in arindamxd/camerax-android, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Play Billing Library Version Upgrade next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Play Billing Library Version Upgrade compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Play Billing Library Version Upgrade this skillarindamxd/camerax-android1325 repos~1.4kAutomated safety check: PassApache-2.0
Project Gradle Third Party Version UpgradeafkT/DevUtils1.6k—~1.2kAutomated safety check: PassApache-2.0
Hz API Upgrademeta-quest/agentic-tools213—~1.8kAutomated safety check: PassApache-2.0
jscpd Code Migration Trackerkucherenko/jscpd6.3k—~5kAutomated safety check: PassMIT
Codebase Comparison with jscpdkucherenko/jscpd6.3k—~3.2kAutomated safety check: PassMIT
Groovy 5 Developer Guideapache/grails-core2.9k—~3kAutomated safety check: PassApache-2.0

Similar skills

  • 对 DevUtils 工程(DEPSROOT=file/gradle、DEPSMANIFEST=file/deps)中定义的第三方库 GAV 依赖做版本查证与升级;结合 Maven Central、Google Maven、Gradle Plugin Portal、 JitPack 与 GitHub Releases/README 交叉校验「最新可用版本」;必要时修正…

    1.6k GitHub stars~1.2k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Hz API Upgrade

    meta-quest/agentic-tools

    Upgrades Meta VR apps to newer Horizon OS SDK versions — migration guides, deprecated API replacements, changelog.

    213 GitHub stars~1.8k tokensUpdated 13 days ago
    DevelopmentAuto-check passed
  • Measures a code port between languages or frameworks with jscpd's function-level comparison, porting tests before code and tracking what is left unmatched.

    6.3k GitHub stars~5k tokensUpdated today
    DevelopmentAuto-check passed
  • Compares two folders function by function with jscpd --compare, across languages if needed, and explains which functions match and which have no counterpart.

    6.3k GitHub stars~3.2k tokensUpdated today
    DevelopmentAuto-check passed
  • Groovy 5 Developer Guide

    apache/grails-core

    Guidance for Groovy 5 work in Grails projects: syntax, closures, traits, DSLs, metaprogramming, Spock tests, static compilation and Java 21 integration.

    2.9k GitHub stars~3k tokensUpdated today
    DevelopmentAuto-check passed
  • Update Version Catalog

    RedMadRobot/gradle-version-catalogs

    Use EVERY time the user asks to update / bump the version catalogs, "сделать обновление", "обновить каталог(и)", "обнови версии", "оформи изменения", "update the catalog", or to record dependency…

    118 GitHub stars~9.5k tokensUpdated 4 days ago
    DevelopmentAuto-check passed

More from arindamxd/camerax-android

All 21 skills in this repo
  • Styles

    arindamxd/camerax-android

    A skill your agent uses to integrate the Jetpack Compose Styles API into an Android project.

    132 GitHub starsUsed in 4 repos~2.3k tokens
    Auto-check passed
  • Verified Email

    arindamxd/camerax-android

    Provides a complete workflow for implementing verified email retrieval on Android Credential Manager API.

    132 GitHub starsUsed in 4 repos~4.7k tokens
    Auto-check passed
  • Edge To Edge

    arindamxd/camerax-android

    A skill your agent uses to migrate your Jetpack Compose app to add adaptive edge-to-edge support and troubleshoot common issues.

    132 GitHub starsUsed in 5 repos~3.6k tokens
    Auto-check passed
  • Camerax

    arindamxd/camerax-android

    Provide technical guidance for Android camera development with CameraX.

    132 GitHub starsUsed in 2 repos~1.6k tokens
    Auto-check passed
  • Leanback To Compose Tv Migration

    arindamxd/camerax-android

    Provides instructions and architectural patterns for migrating Android TV applications from legacy Leanback UI Toolkit, Android Views, or Support Fragments to Jetpack Compose for TV (androidx.tv).

    132 GitHub starsUsed in 2 repos~8.7k tokens
    Auto-check passed
  • Migrate XML Views To Jetpack Compose

    arindamxd/camerax-android

    Provides a structured workflow for migrating an Android XML View to Jetpack Compose.

    132 GitHub starsUsed in 5 repos~1.4k tokens
    Auto-check passed

Works with

Categories

Questions about Play Billing Library Version Upgrade

What does Play Billing Library Version Upgrade do?

A skill your agent uses when upgrading or migrating an Android project from any legacy Google Play Billing Library (PBL) version to the latest stable version of PBL. Play Billing Library Version Upgrade is an agent skill from arindamxd/camerax-android. Use this skill when upgrading or migrating an Android project from any legacy Google Play Billing Library (PBL) version to the latest stable version of PBL.

When should I use Play Billing Library Version Upgrade?

Play Billing Library Version Upgrade fits situations like: migrating an Android project from any legacy Google Play Billing Library (PBL) version to the latest stable version of PBL; tasks that involve Code migrations.

How do I install Play Billing Library Version Upgrade in Claude Code?

Run `npx skills add arindamxd/camerax-android --skill play-billing-library-version-upgrade -a claude-code`. Or copy the skill folder (.agents/skills/play-billing-library-version-upgrade in arindamxd/camerax-android) into .claude/skills/play-billing-library-version-upgrade in your project. Claude Code loads it when a task matches its description.

How do I install Play Billing Library Version Upgrade in Codex?

Run `npx skills add arindamxd/camerax-android --skill play-billing-library-version-upgrade -a codex`. Or copy the skill folder (.agents/skills/play-billing-library-version-upgrade in arindamxd/camerax-android) into .agents/skills/play-billing-library-version-upgrade in your project. Codex loads it when a task matches its description.

Can I use Play Billing Library Version Upgrade in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add arindamxd/camerax-android --skill play-billing-library-version-upgrade -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/play-billing-library-version-upgrade, .gemini/skills/play-billing-library-version-upgrade, .github/skills/play-billing-library-version-upgrade and .opencode/skills/play-billing-library-version-upgrade in your project.

What does Play Billing Library Version Upgrade need to run?

SKILL.md names no scripts, command-line tools or credentials: Play Billing Library Version Upgrade is instructions for the agent only.

Does Play Billing Library Version Upgrade access the network?

SKILL.md names 1 domain. As links in the text: developer.android.com. This is read from the text; nothing was executed.

Is Play Billing Library Version Upgrade safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Play Billing Library Version Upgrade use?

Play Billing Library Version Upgrade is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Play Billing Library Version Upgrade use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 22k tokens, read only when the agent opens those files.

What are the alternatives to Play Billing Library Version Upgrade?

Skills that share tags, products or a category with Play Billing Library Version Upgrade: Project Gradle Third Party Version Upgrade (afkT/DevUtils, 1.6k stars), Hz API Upgrade (meta-quest/agentic-tools, 213 stars), jscpd Code Migration Tracker (kucherenko/jscpd, 6.3k stars) and Codebase Comparison with jscpd (kucherenko/jscpd, 6.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Play Billing Library Version Upgrade?

arindamxd (a GitHub user) maintains it in arindamxd/camerax-android, which has 132 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 2, 2026.

Source: arindamxd/camerax-android on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.