Skip to main content
Guide9 min read·Updated August 1, 2026
🧩

Best AI Agent Skills for Android Developers (2026)

B

A. Frans

Published August 1, 2026

AndroidKotlinAgent SkillsClaude CodeMobile Development

The most-starred Android agent skill on GitHub is not for building Android apps. It's for taking them apart.

SimoneAvogadro/android-reverse-engineering-skill sits at 6,601 stars. The most-starred skill for writing Android code has 300, hasn't been touched since December 2025, and its own README still opens with a "[WIP]" tag.

Compare that to Apple's side of the fence. Paul Hudson's SwiftUI Agent Skill is at 4,392 stars, Antoine van der Lee's competing SwiftUI skill at 3,350, his Swift Concurrency skill at 1,606, all three actively maintained. iOS developers have a deep bench of authored, opinionated skills from named experts. Android developers have a reverse-engineering tool, two forensics MCP servers, and a handful of small repos doing good work with almost no attention.

That gap is the story of this category in 2026, and it changes what you should install. Every star count and install command below was pulled from the GitHub API and each project's own README on August 1, 2026, not from a directory listing.

Every Android skill worth knowing about, verified

ProjectStarsLast pushWhat it isType
android-reverse-engineering-skill6,6012026-06-10APK decompilation and analysis workflowSkill
mobile-mcp5,7262026-07-12Device automation across iOS and AndroidMCP server
awesome-android-agent-skills9082026-07-27Multi-agent Android skill collectionSkill collection
android-mcp-server7892025-05-28adb control surface for the agentMCP server
apktool-mcp-server6142026-07-02APK Tool wrapper for RE workMCP server
claude-android-skill3002025-12-07Clean architecture and Compose patternsSkill (WIP)
android-skills1162026-07-28Android and KMP practice skillsSkill plugin
claude-android-ninja1012026-07-26Kotlin and Jetpack Compose guidanceSkill
kmp-compose-multiplatform-skill692026-03-20KMP plus Compose MultiplatformSkill
kotlin-kmp-claude-agent-skills582026-04-10KMP skills from official docsSkill
Read that table by the "last push" column rather than by stars and the ranking inverts. The two freshest repos are the two smallest.

If you write Android apps for a living, android-skills is the first install. It was pushed three days before this article went up, it covers Android and Kotlin Multiplatform together, and its skill descriptions read like they were written by someone who has been bitten by the things they describe. The Ktor skill, for one, documents plugin install order, that HttpRequestRetry has to go in before HttpTimeout, and the vanishing-constant trap when encodeDefaults is left off. That is not the kind of detail you get from a model summarising the docs.

Install it as a Claude Code plugin:

  • /plugin marketplace add rcosteira79/android-skills
  • /plugin install android-skills@android-skills

