ad-investigate

Triage Android debugging goals and dispatch to matching ad-* templates.

3|Updated May 10, 2026
One-click install
npx skills add https://github.com/Acendas/android-debugger --skill ad-investigate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ad-investigate
Source: https://github.com/Acendas/android-debugger/tree/main/skills/ad-investigate
Command: npx skills add https://github.com/Acendas/android-debugger --skill ad-investigate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Triages Android debugging goals and routes them to the appropriate plan template to reduce manual debugging guesswork and rework.

Core Features & Use Cases

  • Goal triage: classify user intent into one of the predefined shapes.
  • Plan dispatch: select and submit the matching ad-* template (ad-catch, ad-trace, ad-walk, ad-bisect-flaky).
  • Plan monitoring: stream plan_progress events, handle yielded, aborted, or completed outcomes, and re-author when needed.
  • Escape hatches: fall back to interactive frame_snapshot/evaluate when automation cannot proceed.

Quick Start

Dispatch to the matching ad-* template and monitor plan_progress until completion.

Frequently Asked Questions about ad-investigate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Android bug investigation end-to-end?

Plan-driven Android bug investigation triages your debugging goals and dispatches them to matching template skills like ad-catch, ad-trace, ad-walk, or ad-bisect-flaky. It monitors execution progress and handles abort or reauthor loops automatically.

What is the best way to triage Android debugging goals automatically?

Automated triage classifies user intent into predefined shapes and submits the matching ad-* template to a server-driven plan engine. This approach reduces manual debugging guesswork by routing issues to deterministic plan execution.

How does plan monitoring work for Android debugging orchestration?

Plan monitoring streams plan_progress events to track yielded, aborted, or completed outcomes during template execution. It automatically handles re-authoring loops and escalates when the automation cannot proceed deterministically.

Can I use interactive debugging when plan automation cannot proceed?

Yes, you can use interactive escape hatches like frame_snapshot and evaluate when plan automation cannot proceed. These fallbacks allow manual intervention during Android debugging orchestration when templates yield or abort unexpectedly.

Do I need template skills to run Android debugger orchestration?

Yes, Android debugger orchestration relies on template skills like ad-catch, ad-trace, ad-walk, and ad-bisect-flaky alongside a server-driven plan engine. These dependencies are required to dispatch and monitor deterministic debugging plans.

Why does automated Android debugging use plan dispatch templates?

Automated Android debugging uses plan dispatch templates to reduce manual debugging guesswork and rework. Templates provide deterministic execution by routing triaged goals to predefined shapes like ad-catch, ad-trace, or ad-bisect-flaky.