Sync

What This Skill Does

The Sync skill is an enterprise-grade utility designed for the OpenClaw AI agent to manage, mirror, and synchronize files across diverse environments. Whether you are dealing with local directories, remote servers over SSH, or cloud storage providers like S3, this skill provides a structured framework for data integrity. It leverages industry-standard tools like rsync for filesystem operations and rclone for cloud integrations, ensuring that transfers are robust, version-aware, and verifiable. It handles complex tasks such as differential transfers, exclusion management via ignore files, and checksum verification.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/ivangdavila/sync Ensure that your environment has rsync and rclone installed and available in the system PATH before executing the command to avoid dependency errors.

Use Cases

• Deployment Automation: Seamlessly push build artifacts from a local machine to a remote web server using secure, key-based SSH authentication.
• Cloud Backup: Automatically back up sensitive project directories to S3, Google Cloud Storage, or B2 using rclone with specific chunk sizing for large files.
• Data Consistency: Use rsync with the --checksum flag to verify that two directories are identical, preventing issues caused by clock skew or timestamp mismatches.
• Clean Development Environments: Utilize custom .syncignore files to mirror source code while excluding transient artifacts like .git or node_modules.

Example Prompts

1. "Sync the local folder './src' to the remote server 'web-prod' at /var/www/html/ using key '~/.ssh/deploy_key', ensuring we mirror the source exactly and exclude any git metadata."
2. "Perform a dry-run backup of my local project to the S3 bucket named 'my-project-backups' and provide a progress bar during the operation."
3. "Verify the integrity of my remote backup folder against the local copy using checksums and output the results to a file named sync-verify.log."

Tips & Limitations

• Trailing Slashes: Always remember that src/ copies the contents, while src copies the directory itself. This is critical for preventing incorrect nesting.
• Bidirectional Challenges: rsync is strictly one-way. For bidirectional synchronization (e.g., syncing between two workstations), look into unison or dedicated synchronization software like Syncthing rather than forcing a script-based solution.
• Permissions: Always test commands with --dry-run to visualize changes before they occur. Be wary of using --delete in production environments without rigorous testing, as it permanently removes files on the destination that do not exist in the source.