sync-to-cloudinary
Use when uploading ad asset variants to Cloudinary with structured folder naming, metadata tags, and sync status tracking. Handles retry logic and integrates with the cloudinary skill for API reference.
| Model | Source |
|---|---|
| sonnet | pack: ad-assets |
Full Reference
sync-to-cloudinary
Section titled “sync-to-cloudinary”Uploads ad asset variants to Cloudinary with a consistent folder structure, rich metadata tags, and sync status tracking. Processes the variant manifest from generate-ad-variants. Handles concurrent uploads with configurable concurrency, exponential backoff on failure, and per-variant status persistence so runs are resumable. For Cloudinary API reference (upload params, transformation syntax, signed URLs), use the cloudinary skill.
Quick Reference
Section titled “Quick Reference”| Fact | Value |
|---|---|
| Folder pattern | ads/images/{platform}/{placement}/{filename} |
| Default concurrency | 5 parallel uploads |
| Default max retries | 3 |
| Backoff schedule | 1s, 2s, 4s (exponential) |
| Status file | ./sync-status.json |
| overwrite default | false — skips existing Cloudinary assets |
| Required env vars | CLOUDINARY_CLOUD_NAME, CLOUDINARY_API_KEY, CLOUDINARY_API_SECRET |
Reference Index
Section titled “Reference Index”| I want to… | File |
|---|---|
| Implement upload with retry, concurrency, folder naming, and tags | upload.md |
| Understand SyncRecord lifecycle, sync-status.json persistence, and resume behavior | sync-status.md |
Usage: Read the reference file matching your current task from the index above. Each file is self-contained with code examples and inline gotchas.
Announcement
Section titled “Announcement”┏━ 🎯 sync-to-cloudinary ━━━━━━━━━━━━━━━━━━━━━━━━┓ ┃ Syncing: [N] variants → Cloudinary ┃ ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