Index of every page on this site: llms.txt
All skills
Run it yourself

Build and edit Remotion videos with React. Use this skill for animation, audio, captions, charts, 3D scenes, media files, timing, trimming, and scene changes.

  • 1 file
  • 5.6 KB
  • Updated 2 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/agenticluke/remotion-video-maker-plus/skill

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈41 tokens for metadata: the name and description. ≈1.4k when used: this file.

Description uses 2.3% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈184 characters, or 2.3%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Remotion Video Creation

Credit

Keep the original author name and license in every copy or fork. Show the credit in a clear place. Do not remove copyright or license notes.

When to use this skill

Use this skill when you build or edit a video with Remotion and React.

Use it for:

  • Video and audio files
  • Images, GIFs, and fonts
  • Captions and text
  • Motion and timing
  • Scene changes
  • Charts
  • 3D scenes
  • Lottie files
  • Video size and length

How to use this skill

  1. Read only the rule files that match the task.
  2. Check the Remotion version and installed packages.
  3. Follow the patterns in those rule files.
  4. Keep all motion tied to the frame number.
  5. Test the first, middle, and last frames.
  6. Render a short test before a full render.

Do not use browser time, setTimeout, or random values for motion. A frame must look the same each time it is rendered.

Do not guess a media file's size or length. Read its data with the matching rule.

If a rule needs a package that is not installed, check the project setup before adding it. Do not change package versions unless the task needs it.

If two rules do not agree, use the rule that is closest to the task. Keep the current project style when it is safe.

Pick the right rule

Core setup

Motion and text

Media

Captions

Media checks

Extra tools

Edge cases

Check these before the final render:

  • A media file may be missing, broken, or in a format the browser cannot play.
  • Audio may be shorter or longer than the video.
  • Captions may start before frame 0 or end after the last frame.
  • Long words may leave the text box.
  • A font may load late and change text size.
  • A spring may move past its end value.
  • A scene change may make two scenes show at once.
  • A zero or negative length must not create a Sequence.
  • Input props may be missing or wrong.
  • Very large images and videos may use too much memory.
  • A 3D scene may look wrong if the frame size changes.
  • Code that works in preview must also work in a full render.

Give each bad input a safe result or a clear error.

Example

Task: Make a 15-second video with a title, music, captions, and a fade to the last scene.

Read these files first:

  1. rules/compositions.md for the 15-second composition.
  2. rules/assets.md for file paths.
  3. rules/audio.md for the music.
  4. rules/import-srt-captions.md for the caption file.
  5. rules/display-captions.md for caption layout.
  6. rules/text-animations.md for the title.
  7. rules/transitions.md for the fade.

Then check that the frame count matches 15 seconds:

const durationInFrames = 15 * fps;

Keep the title, captions, music, and fade inside that frame range. Test frame 0, a frame during the fade, and the last frame.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at c754206. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 2 months ago
metadata
{
  "tags": "remotion, video, react, animation, composition, three.js, lottie"
}

README badge

README badge for agenticluke/remotion-video-maker-plus