agentleFS
amit-nayaramit-nayar/android-adb-skill/AGENTS.md

android-adb-skill

AGENTS.md29 starsChanged 8 months agoMITView on GitHub

Use the local command layer first: Read docs/command-contract.md for the supported commands and output conventions. Read the relevant skills/*/SKILL.md file for task-specific workflow guidance.

The file

We split this AGENTS.md into the rules it gives an agent

6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the local command layer first:

    line 3
  2. Very specific:

    Read docs/command-contract.md for the supported commands and output conventions.

    line 9
  3. Very specific:

    Prefer ./tools/android ...

    line 13
  4. Very specific:

    If multiple devices are connected, pass --device <id> or stop and ask the user to choose.

    line 14
  5. Very specific:

    Verify state after each interaction with ui dump, wait element, or screenshot.

    line 15
  6. Very specific:

    Use raw adb only when the command layer does not support the required operation.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Android Automation

Use the local command layer first:

./tools/android ...

Read docs/command-contract.md for the supported commands and output conventions. Read the relevant skills/*/SKILL.md file for task-specific workflow guidance.

Default Behavior

  • Prefer ./tools/android ... --json over raw adb.
  • If multiple devices are connected, pass --device <id> or stop and ask the user to choose.
  • Verify state after each interaction with ui dump, wait element, or screenshot.
  • Use raw adb only when the command layer does not support the required operation.

Skill Entry Points

  • skills/android/SKILL.md — General orchestration
  • skills/android-screenshot/SKILL.md — Screenshots
  • skills/android-ui/SKILL.md — UI inspection
  • skills/android-tap/SKILL.md — Element tapping
  • skills/android-navigate/SKILL.md — Navigation
  • skills/android-scroll/SKILL.md — Scrolling
  • skills/android-gesture/SKILL.md — Gestures
  • skills/android-test/SKILL.md — Test flows
  • skills/android-debug/SKILL.md — Debugging
  • skills/android-install/SKILL.md — APK installation
  • skills/android-device/SKILL.md — Device management

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.