device-status

Report Android device status via ADB and flag profile mismatches.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/danielrosehill/Claude-ADB-Ops-Plugin --skill device-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: device-status
Source: https://github.com/danielrosehill/Claude-ADB-Ops-Plugin/tree/main/skills/device-status
Command: npx skills add https://github.com/danielrosehill/Claude-ADB-Ops-Plugin --skill device-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Android devices connected via ADB can be hard to verify and coordinate for operations. This Skill provides a quick health snapshot, including identity and status details, to ensure you know which device is in scope before running subsequent commands.

Core Features & Use Cases

  • Collects and reports serial, manufacturer, model, Android version, battery, storage, and uptime for each connected device.
  • Flags mismatches with the onboarded profile in workspace/profile.yaml to prevent cross-device mistakes.
  • Outputs a compact table and, when multiple devices are connected, reminds you to pass -s <serial> to downstream skills for specificity.

Quick Start

Ask Claude to run the device-status skill after you connect and authorize the Android device.

Frequently Asked Questions about device-status

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

FAQPage Schema
How do I check the status of Android devices connected via ADB?

To check the status of Android devices connected via ADB, use this Skill to collect serial, manufacturer, model, Android version, battery, storage, and uptime data into a compact table. It verifies device health and flags mismatches with the onboarded profile.

How do I verify an Android device matches its onboarded profile before running commands?

Verify an Android device matches its onboarded profile by comparing live diagnostics against workspace/profile.yaml. This Skill flags mismatches in serial, model, and Android version to prevent cross-device mistakes before executing downstream operations.

What ADB device information do I need to collect for inventory diagnostics?

For ADB inventory diagnostics, this Skill collects device serial, manufacturer, model, Android version, battery level, storage capacity, and uptime. It outputs a compact table summarizing connected Android devices for quick health assessment.

How do I target a specific Android device when multiple are connected via ADB?

To target a specific Android device when multiple are connected via ADB, pass the -s <serial> flag to downstream skills. This Skill detects multiple connections and reminds you to use the serial identifier for command specificity.

Do I need to authorize my Android device before running ADB diagnostics?

Yes, you need to authorize your Android device before running ADB diagnostics. Connect the device, accept the ADB authorization prompt on screen, and then run the Skill to collect status details and verify health.

Why does my Android device profile mismatch when connected via ADB?

An Android device profile mismatch occurs when live diagnostics differ from the onboarded workspace/profile.yaml. This Skill detects discrepancies in serial, manufacturer, model, or Android version to prevent operating on the wrong device.