debugging

Capture UI states and inspect element hierarchies to debug automated processes.

198|40|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/SelectXn00b/AndroidForClaw --skill debugging-selectxn00b
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/SelectXn00b/AndroidForClaw/tree/main/app/src/main/assets/skills/debugging
Command: npx skills add https://github.com/SelectXn00b/AndroidForClaw --skill debugging-selectxn00b

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive set of tools and strategies to diagnose failures, locate bugs, reproduce problems, and verify fixes in an automated environment.

Core Features & Use Cases

  • Diagnose Failures: Understand why operations are not working as expected.
  • Locate Bugs: Pinpoint the root cause of issues within a workflow.
  • Reproduce Problems: Reliably trigger and document issues for analysis.
  • Verify Fixes: Confirm that resolved problems are indeed fixed.
  • Use Case: When an AI agent fails to tap a specific button, this skill can capture screenshots, inspect the UI tree, and systematically test potential causes like incorrect coordinates or elements being off-screen, guiding the AI to the solution.

Quick Start

Use the debugging skill to capture a screenshot and log the current state of the application.

Frequently Asked Questions about debugging

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

FAQPage Schema
How do I troubleshoot automated processes when an element is not found or an operation has no response?

Troubleshoot automated processes by capturing UI states, inspecting element hierarchies, and logging execution flow to identify why elements are missing or operations become unresponsive. This captures the exact UI state to reveal root causes like incorrect coordinates or off-screen elements.

What is the best way to isolate the root cause of intermittent failures and app crashes in automated workflows?

Isolate root causes of intermittent failures and app crashes using comparison debugging and binary search techniques. This approach systematically narrows down execution flow logs to pinpoint the exact trigger and verify the solution.

How do I debug an AI agent that fails to tap a specific button during test execution?

Debug an AI agent failing to tap a button by capturing screenshots and inspecting the UI tree to systematically test potential causes. This identifies whether the failure stems from incorrect coordinates, element visibility, or hierarchy issues.

How can I reliably reproduce problems and verify fixes in an automated testing environment?

Reliably reproduce problems and verify fixes by capturing UI states and logging execution flow to document issues for analysis. This ensures that resolved problems are genuinely fixed by providing consistent, verifiable execution traces.

Does this debugging approach require specific dependencies to diagnose failures and locate bugs?

Diagnosing failures and locating bugs requires no external dependencies, relying entirely on internal scripts and references. This allows immediate integration into automated workflows to capture screenshots, inspect hierarchies, and log execution flow.

Why should I use systematic problem isolation instead of manual inspection for automated testing errors?

Systematic problem isolation replaces manual inspection by applying binary search and comparison debugging to identify root causes precisely. This reduces guesswork when addressing element not found errors, no response operations, and app crashes.