This skill is a specialization of the ctf-sandbox-orchestrator skill for challenges where the decisive path runs through an Android app’s live trust boundary. It starts with the manifest, exported components, deeplinks, native libraries and local storage, then picks the narrowest runtime boundary to observe.
The method keeps static evidence and dynamic traces together before any claim is made. The skill states that it runs only after the orchestrator has set sandbox assumptions.
What You Get
- A three-step workflow: static triage before hooks, hook the narrowest boundary, replay the accepted path
- A reference checklist of static targets and preferred hook boundaries such as signer, crypto helper, JNI bridge, keystore and WebView bridge
- Evidence guidance that pairs a static location with dynamic proof and the local state it depends on
- A hand-off rule to the broader crypto and mobile skill when transform recovery dominates
Common Use Cases
- Tracing how an Android app in a CTF builds and signs its requests
- Inspecting shared preferences, local databases and token storage in a lab APK
- Documenting the smallest hook set that reproduces an accepted server-side branch
What Makes It Unique
It focuses on the live trust boundary of the app and advises hooking the signer, crypto helper or JNI marshaling, with the user interface layer left alone. Its checklist names the common pitfalls: capturing a signed header without the plaintext that produced it, and ignoring local state such as prefs or keystore material.
Under The Hood
The skill is instruction text only: a SKILL.md, one reference checklist and an agent configuration file. It ships no scripts. The method itself involves decompiling and running an APK, using a hooking framework such as Frida, patching or re-signing the package, and sending requests to a server, so the agent’s own tools perform those actions in the sandbox the orchestrator set up. The skill does not fetch pages or call APIs on its own.