agentleFS
frankxaifrankxai/awesome-motion-design-agent-skills/skills/remotion-video-agent/SKILL.md

remotion-video-agent

Skill111 starsChanged 12 days agoCC0-1.0View on GitHub

Use when creating or editing Remotion videos, programmatic explainers, motion graphics, MP4 renders, GIF renders, social cutdowns, or React-authored video templates.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. muzimu217/ui-design-agent-kit★ 23same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use Remotion helpers for interpolation, sequencing, audio, static files, and rendering.

    line 13
  2. Distinctive:

    Prefer MP4 for delivery. Use GIF only for previews or documentation.

    line 14
  3. Distinctive:

    Read current Remotion documentation and the relevant official Remotion skills before implementation.

    line 19
  4. Distinctive:

    Use frame ranges for the hook, explanation, demonstration, and final hold.

    line 21
  5. Distinctive:

    Do not render into an input asset or silently reuse a stale export.

    line 23
  6. Distinctive:

    No text cut off.

    line 37
  7. Distinctive:

    No scene timing dead air.

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Remotion Video Agent

Workflow

  1. Confirm the composition format: aspect ratio, duration, FPS, destination, and voice/music requirements.
  2. Break the video into scenes with frame ranges.
  3. Build scenes as React components with deterministic, frame-derived timing. Avoid wall-clock time, unseeded randomness, and network-dependent rendering.
  4. Use Remotion helpers for interpolation, sequencing, audio, static files, and rendering.
  5. Prefer MP4 for delivery. Use GIF only for previews or documentation.
  6. Render and inspect before final delivery. Name the composition, input props, source revision, output path, and render command actually used.

Implementation and recovery

  • Read current Remotion documentation and the relevant official Remotion skills before implementation. Use the existing project's compatible package versions; do not copy APIs from memory or upgrade dependencies as a side effect.
  • Preflight fonts, asset paths, duration metadata, codec, and output dimensions. Keep exact text as editable code.
  • Use frame ranges for the hook, explanation, demonstration, and final hold. Inspect first/last frames and scene boundaries, plus the finished playback.
  • Preserve a previous usable export until its replacement succeeds. On failure, retain the input props and error, repair the failing scene or asset, and retry within an explicit time/resource budget.
  • Do not render into an input asset or silently reuse a stale export. Check output existence, duration, dimensions, audio, and decode/playback before saying the render succeeded.
  • Provide captions where speech carries meaning and a useful poster or still sequence for viewers who cannot use motion. README previews need a static alternative and a link to a controllable video.
  • Confirm asset rights and current Remotion licensing for the intended use. This skill is workflow guidance; a renderer, paid service, and publication permission are separate requirements.

Useful Defaults

  • 30 FPS for general video.
  • 60 FPS only when motion quality requires it.
  • 1080x1920 for vertical social.
  • 1920x1080 for YouTube/demo.
  • 1200x630 or 1600x900 for launch preview loops.

QA

  • No text cut off.
  • No scene timing dead air.
  • Motion supports the script.
  • Assets are licensed or owned.
  • Audio levels are not clipped.
  • GIF exports are size-conscious.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.