android
Skill29 starsChanged 8 months agoMITView on GitHub
General-purpose Android automation. Use for multi-step Android tasks that should be executed through the local ./tools/android command layer instead of raw adb.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- Codename-11/hermes-relaytheir own version, first seen Nov 8, 2026
- lgzarturo/codeconductortheir own version, first seen Oct 18, 2026
- JetBrains/junie-extensionstheir own version, first seen Oct 13, 2026
- BrowserWorks/waterfox-androidtheir own version, first seen Oct 8, 2026
- Eclipse-Community/r3dfoxtheir own version, first seen Oct 8, 2026
- BrowserWorks/waterfoxtheir own version, first seen Oct 8, 2026
Used with
Projects with it also use accessibility-frontend-review, android-new-module and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
BrowserWorksSkillaccessibility-frontend-review
Performs an accessibility code review of a local diff or Phabricator revision in the style of the Firefox accessibility team. Use this skill whenever the user asks to review a Phabricator patch or revision for accessibility issues, mentions a D-number (like D284142) in the context of accessibility review, asks "does this patch have any a11y issues", or wants to check a diff against accessibility guidelines. Also use it when the user says things like "can you review this for a11y", "check this patch", or "give me an accessibility review of D[number]". Invoke proactively when the user pastes a phabricator.services.mozilla.com URL or shares a revision ID alongside any accessibility concern. Invoke when questions about the following topics are raised: aria properties, aria roles, high contrast mode, forced colors, prefers contrast, focus order, screen readers, assistive technology.
Also in 4 projects that use this
- BrowserWorksSkill
android-new-module
Guide for creating new Android gradle modules in the android-components project.
Also in 4 projects that use this
- +10 more from BrowserWorks
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- mozilla-firefox/firefox★ 14ksame name
- BrowserWorks/waterfox★ 6.4ksame name
- Codename-11/hermes-relay★ 432same name
- BrowserWorks/waterfox-android★ 393same name
- Eclipse-Community/r3dfox★ 347same name
- ayush016/android-lead-agent-skills★ 76same name
- JetBrains/junie-extensions★ 23same name
- ffsshhttiikk/opencode-agents-skills★ 2same name
- iadr-dev/colab★ 2same name
- hebertzhu/agent-foundry★ 0same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/android-adb.mdcCursor rule
- android-debugSkill
- android-deviceSkill
- android-gestureSkill
- android-installSkill
- android-navigateSkill
- android-screenshotSkill
- android-scrollSkill
- android-tapSkill
- android-testSkill
- android-uiSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use ./tools/android as the default execution layer.
- Distinctive: line 13
If multiple devices are attached and the user did not choose one, stop and ask.
- Very specific: line 22
Prefer --json and reason from structured output.
- Very specific: line 23
After every interaction, verify with ui dump, wait element, or screenshot.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Use ./tools/android as the default execution layer. Read docs/command-contract.md if you need the exact command surface.
Workflow:
- Start with
./tools/android device list --json. - If multiple devices are attached and the user did not choose one, stop and ask.
- Break the request into steps and route each step to the right command family:
- screenshots:
screenshot - UI inspection:
ui dump,ui find - interaction:
input ... - waits:
wait element - scrolling:
scroll find - app lifecycle:
app ... - logs:
debug ...
- screenshots:
- Prefer
--jsonand reason from structured output. - After every interaction, verify with
ui dump,wait element, orscreenshot.
Fallback to raw adb only if the command layer cannot do the required operation.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.