MCPInstall

remotion-video-production

Compatibility alias for video-production when a prompt, setup surface, or legacy workflow explicitly asks for Remotion video production. Use when the request names Remotion, React-based video rendering, compositions, scene components, or a legacy remotion-video-production catalog entry, but the real workflow is still the canonical programmable-video lane. Prefer video-production for general use. Triggers on: remotion-video-production, Remotion render pipeline, React video composition, migrate old Remotion skill.

Installs
520
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/akillness/jeo-skills --skill remotion-video-production
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads remotion-video-production automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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-production directly 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.md
  • references/alias-routing.md
  • references/remotion-route-outs.md

FAQ

What does the remotion-video-production skill do?

Compatibility alias for video-production when a prompt, setup surface, or legacy workflow explicitly asks for Remotion video production. Use when the request names Remotion, React-based video rendering, compositions, scene components, or a legacy remotion-video-production catalog entry, but the real workflow is still the canonical programmable-video lane. Prefer video-production for general use. Triggers on: remotion-video-production, Remotion render pipeline, React video composition, migrate old Remotion skill.

How do I install remotion-video-production?

Run npx skills add https://github.com/akillness/jeo-skills --skill remotion-video-production in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/remotion-video-production/ (personal) or .claude/skills/remotion-video-production/ (project).

Which AI agents can use remotion-video-production?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is remotion-video-production safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains remotion-video-production?

It is published by akillness in akillness/jeo-skills. It has 520 recorded installs.

More from akillness/jeo-skills

View all →

rtk

akillness/jeo-skills

Install, initialize, verify, and troubleshoot RTK (Rust Token Killer) for AI coding agents. Use when you need to reduce shell-command token output, confirm that the correct rtk binary is installed, choose between Homebrew, install.sh, or Cargo installation, wire rtk init for Claude Code, Codex, Gemini CLI, Cursor, Copilot, Windsurf, Cline, or OpenCode, or use compact wrappers such as rtk git status, rtk read, rtk grep, rtk test, rtk lint, and rtk gain. Triggers on: rtk, rust token killer, token saver cli, rtk init, rtk gain, codex rtk, gemini rtk, opencode rtk, claude hook token reduction.

Backend & APIs672 installs

graphify

akillness/jeo-skills

Drive Graphify from its CLI to build, refresh, query, export, and serve a durable code/corpus knowledge graph. Use when the user wants .graphify/GRAPHREPORT.md, graph.json, graph.html, graphify update/summary/query/path/explain/tree, change-aware review context, git-hook or watch-based refresh, a stdio MCP graph server, or an install into jeo, jeopi, gjc, opencode, Claude, Codex, or Gemini. Also covers the honest structural fallback when native extraction is empty or misleading. Route simple locate/reference work to codebase-search, narrative knowledge-base work to llm-wiki, and project-memory handoff to opencontext. Triggers on: graphify, graphify update, graphify query, knowledge graph CLI, GRAPHREPORT.md, graph.json, codebase graph, graph refresh, graphify install, graphify serve, review context, affected flows.

data-analysis

akillness/jeo-skills

Analyze datasets to extract insights, identify patterns, and generate reports.

598 installs

code-refactoring

akillness/jeo-skills

Turn a cleanup packet into one behavior-preserving refactor brief. Use when simplifying a messy function/component/service, freezing behavior before touching fragile legacy code, splitting a cleanup-heavy diff into reviewable slices, or planning a repeated migration / codemod without changing intended behavior. Route diagnosis to debugging, review judgment to code-review, validation-program design to testing-strategies, bottleneck-led tuning to performance-optimization, and pure symbol inventory to codebase-search.

technical-writing

akillness/jeo-skills

Write internal technical documentation for engineers and operators: technical specs, architecture docs, ADRs, runbooks, migration plans, and developer-facing implementation guides. Use when the main job is capturing a technical decision, system boundary, operating procedure, or rollout path for builders and maintainers. Triggers on: tech spec, design doc, architecture doc, ADR, runbook, migration guide, implementation guide, rollout doc, operational guide, and internal technical writing. End-user onboarding guides, tutorials, FAQs, and help-center flows belong here too. Route API portals to api-documentation, release notes to changelog-maintenance, decks to presentation-builder, and GTM messaging to marketing-automation.

