device-status

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.

Ir para a instalação

Repositório: danielrosehill/Claude-ADB-Ops-Plugin
Última atividade na origem: 21 de abril de 2026 às 11:44
Idioma detectado do SKILL.md: inglês
Estrelas: 1
Forks: 0

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/danielrosehill/Claude-ADB-Ops-Plugin --skill device-status

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

onboard

First-run onboarding for the adb-ops plugin. Interview the user about the Android device connected via ADB — model, Android version, rooted status — then collect folder mappings (phone path to local path, with labels and use cases). Writes profile and mappings to the adb-ops workspace at <workspace>/. Use this before any other adb-ops skill, or whenever the user wants to add a new phone folder mapping.

2026-04-27

bloatware-log

View, search, and summarise the bloatware operations log at <workspace>/bloatware-log.jsonl. Use when the user asks "what bloatware did I remove", "show my debloat history", "what did I disable on this phone", or wants to audit past package operations before restoring something.

2026-04-21

import-media

Import media (photos, videos, voice memos, downloads) from the connected Android device to the local computer using saved mappings from <workspace>/mappings.yaml. Supports "import new since last run" (incremental) or full sync. Use when the user says "import my photos", "pull new videos from my phone", or references a mapping label like "import camera-photos".

2026-04-21

Ver todas deste repositório

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.

adb-ops: device-status

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

Procedure

Run adb devices -l. If no devices, tell the user to plug in the phone and authorise USB debugging.
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
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").
Report as a compact table. If multiple devices are connected, remind the user to pass -s <serial> to downstream skills.

device-status

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

Mais deste repositório

adb-ops: device-status

Procedure

adb-ops: device-status

Procedure