Remotion to HyperFrames Porter
heygen-com/hyperframes
Ports an existing Remotion (React) composition to HyperFrames HTML with GSAP, one way, and grades the result against a tiered set of reference fixtures.
Update the current Remotion branch with the latest canonical main branch.
Install Update From Upstream Main
$ npx skills add remotion-dev/remotion --skill update-from-upstream-main -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install remotion-dev/remotion update-from-upstream-main --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/remotion-dev/remotion.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/update-from-upstream-main .claude/skills/update-from-upstream-main && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "update-from-upstream-main" agent skill from https://github.com/remotion-dev/remotion/tree/main/.agents/skills/update-from-upstream-main into .claude/skills/update-from-upstream-main/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-from-upstream-main", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/remotion-dev/remotion/tree/main/.agents/skills/update-from-upstream-mainType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add remotion-dev/remotion --skill update-from-upstream-main -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install remotion-dev/remotion update-from-upstream-main --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/remotion-dev/remotion.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/update-from-upstream-main .agents/skills/update-from-upstream-main && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "update-from-upstream-main" agent skill from https://github.com/remotion-dev/remotion/tree/main/.agents/skills/update-from-upstream-main into .agents/skills/update-from-upstream-main/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-from-upstream-main", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add remotion-dev/remotion --skill update-from-upstream-main -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install remotion-dev/remotion update-from-upstream-main --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/remotion-dev/remotion.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/update-from-upstream-main .cursor/skills/update-from-upstream-main && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "update-from-upstream-main" agent skill from https://github.com/remotion-dev/remotion/tree/main/.agents/skills/update-from-upstream-main into .cursor/skills/update-from-upstream-main/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-from-upstream-main", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/remotion-dev/remotion.git --path .agents/skills/update-from-upstream-main--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add remotion-dev/remotion --skill update-from-upstream-main -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install remotion-dev/remotion update-from-upstream-main --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/remotion-dev/remotion.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/update-from-upstream-main .gemini/skills/update-from-upstream-main && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "update-from-upstream-main" agent skill from https://github.com/remotion-dev/remotion/tree/main/.agents/skills/update-from-upstream-main into .gemini/skills/update-from-upstream-main/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-from-upstream-main", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install remotion-dev/remotion update-from-upstream-mainInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add remotion-dev/remotion --skill update-from-upstream-main -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/remotion-dev/remotion.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/update-from-upstream-main .github/skills/update-from-upstream-main && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "update-from-upstream-main" agent skill from https://github.com/remotion-dev/remotion/tree/main/.agents/skills/update-from-upstream-main into .github/skills/update-from-upstream-main/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-from-upstream-main", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add remotion-dev/remotion --skill update-from-upstream-main -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install remotion-dev/remotion update-from-upstream-main --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/remotion-dev/remotion.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/update-from-upstream-main .opencode/skills/update-from-upstream-main && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "update-from-upstream-main" agent skill from https://github.com/remotion-dev/remotion/tree/main/.agents/skills/update-from-upstream-main into .opencode/skills/update-from-upstream-main/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-from-upstream-main", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
update-from-upstream-main- GitHub stars
- 62k
- Token cost
- ~1k tokens
- SKILL.md length
- 472 words
- Files
- 2
- Skills in repo
- 71
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Update the current Remotion branch with the latest canonical main branch.
- Works in 9 steps: Inspect the repository before changing it → Select the canonical remote whose URL… → Fetch the latest main branch without… → …
- Asked to update
- Calls git, bun and rg
- Sync from upstream main
What it does
Update From Upstream Main is an agent skill from remotion-dev/remotion, published by the product's own GitHub organization. Update the current Remotion branch with the latest canonical main branch. Use when asked to update or sync from upstream main, merge the latest main into a feature branch, fast-forward local main, or bring a pull request branch up to date without rewriting published history.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Media & Creative, covering Video production and Pull requests. It works with Remotion. The repository describes itself as: 🎥 Make videos programmatically with React.
When your agent uses it
- Asked to update
- Sync from upstream main
- Merge the latest main into a feature branch
- Fast-forward local main
Example prompts
- “/update-from-upstream-main”
Workflow steps
9 steps, taken from the first numbered list in SKILL.md.
- Inspect the repository before changing it
- Select the canonical remote whose URL points to remotion-dev/remotion. Prefer upstream when it exists; otherwise use origin. If neither…
- Fetch the latest main branch without changing the working tree
- Update the checked-out branch
- If the merge conflicts, resolve each file deliberately and preserve both the feature intent and upstream changes. Do not accept ours or…
- If step 1 created a stash, reapply it after the upstream update is complete
- Validate the result. Always run git diff --check and git diff --cached --check. If conflicts were resolved or the combined changes could…
- Push only when the user asked to update a published branch or pull request. Use a normal push and stop if it is rejected
- Report the previous and new commit, whether the checkout is detached, whether the update was a fast-forward or merge, whether local…
What it can do on your machine
Read from SKILL.md and the folder at commit 1e4c5de. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitbunrg
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Update From Upstream Main loads about 1k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 472 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 472 words (~1,010 tokens).
“Update from the canonical remotion-dev/remotion repository while preserving local work and published branch history.”
- name
- update-from-upstream-main
Files
SKILL.md and 1 other file in .agents/skills/update-from-upstream-main of remotion-dev/remotion.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 1e4c5de
Compare with similar skills
Update From Upstream Main next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Update From Upstream Main this skillremotion-dev/remotion | 62k | — | ~1k | Automated safety check: Pass | Custom licence | |
| Remotion to HyperFrames Porterheygen-com/hyperframes | 58k | 3 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Pull Request Explainer Videoheygen-com/hyperframes | 58k | 2 repos | ~8.2k | Automated safety check: Notes | Apache-2.0 | |
| Disney Animation Rule Skillvibe-motion/skills | 1.3k | — | ~1.5k | Automated safety check: Pass | None | |
| Remotion Best Practiceslyonjs/shortvid.io | 147 | 32 repos | ~1k | Automated safety check: Pass | MIT | |
| Making Demo Videosnukeop/nuclear | 19k | — | ~892 | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Pull Request Explainer Video
heygen-com/hyperframes
Turns a GitHub pull request into a code-change explainer video built from its diff, commits and files, rendered with HyperFrames.
Disney Animation Rule Skill
vibe-motion/skills
Apply Disney's 12 principles as practical design and engineering rules for procedural animation.
Remotion Best Practices
lyonjs/shortvid.io
Best practices for Remotion - Video creation in React. An agent skill from lyonjs/shortvid.io.
Making Demo Videos
nukeop/nuclear
A skill your agent uses when making a demo, tutorial, or feature video of Nuclear.
HyperFrames Video Entry Point
heygen-com/hyperframes
Entry point for making, editing and rendering videos from HTML compositions with HyperFrames, routing each request to the right workflow.
More from remotion-dev/remotion
All 71 skills in this repo- Official
Gh Stack
remotion-dev/remotion
Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack.
- Official
Canvas Capture Extension
remotion-dev/remotion
Rebuild, install, and reload the private Remotion Canvas Capture unpacked Chrome extension.
- Official
Nullable New Params
remotion-dev/remotion
Fix newly added optional parameters, optional React props, and optional type/interface members in Remotion monorepo diffs by converting internal APIs to required nullable values and updating call…
- Official
Vercel
remotion-dev/remotion
Set up a Codex monitor for Vercel deployments and preview URLs.
- Official
Writing Docs
remotion-dev/remotion
Guides for writing and editing Remotion documentation. An agent skill from remotion-dev/remotion.
- Official
Find Unplanned Issues
remotion-dev/remotion
Audit and clean the Remotion GitHub masterplan hierarchy. An agent skill from remotion-dev/remotion.
Related
Works with
Categories
Questions about Update From Upstream Main
What does Update From Upstream Main do?
Update the current Remotion branch with the latest canonical main branch. Update From Upstream Main is an agent skill from remotion-dev/remotion, published by the product's own GitHub organization. Update the current Remotion branch with the latest canonical main branch.
When should I use Update From Upstream Main?
Update From Upstream Main fits situations like: asked to update; sync from upstream main; merge the latest main into a feature branch; fast-forward local main.
How do I install Update From Upstream Main in Claude Code?
Run `npx skills add remotion-dev/remotion --skill update-from-upstream-main -a claude-code`. Or copy the skill folder (.agents/skills/update-from-upstream-main in remotion-dev/remotion) into .claude/skills/update-from-upstream-main in your project. Claude Code loads it when a task matches its description.
How do I install Update From Upstream Main in Codex?
Run `npx skills add remotion-dev/remotion --skill update-from-upstream-main -a codex`. Or copy the skill folder (.agents/skills/update-from-upstream-main in remotion-dev/remotion) into .agents/skills/update-from-upstream-main in your project. Codex loads it when a task matches its description.
Can I use Update From Upstream Main in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add remotion-dev/remotion --skill update-from-upstream-main -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/update-from-upstream-main, .gemini/skills/update-from-upstream-main, .github/skills/update-from-upstream-main and .opencode/skills/update-from-upstream-main in your project.
What does Update From Upstream Main need to run?
Going by SKILL.md and its folder, Update From Upstream Main needs the command-line tools its instructions call (git, bun and rg).
Does Update From Upstream Main access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Update From Upstream Main safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Update From Upstream Main use?
Update From Upstream Main has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Update From Upstream Main use?
About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Update From Upstream Main?
Skills that share tags, products or a category with Update From Upstream Main: Remotion to HyperFrames Porter (heygen-com/hyperframes, 58k stars), Pull Request Explainer Video (heygen-com/hyperframes, 58k stars), Disney Animation Rule Skill (vibe-motion/skills, 1.3k stars) and Remotion Best Practices (lyonjs/shortvid.io, 147 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Update From Upstream Main?
remotion-dev (a GitHub organization, an official publisher) maintains it in remotion-dev/remotion, which has 62,235 GitHub stars. The repository holds 71 skills in this directory. The repository was last updated on October 7, 2026.
Source: remotion-dev/remotion on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.