Stats
Actions
Tags
From adb-ops
Report the status of Android devices connected via ADB — serial, manufacturer, model, Android version, battery, storage, and whether the device matches the onboarded profile in <workspace>/profile.yaml. Use when the user asks "is my phone connected", "what phone is this", or before any other adb-ops operation to confirm the right device is in scope.
How this skill is triggered — by the user, by Claude, or both
Slash command
/adb-ops:device-statusThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Quick health snapshot of the connected Android device(s).
Quick health snapshot of the connected Android device(s).
Run adb devices -l. If no devices, tell the user to plug in the phone and authorise USB debugging.
For each device, collect:
adb -s <serial> shell dumpsys battery | grep -E 'level|status|temperature'adb -s <serial> shell df -h /sdcardadb -s <serial> shell uptimeCross-reference with <workspace>/profile.yaml (if present). Flag mismatches (e.g. different serial than onboarded — "this is a different phone than the one you onboarded").
Report as a compact table. If multiple devices are connected, remind the user to pass -s <serial> to downstream skills.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin adb-ops