Automates Android device management via dab CLI without interactive input.
npx skills add https://github.com/cesarferreira/dab --skill dab
Please help me install this Agent Skill. Skill: dab Source: https://github.com/cesarferreira/dab/tree/main Command: npx skills add https://github.com/cesarferreira/dab --skill dab
This Skill eliminates the need for manual interactive input when using the dab CLI, enabling AI agents to fully automate Android device management, app testing, and debugging tasks without human intervention.
Use the dab skill to install your app's debug build to the connected Android emulator, grant it camera and location permissions, and take a screenshot of the home screen for verification.
High-intent search queries and answers about installing and using this skill.
Automating Android device management requires structured CLI execution without interactive prompts. This Skill enables AI agents to run ADB operations, APK deployment, and permission auditing programmatically via JSON output, eliminating manual intervention in mobile development workflows.
Automating APK deployment and permission management is supported through pre-built patterns. You can programmatically install a debug APK to a connected emulator, grant required permissions like camera and location access, and capture screenshots for verification without manual steps.
USB debugging must be enabled on physical Android devices to run ADB operations. You also need the dab CLI tool installed in your system PATH, with a connected physical device or emulator ready to receive automated commands for app testing and device health monitoring.
Integrating ADB commands into CI/CD pipelines requires non-interactive device control with structured output. This Skill provides ready-to-use automation patterns for APK deployment, permission auditing, and device health checks, allowing automated workflows to execute ADB operations programmatically without human intervention.
Both physical Android devices and emulators are supported for automation tasks. Physical devices require USB debugging enabled and a wired connection, while emulators must be running and accessible via ADB, allowing the AI agent to manage app deployment and testing across either environment.
Automated ADB operations fail without a connected device because the CLI requires an active ADB target. Ensure the dab CLI is installed in your system PATH and that a physical device with USB debugging or a running emulator is properly connected before executing automation commands.
asnar00Build and deploy Android APKs to USB-connected devices via ADB.
FutureAtomsMonitor and manage GitHub check statuses for pull requests and commits.
owenlim225Consolidate project planning sections and specialized Claude Skills for lifecycle management.
hyperb1issAutomate Android device management and debugging via ADB and shell commands.
