AutoGOD Automation Assistant

Problem

AutoGOD and AIGame scripts span many APIs, including $act, $screen, $ocr, $floaty, $http, $file, and $thread, each with different signatures and permission requirements. Writing code from memory can easily introduce API name errors, wrong argument types, missing permissions, resource leaks, and async bugs, especially when behavior changes across ROOT, Shizuku, and Accessibility environments.

How It Works

This skill organizes AutoGOD standards, API references, code patterns, and error-correction notes into searchable material. Before generating code, it uses a structured workflow: read the relevant module documentation, run a mandatory checklist, generate code according to the standard API patterns, and review common errors. For $act gestures, it enforces the ROOT > Shizuku > Accessibility priority order. For OCR, it distinguishes the trade-offs between ncnn, mlkit, and ppv5 in speed and accuracy. For UI, floaty windows, networking, file operations, and concurrency, it prefers the module docs and examples under references/ over guessing call signatures.

Boundaries

It is useful for writing and reviewing AutoGOD Android automation scripts, including image recognition, text recognition, UI building, network requests, file operations, and multi-threaded tasks. Key caveats include calling $permit permission methods only once, avoiding the blocking getPermit() on the UI thread, accounting for MIUI restrictions on full-screen $draw, expecting empty or failed clipboard reads on Android 13+, and packaging APKs with $engine.run("project js path") instead of executing source-code strings directly.