GitHub Copilot users have a direct path too, "copilot plugin install rcosteira79/android-skills". If you'd rather not go through a marketplace, clone and copy the skill folders into your personal skills directory:

  • git clone https://github.com/rcosteira79/android-skills.git
  • cp -r android-skills/plugins/android-skills/skills/* ~/.claude/skills/

The 116 stars are not a quality signal here. They're a discovery problem. Android skill repos surface poorly because the search terms are dominated by reverse-engineering tooling.

claude-android-ninja for Compose-heavy work

Drjacky/claude-android-ninja targets Kotlin and Jetpack Compose specifically, and it's the one repo here that took multi-agent portability seriously. Its README maps the install path for each agent's native skills directory rather than assuming everyone is on Claude Code.

Recommended install goes through the Vercel skills CLI, which auto-detects your installed agents:

  • npx skills add drjacky/claude-android-ninja

Manual install, if you want to see what lands on disk first:

  • git clone https://github.com/Drjacky/claude-android-ninja.git
  • mkdir -p ~/.claude/skills
  • cp -r claude-android-ninja ~/.claude/skills/claude-android-ninja

Read the SKILL.md before you install either of these. That advice applies to every third-party skill and Paul Hudson makes the point bluntly in his own Swift skill directory: being listed somewhere is not an endorsement. A skill is instructions your agent will follow with your credentials in your repo.

The 300-star trap

dpconde/claude-android-skill shows up first in most searches for "Claude Code Android skill," and on paper it's exactly what you want: clean architecture layers, Compose patterns, multi-module Gradle, Hilt, offline-first with Room, all grounded in Google's NowInAndroid reference app.

It was last pushed on December 7, 2025. Nearly eight months stale, in a toolchain that ships breaking changes on a quarterly cadence, with "[WIP]" still in the title. Its install instructions are also incomplete: the README says to clone the repo into your skills directory but the command it gives is a bare git clone with no destination, so it lands in whatever directory you happened to be in.

The architecture guidance inside it hasn't rotted, and NowInAndroid is still the right reference. But install it knowing you're getting a snapshot of late-2025 practice, and put the fresher repos ahead of it in your skill precedence.

Reverse engineering is where Android agent tooling leads

The security side of Android is the one place where the tooling beats iOS outright, and it's worth understanding why the star counts look the way they do.

android-reverse-engineering-skill drives APK decompilation and analysis as an agent workflow. Install it with:

  • /plugin marketplace add SimoneAvogadro/android-reverse-engineering-skill
  • /plugin install android-reverse-engineering@android-reverse-engineering-skill

apktool-mcp-server sits underneath as part of a wider Android RE suite, exposing APK Tool through MCP. It's Apache-2.0 and was pushed in July 2026.

Android is open enough that decompiling a shipped APK is straightforward, which makes it a natural fit for agent automation. iOS is not, which is why no equivalent iOS category exists. If your work is mobile app security rather than mobile app development, this is the strongest agent tooling available on either platform.

Both are dual-use. Point them at binaries you have permission to analyse.

Skills, MCP servers, and telling them apart

Three of the ten entries above are MCP servers, not skills, and directories, ours included, list them side by side without flagging the difference.

A skill is a markdown file of instructions that changes how the agent thinks about a problem. An MCP server is a running process that gives the agent new tools to call. You install them differently, they fail differently, and one cannot substitute for the other.

For Android that split is clean. android-mcp-server gives your agent adb control over a connected device. mobile-mcp does the same across iOS, Android, emulators and physical devices under Apache-2.0. Neither teaches the agent anything about Kotlin idiom or Compose recomposition. That's the skill's job.

Pair them. A skill for how to write the code, an MCP server so the agent can install the APK and drive the screen and see whether it worked. That build-and-observe loop is what separates a useful mobile agent setup from an expensive autocomplete, and it's covered in more depth in our mobile app development skills roundup.

One caveat on android-mcp-server: its last push was May 2025. It works, adb is stable, but it's unmaintained.

Kotlin Multiplatform has two small options

kmp-compose-multiplatform-skill at 69 stars and kotlin-kmp-claude-agent-skills at 58 both target KMP, the second grounded explicitly in official Android documentation. Both were last pushed in the first half of 2026.

Neither has enough usage behind it to recommend without reservation, and mmiani's carries a non-standard license, so check it against your employer's policy before it goes anywhere near a work repo. For most teams the KMP coverage inside rcosteira79/android-skills is the better starting point because it's maintained alongside the Android skills you already need.

If you also ship React Native

Expo Skills at 2,347 stars and Callstack's React Native skills at 1,574 are both actively maintained and both MIT. Expo's install goes through the official Claude Code plugin marketplace:

  • claude plugin install expo@claude-plugins-official

Or through the skills CLI for other agents, "npx skills@latest add expo/skills --skill '*'". Callstack's is a marketplace add plus per-skill installs, including one for upgrading React Native versions and one for brownfield migration, which is the least fun task in the category and the one most worth automating.

Cross-platform developers get better skill coverage than native Android developers right now. That's an odd state of affairs and it should correct, but it's where things stand.

A working setup

For native Android work, install rcosteira79/android-skills and claude-android-ninja, add mobile-mcp so the agent can drive a device, and keep dpconde's architecture skill around as reference rather than as an active instruction set. That's two skills and one server.

Resist stacking more. Skills load into context and overlapping guidance from four repos produces an agent that hedges instead of deciding. Claude Code resolves same-name skills by precedence, enterprise over personal over project, but it has no way to reconcile two skills that disagree about whether your ViewModel should expose a StateFlow. You'll get whichever one it read last.

If you want more on how skills, subagents and hooks fit together before you start layering them, we compared the three extension types. And for general engineering skills beyond mobile, our full list for developers covers the rest of the stack.

FAQ

Why are there so few Android agent skills compared to iOS? Best guess: the iOS community has a small number of very visible educators, Paul Hudson and Antoine van der Lee among them, who published skills early and brought their audiences with them. Android's expertise is more distributed across company engineering blogs, so nobody's skill repo inherited a following. The Android skills that exist are not lower quality, they're less discovered.

Is claude-android-skill still safe to use at eight months stale? The architecture guidance is fine. Clean architecture layering, offline-first with Room, and Hilt injection haven't changed. What's stale is anything touching current Gradle, AGP or Compose API surface. Use it for structural decisions and let a fresher skill handle the API specifics.

Do I need an MCP server, or is a skill enough? A skill alone can write code but can't verify it. Without adb access through something like android-mcp-server or mobile-mcp, the agent writes, you build, you report the error, and it guesses again. Adding device access closes that loop and it's the single biggest quality jump in a mobile agent setup.

Where do skills go on disk? Personal skills live at ~/.claude/skills/name/SKILL.md and apply to every project. Project skills live at .claude/skills/name/SKILL.md and apply to one repo. Plugin skills are namespaced as plugin-name:skill-name so they can't collide with either. When names clash, enterprise beats personal beats project.

Is the reverse-engineering skill legal to use? Analysing an APK you own or have written permission to test is standard security work. Decompiling a competitor's app to copy it, or to bypass licensing, is not, and the tool doesn't know the difference. The obligation is yours.

Share this article

📬

Get More AI Tool Guides

New comparisons and guides every week. Join thousands of professionals staying ahead of the AI curve.