adb-ops

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.

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.

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".

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.

Pull an arbitrary folder (or single file) from the connected Android device to the local computer via `adb pull`. Unlike import-media this is ad-hoc — the user supplies the phone path and optional local destination. Use when the user wants "just grab /sdcard/<something>" that isn't in their saved mappings.