Agent skills for Grok Build

Skills for testing Android devices and emulators on Windows/OpenCode. Control devices using ADB, PowerShell, UIAutomator, and screenshots…

The object graph: what lives how long, what may depend on what, and when a wiring mistake is discovered.

Control and inspect a local Android emulator app through ADB, screenshots, Pillow-based image analysis, and optional desktop coordinate…

Images that arrive at runtime, fetched or picked or decoded: caching, sizing, cancellation, and what a picker actually hands back.

Java on Android without the language features Kotlin has: threading, equality, resource handling, and interoperating with Kotlin.

Android and Kotlin development patterns — Compose, architecture, coroutines,

The shape of the layer graph: which layers exist, which way dependencies point, and what each one may touch.

Talking to a server: client configuration, what comes back, what happens when it does not, and how a request is authorised.

Use to extract concrete numbers and slice-level evidence from a `.perfetto-trace` captured by `android-perfetto-capture`.

Use to capture Perfetto system traces from a connected Android device — the input for any timing, threading, jank, or "is this on the main…

Use INSTEAD of git bisect when investigating a regression between two refs (releases, branches, "it worked yesterday") — especially when…

Use BEFORE fixing any non-trivial bug. Write a test that fails because of the bug, watch it fail, then fix the bug until the test passes…

Guides the end-to-end workflow for decompiling, analyzing, modifying, and reconstructing Android APK packages.

Use to flip framework-level diagnostics without code changes — verbose framework logging (`log.tag.<Tag> VERBOSE`), view-bounds overlay…

Keeping a secret on a device you do not control: key storage, backup, intents, and client-side checks that are signals rather than controls.

Use to prove (or disprove) that a state actually changed between two points — "did the dialog dismiss?", "did this navigation actually…

Use to surface invisible main-thread I/O, leaked closeables, leaked activities, and other policy violations that don't crash but cause…

What makes a test able to fail for the right reason: the shape of the seam, the scheduler it runs on, and what an assertion is allowed to…

Use to answer questions logging can't — "did this run, on what thread, for how long, in what overlap with frame boundaries?" Wrap suspect…

XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.

Automated end-to-end UI testing and verification on an Android Emulator using ADB.