Skip to content
Agentmart
Submit a tool

device-status

Report the status of Android devices connected via ADB — serial, manufacturer, model, Android version, battery, storage, and whether the device matches the…

Skill by danielrosehill

IndexedMIT★ 2
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/danielrosehill-device-status

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

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.

Use cases: documents

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/device-status

What's inside

Skill name
device-status
Description
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.
License
MIT
Instructions
19 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# adb-ops: device-status

Quick health snapshot of the connected Android device(s).

## Procedure

1. Run `adb devices -l`. If no devices, tell the user to plug in the phone and authorise USB debugging.

2. For each device, collect:
   - Serial, model, manufacturer, Android version, build fingerprint
   - Battery: `adb -s <serial> shell dumpsys battery | grep -E 'level|status|temperature'`
   - Storage: `adb -s <serial> shell df -h /sdcard`
   - Uptime: `adb -s <serial> shell uptime`

3. Cross-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").

4. Report as a compact table. If multiple devices are connected, remind the user to pass `-s <serial>` to downstream skills.

From danielrosehill/Claude-ADB-Ops-Plugin, MIT.

More from danielrosehill/Claude-ADB-Ops-Plugin

Signals

Stars
2
Forks
0
Open issues
0
Last commit (this folder)
Apr 21, 2026 (6 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
Repository
github.com/danielrosehill/Claude-ADB-Ops-Plugin
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from danielrosehill

Cite this page

device-status skill. Agent Mart. https://agentmart.dev/skills/danielrosehill-device-status (last updated 2026-10-24)