agentleFS
badgidsbadgids/Story-Film-Skills/skills/programmatic-video/SKILL.md

programmatic-video

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Create portable frame-deterministic programmatic video compositions and optionally translate them into a Remotion project for complex motion graphics, explainers, maps, kinetic typography, data-driven video, and reusable campaign templates.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Write 05_post/programmatic/compositions.json using stable COMP-### IDs and project-relative assets.

    line 12
  2. Distinctive:

    Keep timing in frames or exact seconds derived from declared FPS.

    line 13
  3. Very specific:

    Use scripts/remotion_adapter.py scaffold only when Remotion is a useful implementation target.

    line 14
  4. Distinctive:

    Do not bundle Remotion or assume the user is license-eligible.

    line 15
  5. Distinctive:

    When rendering is requested, require an installed/configured Remotion runtime and explicit license acknowledgement before invoking it.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Programmatic Video

  1. Read ../../references/PROGRAMMATIC_VIDEO.md.
  2. Write 05_post/programmatic/compositions.json using stable COMP-### IDs and project-relative assets.
  3. Keep timing in frames or exact seconds derived from declared FPS.
  4. Use scripts/remotion_adapter.py scaffold only when Remotion is a useful implementation target.
  5. Do not bundle Remotion or assume the user is license-eligible.
  6. Preserve user edits to generated code on later passes.
  7. When rendering is requested, require an installed/configured Remotion runtime and explicit license acknowledgement before invoking it.
  8. Register the final render in the media registry and QC it.

Done when the portable composition exists and any requested renderer-specific implementation has been generated or truthfully blocked.

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.