android-tap

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 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.

• 4

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   Default to semantic tapping:

   line 8
2. Very specific:

   If the target is described by text, resource-id, or content description, run ./tools/android input tap-element ...

   line 10
3. Very specific:

   If the user gave coordinates, run ./tools/android input tap --x ...

   line 11
4. Very specific:

   After tapping, verify the result with ./tools/android ui dump --json or ./tools/android wait element ...

   line 12
5. Very specific:

   If the target is not visible, switch to android-scroll before falling back to raw coordinates.

   line 14

≈ “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.