agentleFS
Sign inStart free
kiku-jwkiku-jw/codex-skills/video-render-run/SKILL.md

video-render-run

Skill0 starsChanged 4 months agoMITView on GitHub

Render and validate an MP4 from an existing `video-builder` spec JSON using the bundled Python pipeline. Use when a spec already exists and the job is actual rendering, not story or spec design.

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. Distinctive:

    Do not use when: the user still needs help designing the spec or choosing the input mode.

    line 10
  2. Very specific:

    Verify the spec path, required assets, fonts, and ffmpeg plus ffprobe availability before running the pipeline.

    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

Video Render Run

Metadata

  • Trigger when: a video spec JSON already exists and the task is to render and verify output.
  • Do not use when: the user still needs help designing the spec or choosing the input mode.

Skill Purpose

Take an existing spec, run the renderer deterministically, and validate the resulting MP4 instead of mixing render execution with preproduction planning.

Instructions

  1. Verify the spec path, required assets, fonts, and ffmpeg plus ffprobe availability before running the pipeline.
  2. Render with ~/.codex/skills/video-builder/scripts/render_video.py using python3 ~/.codex/skills/video-builder/scripts/render_video.py --spec /absolute/path/to/spec.json --out /absolute/path/to/out.mp4.
  3. Validate the MP4 with ffprobe or equivalent playback checks. Confirm duration, pacing, narration alignment, and whether the render is ready or needs one targeted fix.

Non-Negotiable Acceptance Criteria

  • A real spec path exists before rendering starts.
  • Missing dependencies, fonts, or assets are reported directly.
  • Validation covers output existence plus playback sanity, not just command success.
  • The skill does not silently rewrite the spec unless the task explicitly asked for repair.

Output

  • The spec path and rendered MP4 path.
  • A short validation note on duration, pacing, narration alignment, and any blocker.
  • Next skill options (only if needed): $video-spec-builder — repair or rebuild the spec when the current spec is incomplete or wrong.

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.

Check your setup, free