android-transfer-secure

What This Skill Does

The android-transfer-secure skill provides a robust, enterprise-grade mechanism for transferring files between macOS environments and connected Android devices. Unlike standard MTP (Media Transfer Protocol) implementations, this skill prioritizes data integrity and security by integrating automated SHA256 checksum verification for every file moved. It features strict path validation, which acts as a barrier against directory traversal attacks, and includes built-in safeguards to prevent unintentional overwriting of existing data, ensuring that your critical files remain protected during the migration process.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/aadipapp/android-transfer-skill Ensure that your Android device is in Developer Mode with USB Debugging enabled and that you have authorized the workstation via ADB (Android Debug Bridge) before initiating transfers.

Use Cases

This skill is ideal for developers, data engineers, and power users who move sensitive data between local workstations and Android handsets. It is particularly effective for securely deploying configuration files, backing up application logs, or managing encrypted media assets where verify-on-write is a mandatory requirement for compliance or data health.

Example Prompts

1. "OpenClaw, securely move my local project report to the /sdcard/Documents folder on my Android device and verify the SHA256 hash."
2. "Transfer the latest build APK from my downloads folder to the Android device, but make sure to stop and prompt me if a file with the same name already exists."
3. "Sync the contents of my secure-notes directory to the Android target, ensuring no paths outside the target directory can be accessed."

Tips & Limitations

• Permissions: Always ensure your device has granted the necessary ADB permissions; the skill cannot bypass Android's scoped storage restrictions.
• Verification: Large files may take longer to transfer because the SHA256 calculation must complete before the operation is finalized.
• Pathing: Always provide absolute paths for the destination to avoid ambiguity. The skill will reject any path that attempts to escape the designated storage root.