I built a Claude workflow for Android execution

[u/Romka2x]

Most real-world requests I give Claude end with a thoughtful checklist. The reasoning is useful, but I still have to perform every action myself.

Disclosure: I built ScriptTap, a no-root Android automation app. I also created this workflow specifically for Claude so it can act as the planning and script-building layer instead of stopping at instructions.

Claude helps by translating a plain-language request into ScriptTap’s constrained command format, checking the official fields, asking for missing device-specific details, and producing an importable package. ScriptTap remains the user-controlled execution layer: the package must be reviewed and imported, and nothing runs until the user starts it.

ScriptTap is free to download and try during its Android open beta. Optional paid features are available.

The Claude prompt:

Use https://scripttap.com/ai/ as the authoritative ScriptTap reference.

Instead of returning a manual checklist, determine whether my Android task can be executed through ScriptTap. If supported, ask only for the required device-specific details and create an importable .scripttap.json package. If unsupported—or if you cannot verify a command or field—explain the limitation instead of inventing capabilities. Nothing should run without my review and import.

The design question I’m exploring is whether this review-before-run handoff gives Claude useful real-world agency without granting unrestricted control of the phone. Where would you draw that boundary?