agentleFS
godot-fungodot-fun/gai/.agents/skills/video-to-60fps/SKILL.md

video-to-60fps

Skill210 starsChanged 2 days agoMITView on GitHub

Interpolates a single video to 60fps with Video2X RIFE at source resolution. Already ~60fps files are skipped (nothing is written). Below 60fps uses RIFE, not FFmpeg frame duplication. Above 60fps drops to 60 with FFmpeg. Use when the user wants video-to-60fps, frame interpolation, RIFE, 24 to 60, 30 to 60, or convert fps to 60 before video-to-4k.

1 other project uses 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, 1 is distinctive, and 4 are 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.

  • 4

    Very specific

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

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

    When this skill applies, read and follow dependency-manager — run scripts as documented, install missing tools into .dependency/.

    line 36
  2. Very specific:

    Run convert.py through .dependency/python/python.

    line 38
  3. Very specific:

    Use the bundled script — do not hand-write equivalent video2x / ffmpeg commands.

    line 40
  4. Very specific:

    Do not use FFmpeg fps=60 duplication to fake 60fps on below-60 sources.

    line 42
  5. Distinctive:

    Use the bundled script only.

    line 92

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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 to 60fps

Convert a supported video to 60fps at the source resolution via Video2X RIFE. Run this before video-to-4k.

SpecValue
Frame rate60 FPS
ResolutionUnchanged
Already ~60fps (59.5–60.5, includes 59.94)Skip — no output file
Below 60fpsVideo2X RIFE interpolate, then snap to 60
Above 60fpsFFmpeg fps=60 drop (RIFE cannot reduce fps)
VideoH.265 Main10 (libx265, yuv420p10le, CRF 12)
AudioAAC 320 kbps when present
ContainerMP4 (.mp4, hvc1 tag)

Pipeline

  1. Probe fps with ffprobe.
  2. Already ~60? → skip (do nothing).
  3. Above 60? → FFmpeg drop to 60fps → video-to-60fps/.
  4. Below 60? → Video2X RIFE (-m integer multiplier) at source resolution → FFmpeg to exact 60fps MP4 → video-to-60fps/.

Rules

When this skill applies, read and follow dependency-manager — run scripts as documented, install missing tools into .dependency/.

  • Run convert.py through .dependency/python/python. Never use host python / ffmpeg / video2x.
  • Never overwrite sources. Outputs go under video-to-60fps/.
  • Use the bundled script — do not hand-write equivalent video2x / ffmpeg commands.
  • One file per run — pass --video with a single file; repeat for each clip in a batch.
  • Do not use FFmpeg fps=60 duplication to fake 60fps on below-60 sources.

Setup (first run)

Same Video2X CLI + FFmpeg + Python as video-to-4k. Populate ffmpeg, python, and video2x under .dependency/. Requires a Vulkan GPU and AVX2 CPU.

Quick Start

.dependency/python/python .ai/video-to-60fps/convert.py --video path/to/clip.mp4

Example:

assets/video/clip.mp4          (1280×720 24fps)
  → assets/video/video-to-60fps/clip.mp4  (1280×720 60fps)

Already-60fps source → no output file; log [skip].

Then upscale (fps kept):

.dependency/python/python .ai/video-to-4k/convert.py --video assets/video/video-to-60fps/clip.mp4

Defaults

SettingDefaultNotes
InterpolatorRIFE rife-v4.6Video2X -p rife
MultiplierAutoSmallest integer -m so src_fps × m is at least ~60
UHD modeAuto--uhd when width ≥ 1920
Already ~60fpsSkippedNo file written

Common Flags

--video · -o / --output · --rife-model · --uhd · --gpu

.dependency/python/python .ai/video-to-60fps/convert.py --video clip.mp4
.dependency/python/python .ai/video-to-60fps/convert.py --video clip.mp4 --gpu 0
.dependency/python/python .ai/video-to-60fps/convert.py --video clip.mp4 -o out/clip.mp4

Never overwrite source files. Input must be a single video file (--video), not a directory. Supported inputs: .mp4, .mkv, .mov, .avi, .webm, .wmv, .flv, .m4v, .mpeg, .mpg, .ts, .mts, .m2ts, .3gp, .ogv.

Agent Notes

  1. Use the bundled script only.
  2. Missing Python / FFmpeg / Video2X → populate .dependency/, set populated: true, retry the same command.
  3. Tell the user where video-to-60fps/ outputs are; they swap assets manually. Skipped ~60fps files have no output.
  4. Interpolate at source resolution, then video-to-4k. Do not 4K-upscale first.
  5. Video2X -m is an integer. 30fps → ×2 = 60. 24fps → ×3 = 72, then FFmpeg snaps to 60.
  6. Pipeline / FFmpeg / Video2X details: reference.md

Tests

From repo root:

.dependency/python/python .ai/video-to-60fps/test_convert.py

Manual CLI examples: cli/video-to-60fps.md

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.