import-media

You can pull media from an Android phone by executing adb pull commands driven by pre-configured mappings. The skill selects target directories by label, validates device and local paths, creates missing folders, and preserves the original directory structure during transfer.

Incremental sync fetches only new files added since the last run, while full mirroring copies the entire contents of a specified phone path. This skill supports both modes using mappings.yaml to define whether a pull is incremental or a complete mirror.

Yes, you need an existing mappings.yaml file configured with pull or bidirectional directions. This skill relies on these saved mappings to determine which phone directories to transfer media from and where to place them locally.

Yes, you can automate copying specific folders by defining them as labeled mappings in your mappings.yaml file. The skill reads these mappings to pull media only from the configured phone directories, keeping transfers organized and reproducible.

If the local destination directory does not exist, the skill creates it automatically during the transfer process. It validates both phone and local paths before executing adb pull commands to prevent path-related errors.

Yes, the skill reports summary metrics after syncing media, including the total count of files transferred, total bytes copied, and the top file types encountered. This provides visibility into the results of the adb pull operation.