Google has published a library of Android skills: short instruction files that teach AI coding agents how to do Android work the current way. If your agent keeps writing outdated Android code, these skills are the fix. They’re free, open source, and work with Claude Code, Codex, Gemini and other agents.
Here are the quick facts before we get into how it works.
- Hosted in the official android/skills GitHub repository, licensed Apache 2.0.
- Google’s skills catalog lists 24 skills, from Compose migration to R8 audits.
- Install with the Android CLI:
android skills add <skill-name>. - Follows the open agent skills standard, so any compatible tool can use them.
- Google’s docs page was last updated on September 25, 2026.
That’s the whole pitch: one command, and your agent gets Google’s own playbook for a task.
What are Android skills, really?
A skill is a folder with a SKILL.md file. It holds step-by-step instructions, and sometimes scripts, templates and reference docs. The agent reads it only when your prompt matches the task.
Say you type “make my app UI edge-to-edge.” The agent loads the matching skill and follows Google’s steps instead of guessing from old training data. According to Google’s Android Developers documentation, that’s the main point: grounding models in newer Android knowledge than they were trained on.
The repository’s README also says the project targets areas where language models tend to struggle, not basics like simple Jetpack Compose screens.
Google lists three other benefits. Multi-step jobs become more consistent, skills can bundle scripts and templates with the instructions, and teams can share their own Android patterns the same way.
Which tasks do the skills cover?
| Area | Example skill | What it helps with |
|---|---|---|
| Build tooling | Upgrade to AGP 9 | Moving a project to Android Gradle Plugin 9 |
| UI | Migrate to Compose | Replacing view-based screens with Jetpack Compose |
| Performance | Audit R8 configuration | Reviewing shrinking and optimization rules |
| Navigation | Set up Navigation 3 | Following current best practices for app navigation |
| Play Store | Audit Play policy compliance | Checking permissions, account deletion and data safety |
| Wearables and XR | Wear OS with Compose, display glasses | Building for watches and projected XR devices |
The full list on Google’s browse page is longer. It also includes AppFunctions, CameraX, Media3 Cast and an on-device Gemini Nano prompt skill.
How to install Android skills with the Android CLI
Google recommends the Android CLI because it works with any agent. These two commands cover most people.
android skills list
android skills add r8-analyzer --project=.The first command shows what’s available. The second installs one skill into your current project. To grab everything for every agent it detects, run android skills add --all, and use android skills update --all later to refresh them.
Prefer plugins? The repo lists /plugin install android-skills --marketplace android/skills for Claude Code. Codex has its own marketplace commands. In Android Studio, you can download a skill and import it into your project, then call it by typing @skill-name in chat.
If you’re already running agents in your workflow, our look at Claude Code 2.1.302 changes covers a recent settings shift worth checking first.
Can you write your own Android skills?
Yes, and this is the part teams will like. Put a folder in .skills/ or .agent/skills/ at your project root, with a SKILL.md inside. The file starts with a name and a description, then your instructions.
Google gives a few limits. The name can be up to 64 characters, lowercase with hyphens. The description tops out at 1,024 characters. Aim for roughly 10,000 to 20,000 characters in the body, and move longer material into scripts/, references/ or assets/ folders.
One catch: if you tweak an official skill, rename it first. Otherwise android skills add will overwrite your edits on the next update.
Are Android skills safe to trust blindly?
No. They improve what an agent starts from, but they don’t replace review. Agents still make mistakes, and a skill can’t see your codebase’s quirks.
Treat the output like a pull request from a new teammate. Run your tests, read the diff, and be extra careful with security and billing changes. If you’re curious how AI-assisted code fixes work on the security side, see our piece on GitHub Agentic Autofix.
Frequently Asked Questions
What are Android skills?
They’re markdown instruction files, published by Google, that guide AI agents through Android tasks like Compose migrations or R8 audits.
Do I need Android Studio to use them?
No. The Android CLI works with any agent that supports the agent skills standard. Android Studio is an alternative path, where you import a skill manually.
Which AI agents work with Android skills?
The repo documents Claude Code and Codex plugin installs, plus Gemini and Antigravity defaults. Google’s docs say any tool following the agent skills standard can use them.
Are Android skills free?
Yes. The repository uses the Apache License 2.0.
My take: if you build Android apps with any AI agent, install two or three skills for the work you do most, such as Compose migration or the R8 audit. They cost nothing and take a minute. Just don’t expect them to replace testing and code review.
Leave a Reply