Cloud Storage

What This Skill Does

The Cloud Storage skill is a robust toolkit designed to standardize how the OpenClaw agent interacts with various cloud storage platforms. It provides a unified interface for managing files across traditional enterprise cloud providers (S3, GCS, Azure, R2) and personal productivity platforms (Google Drive, Dropbox, OneDrive). By abstracting the complexities of different provider APIs, this skill enables the agent to perform complex file operations like synchronization, migration, and maintenance while enforcing strict safety protocols.

Installation

To integrate this skill into your OpenClaw environment, use the following CLI command: clawhub install openclaw/skills/skills/ivangdavila/cloud-storage

Use Cases

• Bulk Cloud Migrations: Move data between S3 and Google Cloud Storage, ensuring checksum verification and egress cost optimization.
• Automated Backups: Establish routine file backups from local paths or secondary cloud providers, with built-in verification of backup integrity before deletion of original sources.
• Multi-platform Sync: Keep folders synchronized across Google Drive, OneDrive, and Dropbox, handling differences in folder permissions and file versioning automatically.
• Cost-Conscious Data Management: Utilize the skill's cost-awareness logic to determine if moving specific datasets is financially viable based on current egress pricing models.

Example Prompts

1. "Sync my client assets folder from Dropbox to an S3 bucket in us-east-1, verify the checksums, and provide a report on the egress costs incurred."
2. "Identify any files in my Google Drive that haven't been accessed in over 6 months and move them to S3 Glacier for long-term storage, but only if the total migration cost is under $5."
3. "Upload the report folder from my local directory to Azure Blob storage, ensuring the process is resumable if the network connection drops mid-transfer."

Tips & Limitations

• Verification is Mandatory: Do not rely on HTTP 200 responses as proof of transfer; the skill enforces post-transfer checksum verification to prevent data corruption.
• Rate Limits: Always be mindful of the destination's throughput capabilities (e.g., Google's 750GB/day upload limit). If a transfer exceeds these limits, the agent will throttle operations to prevent service bans.
• Auth Refresh: Refresh OAuth tokens before initiating long-running jobs to prevent mid-stream authentication failures.
• Cost Awareness: Always check the cost estimate before initiating bulk transfers, as egress fees can quickly exceed storage costs.