Offload R2 Asset
SkillCloud & infraLets your agent upload Remotion media assets to Cloudflare R2, switch code to hosted URLs, and remove local copies.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Offload R2 Asset skill
About this capability
Upload Remotion repository media assets to the Cloudflare R2 bucket behind remotion.media, switch source code to hosted URLs, verify the public objects, and remove repository-local copies.
What this skill tells your AI
The instructions your AI receives, as published by remotion-dev/remotion in .agents/skills/offload-r2/SKILL.md and read by ahel’s review.
Host media on https://remotion.media/, update every in-scope source reference to the public object, and remove the repository-local copy after verification.
Workflow
-
Find the main worktree with
git worktree list --porcelain. Prefer the worktree onrefs/heads/main, normally/Users/jonathanburger/remotion. -
Choose a stable, descriptive object key. Use a feature-specific directory prefix when it prevents collisions, for example
studio-close-ups/demo.mp4. When replacing an asset, prefer a new versioned key so browser and Studio caches cannot serve the previous bytes. -
Load credentials from the main worktree without printing them:
--env-file=/Users/jonathanburger/remotion/packages/remotion-media/.envThe required variables are
AWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEY. -
Upload to the
parser-mediabucket with Bun's S3-compatible client:bun --env-file=/Users/jonathanburger/remotion/packages/remotion-media/.env -e "import {S3Client} from 'bun'; const filePath='<local-file>'; const key='<object-key>'; const client=new S3Client({accessKeyId:Bun.env.AWS_ACCESS_KEY_ID,secretAccessKey:Bun.env.AWS_SECRET_ACCESS_KEY,endpoint:'https://2fe488b3b0f4deee223aef7464784c46.r2.cloudflarestorage.com',bucket:'parser-media'}); const bytes=new Uint8Array(await Bun.file(filePath).arrayBuffer()); await client.write(key,bytes); const remote=await client.file(key).arrayBuffer(); if (remote.byteLength!==bytes.byteLength) throw new Error('Size mismatch'); console.log('uploaded',key,remote.byteLength);" -
Verify the public object and compare its SHA-256 hash with the local file before removing anything:
curl -I --fail https://remotion.media/<object-key> test "$(shasum -a 256 <local-file> | cut -d' ' -f1)" = "$(curl --fail --silent https://remotion.media/<object-key> | shasum -a 256 | cut -d' ' -f1)" -
Replace every in-scope source usage with the public URL. Do not wrap remote URLs in
staticFile()because it rejectshttp://andhttps://URLs. -
After the public hash matches and source references are remote, remove the local copy. Use
git rm -- <local-file>for a tracked file or remove the exact untracked/ignored file directly. Remove obsolete asset-specific.gitignoreentries and empty asset directories. Do not use recursive deletion or broad globs. -
Verify the local copy is gone and search the affected package for remaining local references:
test ! -e <local-file> rg -n '<local-filename>|staticFile\(' <affected-package> -
Run focused lint or style checks for touched packages. Commit or push only when requested.
Signals
- GitHub stars
- 59k
- Forks
- 4k
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
offload-r2- Source
- github.com/remotion-dev/remotion