Docs & Writing544 installs

web-accessibility

akillness/jeo-skills

Routing-first skill for web accessibility remediation and verification. Use when the main job is classifying which accessibility surface is failing — semantics, keyboard/focus, labels/announcements, visual perception/reflow, media alternatives, or routed-app navigation feedback — and turning vague audit, WCAG, axe/Lighthouse, or "make this accessible" requests into one concrete remediation packet. Broad UI critique for hierarchy, polish, and launch readiness belongs here too. Route component API architecture and system governance to design-system, and responsive layout strategy to responsive-design.

Frontend & Design531 installs

Popular media & creative skills

View category →

hyperframes

heygen-com/hyperframes

Read first to make, edit, animate or render any video with HyperFrames (HTML rendered to video), including launch films, explainers, music videos, charts, maps, vertical clips, title cards, captions and overlays. Holds the render contract, the work loop and what each kind of video needs.

Media & Creative1.2M installs

media-use

heygen-com/hyperframes

Get or make any media for a HyperFrames video - music, sound effects, images, icons, logos, voiceover, avatar and generated video, transcripts, cutouts, colour grades and looks - with HeyGen or free local tools, and mix placed audio. Also for footage that looks dark, flat or dull, or should be stylized or hidden.

Media & Creative1.1M installs

hyperframes-registry

heygen-com/hyperframes

About 450 ready-made HyperFrames blocks and components installed as editable source - transitions, overlays, titles, kinetic type, captions, charts, map overlays, 3D, camera moves. Use it before hand-building any named visual (CRT scanlines, glitch, film grain, a chart); also for hyperframes add and catalog.

Media & Creative1M installs

hyperframes-creative

heygen-com/hyperframes

Non-animation creative direction for HyperFrames videos. Use for design spec (frame.md / design.md) handling, palettes, typography, narration, beat planning, audio-reactive visuals, composition patterns, and brand / style decisions. For atomic motion patterns and scene blueprints, use hyperframes-animation.

Media & Creative916.5K installs

ai-video-generation

101-skills/superpowers

Generate AI videos with Google Veo, Seedance 2.0, HappyHorse, Wan, Grok and 40+ models via inference.sh CLI. Models: Veo 3.1, Veo 3, Seedance 2.0, HappyHorse 1.0, Wan 2.5, Grok Imagine Video, OmniHuman, Fabric, HunyuanVideo. Capabilities: text-to-video, image-to-video, reference-to-video, video editing, lipsync, avatar animation, video upscaling, foley sound. Use for: social media videos, marketing content, explainer videos, product demos, AI avatars. Triggers: video generation, ai video, text to video, image to video, veo, animate image, video from image, ai animation, video generator, generate video, t2v, i2v, ai video maker, create video with ai, runway alternative, pika alternative, sora alternative, kling alternative, seedance, happyhorse

Media & Creative881.5K installs

ai-image-generation

101-skills/superpowers

Generate AI images with GPT-Image-2, FLUX, Gemini, Grok, Seedream, Reve and 50+ models via inference.sh CLI. Models: GPT-Image-2, FLUX Dev LoRA, FLUX.2 Klein LoRA, Gemini 3 Pro Image, Grok Imagine, Seedream 4.5, Reve, ImagineArt. Capabilities: text-to-image, image-to-image, inpainting, LoRA, image editing, upscaling, text rendering. Use for: AI art, product mockups, concept art, social media graphics, marketing visuals, illustrations. Triggers: flux, image generation, ai image, text to image, stable diffusion, generate image, ai art, midjourney alternative, dall-e alternative, text2img, t2i, image generator, ai picture, create image with ai, generative ai, ai illustration, grok image, gemini image, gpt image, openai image, chatgpt image

Media & Creative880.3K installs