agentleFS
neskuchnyneskuchny/content_factory/.claude/skills/video-code/SKILL.md

video-code

Skill1 starsChanged 2 days agoMITView on GitHub

Editing and motion graphics in code — assembling Reels from source footage with ffmpeg, subtitles, overlay labels, kinetic typography, carousels and covers via HTML, rendering with HyperFrames or Remotion. Use for all units with engine code.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    All texts, numbers and logos are in code.

    line 28
  2. Distinctive:

    Keep the project (HTML/composition) next to the final file — it is editable, the mp4 is not.

    line 31

≈ “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

Video and graphics in code

Tools (installed once, see docs/04-setup.md)

  • ffmpeg / ffprobe — cutting, joining, loudness, frames for checking.
  • HyperFrames (npx skills add heygen-com/hyperframes) — HTML + GSAP → MP4. The main motion-graphics tool: free license, has /media-use for voiceover, music and sounds.
  • Remotion (npx skills add remotion-dev/skills) — React templates driven by data. A company of 4 or more people needs a commercial license.
  • Playwright — HTML → PNG for carousels, covers, Stories.

Typical Reels from real footage

  1. Take the moments from media-index/moments.md according to the script.
  2. ffmpeg: cut by timecodes, 1080×1920, loudness normalization (loudnorm, −14 LUFS).
  3. Subtitles from speech (whisper → words) in the style of brand/visual.md; hook text in the first 1–2 s.
  4. Overlay labels (solution name, CTA) — from a template in brand/templates/.
  5. Final render. 3–4 frames for self-checking: ffmpeg -vf fps=1/3.

Carousels and covers

HTML template from brand/templates/ → data from the script → a Playwright screenshot of each slide (1080×1350). After rendering, look at the PNGs yourself and check line wrapping, cropping, legibility.

Rules

  • All texts, numbers and logos are in code; use fonts that cover the script of the client's language (for ru clients: Cyrillic).
  • 9:16 safe zones: put nothing important in the top 250 px or the bottom 400 px.
  • Keep the project (HTML/composition) next to the final file — it is editable, the mp4 is not.

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.