adb-ui-tree

Automates Android UI-tree debugging via ADB. Use when an app blocks UI inspection or accessibility nodes are missing; collects uiautomator dumps, focused window info, and logcat hierarchy dumps for analysis.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "adb-ui-tree" with this command: npx skills add pratos/clanker-setup/pratos-clanker-setup-adb-ui-tree

ADB UI Tree Debugging Skill

Activation

When this skill is triggered, ALWAYS display this banner first:

╭─────────────────────────────────────────────────────────────╮
│  📱 SKILL ACTIVATED: adb-ui-tree                            │
├─────────────────────────────────────────────────────────────┤
│  Target: [app/screen being inspected]                       │
│  Action: Collecting UI hierarchy via ADB...                 │
│  Output: ui.xml, screen.png, accessibility logs             │
╰─────────────────────────────────────────────────────────────╯

Use this skill when you need to inspect Android UI trees, especially when an app blocks normal debugging/inspection. It provides a repeatable, automatic flow to collect UI hierarchy data, focused window info, and accessibility logs.

Preconditions

  • ADB is installed and available.
  • A device is connected and authorized (adb devices).
  • The target app is open on screen.

Steps

  1. Verify device connectivity
adb devices

If multiple devices are attached, use -s <serial> for all commands.

  1. Confirm focused window
adb shell dumpsys window windows | grep -E "mCurrentFocus|mFocusedApp"

Ensure the focused app is the target (e.g., iSmart).

  1. Try UIAutomator dump (may be blocked)
adb shell uiautomator dump /sdcard/ui.xml
adb pull /sdcard/ui.xml .

If the app blocks the dump, note the error and continue to step 4.

  1. Collect accessibility hierarchy logs If the project includes a custom AccessibilityService that logs a hierarchy dump, trigger the automation and capture logcat:
adb logcat -s BatteryTrackerA11y

Save the output for analysis.

  1. Capture a screenshot for manual inspection
adb exec-out screencap -p > screen.png

Use the screenshot to verify UI state and map coordinates if needed.

Notes / Fallbacks

  • If the app exposes no accessibility nodes, consider coordinate-based taps as a fallback.
  • If uiautomator dump is prohibited by the app, rely on AccessibilityService logs and screenshots.

Output to share

  • ui.xml (if available)
  • adb logcat -s BatteryTrackerA11y output
  • screen.png

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Research

competitive analysis

Provides a systematic competitive analysis framework based on Zhang Zaiwang's methodology, guiding goal-driven, structured market and product competitor eval...

Registry SourceRecently Updated
Research

test

Contract clause analysis, risk flagging, renewal tracking, and obligation extraction for business agreements. Use when you need to review vendor contracts, s...

Registry SourceRecently Updated
Research

clawlens

Analyze OpenClaw conversation history and generate a deep usage insights report covering usage stats, task classification, friction analysis, skills ecosyste...

Registry SourceRecently Updated
Research

ClawInsight

Earn rewards by helping brands understand consumers. With your explicit consent, contributes anonymized market research data through natural conversation and...

Registry SourceRecently Updated
230Profile unavailable