Remotion Video Production
- 383 installs
- 40 repo stars
- Updated August 4, 2026
- akillness/oh-my-skills
remotion-video-production is an agent skill that produces programmatic React-based videos with Remotion for developers who need code-driven promo, explainer, or release announcement clips instead of manual video editing.
About
remotion-video-production is an agent skill from akillness/oh-my-skills that guides developers through building videos as React code using the Remotion framework. The skill helps define compositions, timelines, props, animations, and render commands so promos, explainers, social clips, and release announcements can be regenerated from templates when data or copy changes. Developers reach for remotion-video-production when marketing or product teams need repeatable, version-controlled video output tied to a codebase rather than one-off Premiere or Final Cut projects. It covers the build-phase workflow of authoring Remotion components, previewing in the Remotion studio, and exporting MP4 or GIF assets from parameterized React templates.
- Structures Remotion compositions and scene timelines
- Reuses React components for branded motion graphics
- Supports templated promo and social video generation
- Coordinates assets, text, and animation parameters
- Enables batch or agent-driven video renders
Remotion Video Production by the numbers
- 383 all-time installs (skills.sh)
- Ranked #449 of 1,335 Generative Media skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/akillness/oh-my-skills --skill remotion-video-productionAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 383 |
|---|---|
| repo stars | ★ 40 |
| Last updated | August 4, 2026 |
| Repository | akillness/oh-my-skills ↗ |
How do you render promo videos with Remotion React?
Produce programmatic React-based videos with Remotion for promos, explainers, social clips, or release announcements where code-driven templates beat one-off manual editing.
Who is it for?
Frontend developers who want repeatable, code-driven promo or release videos using Remotion React templates.
Skip if: Teams that only need one-off manual video edits in desktop NLE tools with no programmatic reuse.
When should I use this skill?
A developer needs to create or update programmatic React-based videos with Remotion for promos, explainers, or release clips.
What you get
Remotion React compositions, render config, and exported MP4 or GIF video files
- Remotion composition files
- rendered MP4 or GIF
Files
Note: This skill is a compatibility wrapper for video-production. Use it when the environment still references the Remotion-specific name, but execute the same canonical programmable-video workflow with the code-first programmable video mode selected.Remotion Video Production
Read references/alias-routing.md and references/remotion-route-outs.md before handling broad or ambiguous Remotion requests.
When to use this skill
- A legacy prompt, installed catalog, or setup surface still calls
remotion-video-production - The user explicitly names Remotion, React-based video composition, scenes, compositions, or rendering from code
- The safest behavior is to preserve backward compatibility while steering future usage toward
video-production
When not to use this skill
- The user can already adopt
video-productiondirectly with no compatibility concern - The request is really template/API automation with no Remotion-specific stack need
- The task is only manual finishing or editorial polish with no code-first render layer
Instructions
Step 1: Resolve to the canonical skill
Immediately map this alias to video-production.
Step 2: Lock the mode to code-first programmable video
Run the canonical workflow, but choose Code-first programmable video unless the request clearly says the stack assumption is wrong.
Step 3: Preserve the legacy / explicit reference in the response
If helpful, note that remotion-video-production is the legacy-compatible or explicit-stack alias for video-production.
Step 4: Reuse the canonical packet shape
Use the same process as video-production: 1. normalize the video brief, 2. choose the packet type, 3. return one implementation-ready brief, 4. include assets, QA risks, and handoffs.
Step 5: Keep alternative modes visible
If the ask sounds like bulk personalization, spreadsheet-driven generation, or vendor/API automation rather than a React video codebase, say so explicitly and route back through the relevant video-production mode instead of over-committing to Remotion.
Step 6: Avoid becoming a competing skill
Do not invent separate heuristics, outputs, or support rules here. This alias exists to reduce migration friction and catch explicit Remotion naming, not to compete with the canonical skill.
Output format
Return the same Video Production Brief used by video-production, with a Remotion-flavored stack recommendation when applicable.
Examples
Example 1: legacy setup surface
Input
Use remotion-video-production to help us plan a reusable product video template.
Expected behavior
- Briefly note that the request maps to
video-production - Use the code-first programmable-video mode
- Return a canonical Video Production Brief
Example 2: explicit stack request
Input
We need a Remotion composition plan for weekly feature-announcement videos.
Expected behavior
- Treat the stack choice as explicit
- Use scene/template/rendering language
- Keep the packet shape aligned with the canonical skill
Best practices
1. Keep the alias lightweight and explicit. 2. Preserve backward compatibility without duplicating the full canonical instructions. 3. Nudge future discovery toward video-production whenever naming or setup surfaces are being updated. 4. Reuse the canonical video-production support packet instead of improvising a second media workflow here. 5. Make route-outs explicit when a request is better served by template/API automation than by a Remotion codebase.
References
../video-production/SKILL.mdreferences/alias-routing.mdreferences/remotion-route-outs.md
{
"skill_name": "remotion-video-production",
"evals": [
{
"id": 1,
"prompt": "Use remotion-video-production to help us plan a reusable launch video template.",
"expected_output": "Maps the alias to video-production, keeps the canonical packet shape, and locks the mode to code-first programmable video.",
"assertions": [
"Output notes that remotion-video-production maps to video-production or is a compatibility alias",
"Output selects Code-first programmable video as the primary mode",
"Output returns a Video Production Brief or equivalent canonical packet"
]
},
{
"id": 2,
"prompt": "We need a Remotion composition plan for weekly feature-announcement videos.",
"expected_output": "Uses Remotion-specific workflow language without inventing a competing skill or packet format.",
"assertions": [
"Output mentions Remotion, scenes, compositions, or rendering",
"Output keeps the response aligned with the canonical video-production workflow",
"Output includes asset or QA guidance"
]
},
{
"id": 3,
"prompt": "Our ops team asked for remotion-video-production, but the real job is generating thousands of recap videos from spreadsheet rows with minimal engineering overhead.",
"expected_output": "Acknowledges the alias while routing the workflow back to a broader template/API automation path under video-production instead of forcing a Remotion codebase.",
"assertions": [
"Output notes that remotion-video-production is a compatibility alias or maps to video-production",
"Output explicitly says template/API automation or a broader video-production mode is a better fit than a Remotion codebase",
"Output still returns one coherent implementation-ready packet rather than multiple competing plans"
]
}
]
}
Remotion alias routing
remotion-video-production is a compatibility alias, not a second programmable-video peer.
Use this alias when
- a user explicitly says
remotion-video-production - a setup surface, prompt pack, or migration still depends on the old folder/name
- the stack choice is explicitly Remotion and preserving that exact-name intent is useful
Route to the canonical skill when
- the user just wants automated or repeatable video production without caring about the old alias name
- the request needs the full production-mode decision (code-first, template/API, repurposing, or manual-finish hybrid)
- the work depends on the canonical support packet for asset minimums, QA, and publishing handoffs
Canonical target: ../video-production/SKILL.md
Required response pattern
1. Acknowledge that remotion-video-production is still supported for compatibility. 2. State that the canonical workflow now lives in video-production. 3. Continue with the canonical workflow, locking the primary mode to Code-first programmable video when Remotion is truly the right fit. 4. Preserve the alias name only where exact-name compatibility matters.
Why this exists
The repo keeps one canonical programmable-video entry plus one thin Remotion alias so legacy prompts keep working without turning the creative-media lane back into two overlapping peers.
Remotion alias: route-outs and canonical packets
The alias should stay thin because the real workflow packaging already lives in video-production.
Canonical packets to use after alias handoff
../video-production/references/production-modes.md../video-production/references/asset-and-qa-checklist.md../video-production/references/handoff-boundaries.md
Stay in Remotion when
- the user explicitly wants React-based video composition, scenes, components, or render workers
- runtime customization via
@remotion/playeror app-owned props is part of the ask - the team wants code ownership and a reusable composition codebase
Route back to broader video-production modes when
- the real need is spreadsheet/API/no-code bulk generation, mass personalization, or vendor-managed rendering
- the source material is long-form media and the main job is clip extraction, captioning, and packaging at scale
- the problem is final editorial polish or approval workflow rather than the render stack itself
Practical reminder
Explicit Remotion naming should bias the primary mode toward Code-first programmable video, but it should not hide when the better answer is a template/API workflow, repurposing pipeline, or manual-finish handoff.
Compact-surface rule
SKILL.toon and any other short-form inventory should describe this folder as a compatibility alias for video-production, not as the canonical media skill.
N:remotion-video-production
D:Compatibility alias for `video-production` when legacy tooling or an explicit Remotion request still expects the old skill name. Preserve exact-name compatibility, route substantive work to the canonical programmable-video workflow, and default to the code-first mode only when Remotion is truly the right stack.
G:video remotion alias compatibility programmable-video automated-video react compositions render-player migration
U[4]:
Catch exact-name legacy prompts that still invoke `remotion-video-production`
Preserve explicit Remotion stack requests while routing to the canonical video-production workflow
Keep code-first programmable-video mode as the default only for true Remotion asks
Route bulk template/API, repurposing, or manual-finish work back to broader video-production modes
S[5]{n,action,details}:
1,Resolve,Acknowledge the alias and state that `video-production` now owns the canonical programmable-video workflow
2,Lock,Use Code-first programmable video when the user truly needs Remotion scenes/components/player/runtime control
3,Reuse,Pull the packet shape, asset minimums, QA checklist, and handoff boundaries from `video-production`
4,Route-out,If the real need is API/template automation, clip repurposing, or manual polish, say so explicitly and hand back to the relevant canonical mode
5,Deliver,Return one canonical Video Production Brief while preserving the alias name only where compatibility matters
R[4]:
Keep this folder thin — no competing heuristics or packet types
Treat `video-production` as the canonical owner for support docs and workflow boundaries
Make explicit Remotion cues visible: compositions, props, rendering, player embedding
Refresh compact discovery surfaces whenever alias wording changes materially
E[2]{desc,in,out}:
"Legacy alias request","Use remotion-video-production to plan a reusable product video template","Alias acknowledgement plus canonical Video Production Brief using the code-first programmable-video mode"
"Wrong-stack detection","We need thousands of personalized recap videos from a spreadsheet feed","Alias routes back to template/API automation under video-production instead of overcommitting to Remotion"
Related skills
Remotion Best PracticesGet Remotion-specific coding guidance that prevents common video rendering mistakes when creating animated React videos.451k4.2k
Ai Video GenerationGenerate videos using 40+ AI models including Veo, Seedance, and others via inference.sh442k665Ai Image GenerationGenerate images using 50+ AI models including FLUX, Gemini, and Replicate via inference.sh441k665Ai Avatar VideoGenerate videos featuring AI avatars for product demos, tutorials, marketing, or explainers441k665Remotion RenderRender videos programmatically using React components and Remotion framework441k665
Remotion RenderGenerate high-quality MP4 videos from React code using Remotion inside an AI coding agent.363k665How it compares
Pick remotion-video-production for code-driven repeatable renders rather than static image generation or manual NLE editing skills.
FAQ
What does remotion-video-production output?
remotion-video-production guides developers to create Remotion React compositions with props and timelines, then render exported MP4 or GIF files for promos, explainers, social clips, or release announcements from code-driven templates.
When should I use Remotion over manual editing?
Use remotion-video-production when videos must be regenerated from data or copy changes, version-controlled in a repo, and rendered programmatically with React instead of rebuilt manually in a desktop editor.