When to Use
User needs to upload, download, sync, or manage files across cloud storage providers. Agent handles multi-provider operations with cost awareness.
Quick Reference
| Topic | File |
|---|
| Provider-specific patterns | INLINECODE0 |
| Authentication setup |
auth.md |
| Cost calculation |
costs.md |
Scope
This skill covers operational cloud storage tasks across providers:
- - S3, GCS, Azure Blob, Backblaze B2, Cloudflare R2
- Google Drive, Dropbox, OneDrive, iCloud
For storage architecture decisions, see storage skill.
For S3-specific deep patterns, see s3 skill.
Critical Rules
- 1. Verify operations completed — API 200 ≠ success; check file exists with correct size/checksum
- Calculate ALL costs before large transfers — egress fees often exceed storage costs; check INLINECODE5
- Never delete without backup verification — confirm backup exists AND is restorable before removing source
- Handle partial failures — long operations fail mid-way; implement checkpoints and resume logic
- Rate limits vary wildly — Google 750GB/day upload, Dropbox batch limits, S3 3500 PUT/s per prefix
Authentication Traps
- - OAuth tokens expire — refresh before long operations, not during
- Service account ≠ user account — different quotas, permissions, audit trails
- Wrong region/endpoint — S3 bucket in
eu-west-1 won't work with INLINECODE7 - MFA required — some operations need session tokens, plan for interactive auth
Multi-Provider Gotchas
| Concept | Translates differently |
|---|
| Shared folder | Drive "Shared with me" ≠ Dropbox "Team Folders" ≠ OneDrive "SharePoint" |
| File ID |
Drive uses IDs; Dropbox uses paths; S3 uses keys |
| Versioning | S3 explicit enable; Drive automatic; Dropbox 180 days |
| Permissions | S3 ACLs + policies; Drive roles; Dropbox link-based |
Before Any Bulk Operation
- - [ ] Estimated time calculated (size ÷ bandwidth)
- [ ] Rate limits checked for both source AND destination
- [ ] Cost estimate including egress + API calls
- [ ] Checkpoint/resume strategy for failures
- [ ] Verification method defined (checksum, count, spot-check)
使用场景
用户需要跨云存储提供商上传、下载、同步或管理文件。智能体需处理多提供商操作，并具备成本意识。
快速参考
| 主题 | 文件 |
|---|
| 特定提供商模式 | providers.md |
| 身份验证设置 |
auth.md |
| 成本计算 | costs.md |
适用范围
本技能涵盖跨提供商的云存储操作任务：
- - S3、GCS、Azure Blob、Backblaze B2、Cloudflare R2
- Google Drive、Dropbox、OneDrive、iCloud
存储架构决策请参见 storage 技能。
S3 特定深度模式请参见 s3 技能。
关键规则
- 1. 验证操作完成 — API 返回200 ≠ 成功；需检查文件是否存在且大小/校验和正确
- 大规模传输前计算所有成本 — 出站费用常超过存储费用；请查阅 costs.md
- 未验证备份绝不删除 — 删除源文件前，确认备份存在且可恢复
- 处理部分失败 — 长时间操作可能中途失败；需实现检查点和恢复逻辑
- 速率限制差异巨大 — Google 每日上传750GB、Dropbox 批量限制、S3 每个前缀3500次PUT/秒
身份验证陷阱
- - OAuth令牌会过期 — 在长时间操作前刷新，而非操作过程中
- 服务账号 ≠ 用户账号 — 配额、权限、审计追踪均不同
- 错误的区域/端点 — eu-west-1 区域的S3存储桶无法使用 s3.amazonaws.com
- 需要MFA — 某些操作需要会话令牌，需规划交互式身份验证
多提供商注意事项
| 概念 | 不同翻译方式 |
|---|
| 共享文件夹 | Drive的与我共享 ≠ Dropbox的团队文件夹 ≠ OneDrive的SharePoint |
| 文件ID |
Drive使用ID；Dropbox使用路径；S3使用键 |
| 版本控制 | S3需显式启用；Drive自动启用；Dropbox保留180天 |
| 权限 | S3使用ACL+策略；Drive使用角色；Dropbox基于链接 |
任何批量操作前
- - [ ] 预估时间已计算（大小 ÷ 带宽）
- [ ] 源端和目标端的速率限制均已检查
- [ ] 成本估算包含出站费用和API调用费用
- [ ] 失败时的检查点/恢复策略已制定
- [ ] 验证方法已定义（校验和、计数、抽查）
