Published: 2026-10-10
Summary

Google's Android skills for coding agents: the install commands, writing your own SKILL.md, and which new claims we could not confirm

Chapters / key moments (click to jump — plays here on the page)

Google publishes "Android skills": instructions in the open agent-skills format that hand a coding agent current Android guidance instead of leaving it to guess from older training data. This video, from a channel that uses an AI avatar and ends with community pitches, walks through the install commands, how skills get picked up, the rules for writing your own, two newly announced skills, remote-device testing and an Android Bench ranking. We checked each part against Google's own pages; the page below says which parts held up.

Source video

"Google Just Gave AI Agents New Android Skills" by Julian Goldie SEO — Watch on YouTube →

Confirmed in Google's own pages

These match Google's Android skills documentation and the android/skills repository (Apache 2.0; public contributions aren't accepted at this time):

android skills list                              # see what is available
android skills add <skill-name>                   # install; re-running updates it
android skills add --all                         # all skills for detected agents
android skills update --all                      # update everything
android skills add r8-analyzer --project=.       # one skill into one project

Options documented in the repository: --all, --agent (comma-separated list of agents) and --project (project root). The video writes the command as android-skills add --all with a hyphen; the documented form has a space.
Invoking. The agent activates relevant skills automatically; you just ask ("make my app UI edge-to-edge"). In Android Studio you can also type @skill-name in the chat window to call one directly.
Customising. Google says to rename a skill you customise, or it is overwritten when you update it with skills add.
Writing your own. The agent looks in .skills/ or .agent/skills/ at the project root. Create a directory, then a SKILL.md file (case-sensitive) with front matter containing name (up to 64 characters: lowercase letters, numbers and hyphens, matching the directory name) and description (up to 1,024 characters, saying what it does and when to use it). Aim for about 10,000 to 20,000 characters of body, roughly 2,500 to 5,000 tokens. Optional scripts/, references/ and assets/ folders hold code, detailed docs and templates.
Examples Google gives: migrating from XML to Compose, upgrading to AGP 9, setting up Navigation 3, making an app edge-to-edge, and auditing R8 configuration.

Reported in the video, not confirmed by the pages we checked

Two new skills: "audit Play policy compliance" (the video says it checks permissions, account deletion and data safety, plus the manifest, runtime permissions, target SDK level and privacy disclosures) and "use Android profilers" (record and analyse traces and find jank and memory leaks, turning plain-English questions into Perfetto SQL). The repository lists folders named play and android-profiler, which fits, but Google's skills documentation page doesn't describe either skill. The video itself notes Google says AI can make mistakes, so treat an audit as a checklist to review, not a verdict.
Android device streaming in the Android CLI: reserving a real remote device so the agent can deploy a build, collect logs and traces and take screenshots, with commands the video gives as android device remote models and android device remote create. We found no official documentation of these commands, so verify them in your installed CLI first.
Android Bench ranking (as of October 6, per the video): Claude Opus 5.5 in Claude Code at a 32.7% pass rate on a 30-task long-horizon set, GPT-6 Astra in Codex 28%, Claude Fable 5.1 22.7%. We couldn't match these to a Google page, and coverage we found of earlier Android Bench updates reported different leaders and scoring, so use Google's own leaderboard.

Gotchas & Caveats

The video is promotional in places (community and course pitches, repeated); none of that is part of the setup.
Where an android command isn't on your machine, the Android CLI has to be installed first; the video doesn't show that step, so follow Google's CLI documentation.
A skill is read by an agent with whatever permissions you've given it. Review third-party skills before enabling them, as with any skill.
Without a named agent and no existing agent directories, the repository's README says skills install for Gemini and Antigravity; pass --agent if you use something else.

Key Takeaways

Install with android skills add <name> or --all, then just describe the task.
Your own Android skill is a SKILL.md in .skills/ with a short name, a "what and when" description and detail in references/.
Rename any skill you edit, or the next update replaces it.
Treat the new Play-policy and profiler skills, device streaming commands and benchmark numbers as unconfirmed until they appear in Google's docs.