Skip to content
한국어
Contact us

Blog

Google has published more than 20 Android skills for coding agents. The repository gained 1,070 GitHub stars in a week. This post sets out what app teams should take from it.

Published

Korean version of this postView as Markdown

Google continues to expand its android/skills repository. It is a collection of SKILL.md files that break the official Android guidance into pieces a coding agent can read.

There are now more than 20 skills, covering Compose, navigation, performance, Play policy, testing, Wear and XR.

Tools that write code are no longer new. This development is different in kind. The tools are being given an account of how the platform works before they write a line.

Numbers first. android/skills gained 1,070 stars in a week on GitHub Trending (Kotlin), as of October 26, 2026.

The announcements follow. On September 24, Android Studio opened up to the coding agent of your choice. On October 2, Android CLI stated that it works with any agent, and agents can now reach real devices through Device Streaming.

There is also a trend line. Since skills arrived in Android Studio on September 1, I counted six agent-related posts on the official blog.

One smaller signal: sim-use, which lets an agent drive the iOS Simulator and Android emulators, appeared on Trending this week with 59 stars for the week. It remains small.

The Instagram Direct team described how it built an agent-friendly UI architecture with Jetpack Compose, in a September 30 post on the official blog.

  • The codebase came out 50% smaller than the original
  • Agent execution time dropped 35%
  • Engineer-agent exchanges fell 32%
  • Token cost per agent session came down 33%

These are the team's own figures. They do not promise the same results in another app.

A skill is a markdown file. Writing one is not difficult. Deciding what belongs in it is. How the app is structured, which libraries it avoids and how it is worded all have to be drawn out of the team's heads.

The official skills describe Android. Describing our own app is our job. Both are needed for the output to fit well.

Convention documents that once sat unused in a wiki become components that connect directly to a tool. If the document goes stale, the agent writes in the stale way too. Maintaining the document is part of the development.

On iOS, the sources I reviewed showed no comparable move this week. Tools such as sim-use are, however, trying to cover both kinds of device, so the direction is likely to be similar.

dsui also has a skill. SKILL.md sets out the order of work and the rules to follow, and six reference files accompany it: installation, tokens, copy and screen rules, sound and motion, components and a checklist.

When added to a tool such as Claude Code, it follows the same steps each time: find an item, install it, compose it according to the rules and check it against the checklist. It does not replace the component source, which is obtained separately.

Usage is described in the dsui skill documentation. More of our work is on the work page.

  • iPhone Duo reached customers on October 23. Apple explained how to rebuild with Xcode 27.1 and published Figma and Sketch design kits
  • Expo SDK 58 came out on October 15
  • Tauri v3 reached alpha 5 on October 14

Sources