Google just published a set of Android skills a collection of expert, AI-optimised instructions covering the most common and painful Android development workflows. (Upgrading to AGP 9, migrating XML layouts to Compose, wiring up Navigation 3.) AI automated step-by-step procedures grounded in official Android best practices.
The GitHub repo defaults to wiring them into Gemini CLI (of course). This blog post shows you how to wire them into Claude Code.
What Are “Agent Skills”?
The Android skills repo is built on the open-standard agent skills format, an open specification, originally developed by Anthropic and now adopted widely across the AI coding agent ecosystem (Cursor, Gemini, GitHub Copilot, Claude Code, Codex, VS Code, and many more).
The concept is simple. A skill is just a folder with a SKILL.md file inside it:
my-skill/
- SKILL.md # Required: metadata + instructions
- references/ # Optional: documentation, guides
- scripts/ # Optional: executable helpers
- assets/ # Optional: templates, resources
The SKILL.md file starts with YAML frontmatter giving the skill a name and description, followed by markdown instructions for the agent:
---
name: my-skill
description: A short summary of what this skill does and when to use it.
metadata:
author: Your Name
keywords:
- relevant
- keywords
---
## Instructions
Your detailed instructions here. The agent reads these when the task matches.
The agent discovery process works in three stages:
- Discovery – At startup, only the
nameanddescriptionare loaded. The agent knows what skills exist without blowing up its prompt size (context window). - Activation – When you ask for something that matches a skill’s description, the full
SKILL.mdis read into context. - Execution – The agent follows the instructions, loading any referenced files or running any bundled scripts as needed.
What’s in the Android Skills Repo?
The android/skills repository currently ships six skills:
| Skill | What it does |
|---|---|
agp-9-upgrade | Upgrades an Android project to AGP 9 |
migrate-xml-views-to-jetpack-compose | Convert XML layouts to Compose |
navigation-3 | Install and migrate to Jetpack Navigation 3, including deep links and Hilt integration |
r8-analyzer | Identifies redundant and overly-broad R8 keep rules to shrink your APK |
play-billing-library-version-upgrade | Migrates any legacy Play Billing Library versions |
edge-to-edge | Adds adaptive edge-to-edge support and fixes inset issues in Compose apps |
Each skill is backed by ‘official’ Android documentation references and packs knowledge into a format your AI agent can actually act on.
How the Repo Is Set Up (for Gemini CLI)
Out of the box, the Android CLI install command targets Gemini CLI:
android skills add --all
Without specifying an agent, it deploys skills to ~/.gemini/antigravity/skills. You can also be specific:
# Install all skills for Gemini
android skills add --all --agent=gemini
# Install just the Compose migration skill
android skills add --skill=migrate-xml-views-to-jetpack-compose
If you’re a Gemini CLI user, that’s all you need. Skills are immediately available in your next session.
Manually Adding Them to Claude Code
Claude Code also supports the agent skills format. Skills placed in ~/.claude/skills/ are loaded at startup and available across all your projects.
Since the Android CLI doesn’t (yet) auto-install to the Claude Code directory, it takes a couple of minutes to do manually:
# Clone the repo
git clone https://github.com/android/skills /tmp/android-skills
# Create the Claude skills directory
mkdir -p ~/.claude/skills
# Install each skill
for skill in \
"build/agp/agp-9-upgrade" \
"jetpack-compose/migration/migrate-xml-views-to-jetpack-compose" \
"navigation/navigation-3" \
"performance/r8-analyzer" \
"play/play-billing-library-version-upgrade" \
"system/edge-to-edge"; do
name=$(basename "$skill")
mkdir -p ~/.claude/skills/$name
cp /tmp/android-skills/$skill/SKILL.md ~/.claude/skills/$name/SKILL.md
done
Start or restart Claude Code and the skills are live. You can invoke them like any built-in command — /navigate-xml-views-to-jetpack-compose or just describe what you want and Claude will activate the relevant skill automatically.
One-Shot Prompt: Let Claude Install Them For You
If you’ve already cloned the repo locally, you can paste this prompt into Claude Code and let it handle everything:
I have the android/skills repository cloned at /path/to/android/skills
Please install all the SKILL.md files into my Claude user skills directory at ~/.claude/skills/
For each skill found in the repo, create a directory under ~/.claude/skills/ named after the skill folder, then copy the SKILL.md into it.
When done, list the installed skills to confirm.
Replace /path/to/android/skills with your actual clone path. Claude Code will find the skills, create the directories, and confirm installation. (And is your claude has git access, you can even get it to do the clone as well 🙂 )
Takeaway
The Android skills repo is a practical demonstration of what the open-standard agent skills format makes possible: expert, reusable Android knowledge that works across agents. Whether you’re on Gemini CLI, Claude Code, Cursor, or anything else that supports the format, you get the same quality instructions.
Outside of the amazing Android skills we can now run, the next best bit is the skills protocol. Now that you’ve seen the format, writing your own skills for your team’s specific patterns, custom architecture rules, internal library migrations, release checklists, is genuinely straightforward. A folder, a markdown file, and a good description is all it takes.
Go check out agentskills.io and the android/skills repo, and get those skills loaded.

Leave a Reply