Who it is forDeveloper who already uses Claude Code and wants Android Skills available without installing them project by project.
The problemSetting up Skills by hand for each project takes extra steps when the agent is already the main coding tool.
The outcomeThe android-skills plugin is installed in Claude Code, so relevant Android Skills activate during normal work.
What you need first
- Android CLI, documented at developer.android.com/tools/agents/android-cli
- An AI agent that reads skills, such as Claude Code, Codex, or Gemini
- An Android project to work on
Steps
- Open Claude Code.
- Run
/plugin marketplace add android/skills. - Run
/plugin install android-skills@android-skills. - Ask Claude Code for an Android task, such as: Make my app UI edge-to-edge.
- Check that the agent's reply follows the Android guidance and review the changes it makes.
Prompt for your agent
In Claude Code, add the android/skills marketplace and install the android-skills plugin, then ask it to make the UI of the Android project at <project path> edge-to-edge. Report the files changed. Verify by checking that the plugin appears as installed before the task starts.
Caveat. The README says public contributions are not accepted, so feedback and skill requests go through GitHub issues only.
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page