software-android-runtime-debugging

Pass

Audited by Gen Agent Trust Hub on Oct 6, 2026

Risk Level: SAFEINDIRECT_PROMPT_INJECTIONEXTERNAL_DOWNLOADSCOMMAND_EXECUTION
Full Analysis
  • [SAFE]: The skill provides legitimate instructions for native Android application debugging, including build verification, install/launch loops, and performance triage. All recommended tools and practices align with standard industry procedures for Android development.
  • [INDIRECT_PROMPT_INJECTION]: The skill establishes an attack surface for indirect prompt injection by instructing the agent to ingest and analyze untrusted data from the local environment.
  • Ingestion points: Project configuration files (e.g., build.gradle.kts, AndroidManifest.xml, libs.versions.toml) and runtime output from adb logcat and adb shell commands, as described in SKILL.md and references/stale-build-triage.md.
  • Boundary markers: No explicit delimiters or instructions are provided to the agent to treat external data as untrusted or to ignore embedded instructions within logs or source code.
  • Capability inventory: The skill utilizes powerful CLI tools including adb (for shell access, package management, and device control) and gradlew (for building, cleaning, and executing arbitrary build tasks), which are present in SKILL.md, references/runtime-proof-loop.md, and references/gradle-build-troubleshooting.md.
  • Sanitization: There are no instructions for sanitizing or escaping content retrieved from project files or logs before processing.
  • [EXTERNAL_DOWNLOADS]: The skill contains numerous references to external documentation and performance tools. These references target trusted and well-known services including Google's Android Developer portal (developer.android.com), official Gradle documentation (docs.gradle.org), and established open-source tools like Perfetto (perfetto.dev) and LeakCanary (square.github.io). These references are documented neutrally and pose no security concern.
  • [COMMAND_EXECUTION]: The skill makes extensive use of local command-line tools such as adb, ./gradlew, and aapt2 to perform its debugging functions. These commands are standard for the Android development ecosystem and are used in accordance with their intended purposes.
Audit Metadata
Risk Level
SAFE
Analyzed
Oct 6, 2026, 02:03 PM