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.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin adb-opsThis skill uses the workspace's default tool permissions.
Quick health snapshot of the connected Android device(s).
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
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.