onboard

Interview users to collect Android device details and folder mappings for adb-ops onboarding.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/danielrosehill/Claude-ADB-Ops-Plugin --skill onboard-danielrosehill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: onboard
Source: https://github.com/danielrosehill/Claude-ADB-Ops-Plugin/tree/main/skills/onboard
Command: npx skills add https://github.com/danielrosehill/Claude-ADB-Ops-Plugin --skill onboard-danielrosehill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Onboarding a new Android device into adb-ops can be tedious without a guided workflow for collecting device details and folder mappings.

Core Features & Use Cases

  • Guided device interview to capture model, Android version, and root status.
  • Collect and persist folder mappings between phone paths and local paths with labels and use cases.
  • Writes profile.yaml and mappings.yaml into the workspace, enabling subsequent skills like device-status, take-screenshot, and import-media.

Quick Start

Launch onboard with a connected device and follow the prompts to create a new profile and mapping set.

Frequently Asked Questions about onboard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I onboard a new Android device for adb automation?▼

Onboarding a new Android device for adb automation involves a guided interview to capture model, Android version, and root status, then writing this data to profile.yaml for subsequent adb-ops skills.

How do I map Android phone folders to local paths for adb operations?▼

You map Android phone folders to local paths by creating mappings.yaml entries with labels and use cases, allowing subsequent adb-ops skills to transfer files between device and workspace.

Do I need a rooted Android device to set up an adb device profile?▼

A rooted device is not required to set up an adb device profile. The onboarding interview captures root status, but only requires a live adb-enabled device and adb tools to write profile.yaml.

What files are created in the workspace during adb device onboarding?▼

The onboarding process creates profile.yaml for device details and mappings.yaml for folder mappings, persisting both configuration files under the workspace/ directory for subsequent adb-ops skills.

Can I use this onboarding workflow without a live adb connection?▼

No, this onboarding workflow requires a live adb-enabled device. Setting up a device profile and initial folder mappings depends on an active adb connection to write profile.yaml and mappings.yaml.