Homepage Video Assets
Use when rendering or replacing Remotion homepage creator strip videos, especially transparent Chrome WebM and Safari MP4 assets hosted on remotion.media.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Homepage Video Assets when an AI agent needs a reusable SKILL.md workflow for this job: Use when rendering or replacing Remotion homepage creator strip videos, especially transparent Chrome WebM and Safari MP4 assets hosted on remotion.media.
When not to use it
Skip Homepage Video Assets when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/homepage-video-assets # Save SKILL.md to ~/.claude/skills/homepage-video-assets/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/homepage-video-assets/SKILL.md. For a shared project, commit the folder at .claude/skills/homepage-video-assets/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Homepage Video Assets skill for this task: Render a fresh transparent ProRes 4444 master from packages/brand. Confirm any required inputs or files before making changes.
What supports this recommendation?
81/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 86/100
- Practical detail
- 92/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Homepage Video Assets
Use this workflow for homepage creator strip assets such as:
- `homepage-assets-master` - `editing-vp9-chrome` / `editing-safari` - `what-is-remotion`
## Workflow
1. Render a fresh transparent ProRes 4444 master from `packages/brand`.
```bash cd packages/brand bunx remotion render <composition-id> /tmp/<asset>-master.mov \ --codec=prores \ --prores-profile=4444 \ --pixel-format=yuva444p10le \ --image-format=png \ --timeout=120000 \ --overwrite ```
2. Convert from the ProRes master, not from a previous WebM/MOV.
Chrome WebM:
```bash ffmpeg -y -i /tmp/<asset>-master.mov \ -vf scale=540:540 \ -c:v libvpx \ -pix_fmt yuva420p \ -auto-alt-ref 0 \ -an /tmp/<chrome-name>.webm ```
Safari MP4:
```bash ffmpeg -y -i /tmp/<asset>-master.mov \ -vf scale=540:540 \ -c:v prores_ks \ -profile:v 4 \ -pix_fmt yuva444p10le \ -an /tmp/<asset>-540-prores.mov
avconvert \ --source /tmp/<asset>-540-prores.mov \ --preset PresetHEVCHighestQualityWithAlpha \ --output /tmp/<safari-name>.mp4 \ --replace ```
3. Use the `offload-r2` skill to upload both outputs under `homepage/` with new versioned keys, verify their public SHA-256 hashes, and update the URLs in the relevant homepage consumers. Keep the rendered binaries out of Git.
## Verification
Verify the ProRes master has real alpha before converting, and inspect the Safari MP4:
```bash ffmpeg -i /tmp/<asset>-master.mov ffmpeg -i /tmp/<safari-name>.mp4 ffmpeg -y -i /tmp/<asset>-master.mov \ -vf alphaextract -frames:v 1 /tmp/<asset>-alpha.png ```
The master should report `prores (4444)` and a `yuva...` pixel format. `alphaextract` should succeed, and the alpha image should not be fully opaque. A common failure mode is `alphaextract` succeeding but every sampled pixel is opaque; in that case, the master was rendered with a black/opaque background or a stale opaque master was reused.
Verify the Chrome WebM and Safari MP4 are exactly `540x540`:
```bash for f in \ /tmp/<chrome-name>.webm \ /tmp/<safari-name>.mp4; do ffmpeg -i "$f" done ```
The Safari MP4 should look like the known-good file shape: `major_brand: mp42`, `compatible_brands: isommp41mp42`, `Video: hevc (Main) (hvc1)`, `540x540`, and `handler_name: Core Media Video`. If it reports `h264 (avc1)` or dimensions such as `960x540`, it is the wrong file and will render differently in Safari.
Do not add ProRes `.mov` files to the homepage PR; they are too large. Safari should use the small `.mp4` fallback. Chrome should use the transparent `.webm`.
Intended uses
- Render a fresh transparent ProRes 4444 master from packages/brand.
- Convert from the ProRes master, not from a previous WebM/MOV.
- Use the offload-r2 skill to upload both outputs under homepage/ with
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.