using-android-skills

Routes Google Android product and migration workflows to android/skills leaf names.

1|Updated Aug 26, 2026
One-click install
npx skills add https://github.com/edivad1999/stuc-stack --skill using-android-skills-edivad1999
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: using-android-skills
Source: https://github.com/edivad1999/stuc-stack/tree/main/skills/using-android-skills
Command: npx skills add https://github.com/edivad1999/stuc-stack --skill using-android-skills-edivad1999

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents underperform on Google-specific Android workflows such as AGP 9 upgrades, Navigation 3 migration, edge-to-edge insets, R8 keep rules, and Play policy audits, and often answer from memory instead of using the official android/skills guidance. ## Core Features & Use Cases - Workflow Routing: Maps task signals (CameraX, Navigation 3, edge-to-edge, Play Billing, R8, testing-setup, and more) to the correct android/skills leaf name via a lookup table. - Fail-Closed Behavior: Stops and instructs the user to run android init and android skills add --all when a required upstream skill is not installed, instead of pasting remembered procedures. - Stuc Overlays: Adds project-specific rules on top of official workflows, such as following the repo's existing Compose architecture and screenshot test tasks. - Use Case: When asked to migrate an app to Navigation 3, the agent loads the navigation-3 skill from android/skills rather than improvising a migration plan. ## Quick Start Ask the agent to handle a Google Android workflow such as upgrading to AGP 9 or adding edge-to-edge insets, and it will route to the matching android/skills leaf.

Frequently Asked Questions about using-android-skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route Android migration tasks to official Google skills?▼

Describe the task signal, such as AGP 9 upgrade or Navigation 3 migration, and the routing table maps it to the matching android/skills leaf name like agp-9-upgrade or navigation-3. The agent then loads that upstream skill instead of improvising.

What Android workflows does android/skills cover?▼

Covered workflows include AGP 9 upgrades, CameraX, Navigation 3, edge-to-edge insets, R8 keep rules, Play Billing upgrades, Play policy audits, Media3 Cast, adaptive UI, Wear Compose Material 3, and project testing setup.

What happens if the required android/skills leaf is not installed?▼

The skill fails closed: it stops and tells the user to run android init and android skills add --all (or android skills add --agent=codex --all for Codex). It never pastes a remembered Google procedure or vendors the skill.

When should I use android/skills versus chrisbanes Compose skills?▼

Use android/skills for Google product and migration workflows like AGP upgrades, Play integrations, and edge-to-edge. Use chrisbanes skills for everyday Compose and Kotlin design such as state, effects, performance, and component design.

Can I use a local alias if the HEAD skill name is missing?▼

Yes. If a HEAD leaf name is missing and only a local alias exists, such as camera1-to-camerax for camerax, use the alias and note it. Do not copy either skill file into the repository.