android-gesture
Skill29 starsChanged 8 months agoMITView on GitHub
Perform Android gestures through ./tools/android input commands.
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-installSkill
- android-navigateSkill
- android-screenshotSkill
- android-scrollSkill
- androidSkill
- android-tapSkill
- android-testSkill
- android-uiSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
If the user names an element instead of coordinates, resolve it first with ui find or input tap-element.
- Very specific: line 17
After the gesture, verify with ui dump or screenshot.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Map requests to command-layer actions:
- tap:
input tap - long press:
input swipefrom a point to itself with a long duration - swipe / drag:
input swipe - double tap: run two
input tapcommands in sequence and then verify
If the user names an element instead of coordinates, resolve it first with ui find or input tap-element.
After the gesture, verify with ui dump or screenshot.
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.

