Developer Tools & Repos Agent Skills for OpenAI Agents SDK

Suede Labs Android app factory: plan, build, test, and release a production-grade native Android app from a product idea through Google…

Use this skill when the user wants to: - Control Android devices, emulators, or simulators - Perform mobile testing, QA automation, or UI…

Enforces Android Automotive OS (AAOS) best practices and architectural patterns for high-quality embedded vehicle applications.

Use when diagnosing an Android app problem (crash, misbehavior, UI anomaly) — reproduces the symptom on a device, gathers an evidence…

Use to find stuck coroutines, leaked jobs, and suspended awaits with no resumer — the concurrency bugs that don't crash but cause hangs…

Use to flush out intermittent crashes and ANRs ("it crashes sometimes," "fails on slow devices," "happens after rotation a few times") by…

Use when the user asks for an Android app, Compose UI, Material 3, Material You, Material 3 Expressive, Pixel-style app, foldable/adaptive…

Create production-quality Android app features.

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

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

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 this skill when capturing or analyzing Android Perfetto traces for app startup, UI jank, freezes, memory, CPU scheduling, binder IPC…

Use when you need empirical proof a code path actually executed — branch entries, callback fires, coroutine continuations, suspect early…

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…

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

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…

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.