agentleFS
godot-fungodot-fun/godot-agent/.agents/skills/video-to-4k/SKILL.md

video-to-4k

Skill210 starsChanged 2 days agoMITView on GitHub

Upscales a single low-resolution video to 4K with Video2X (Real-ESRGAN), then encodes to unified 3840×2160 H.265 Main10 40Mbps + AAC 320kbps MP4. Source frame rate is preserved (no fps=60 duplication, no RIFE). Already-4K sources skip Video2X and go straight to FFmpeg. Use when the user wants video-to-4k, 4K upscale, UHD export, Video2X, Real-ESRGAN, H.265 Main10, or convert an SD/HD clip 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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    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 34
  2. Very specific:

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

    line 36
  3. Very specific:

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

    line 38
  4. Very specific:

    Use video2x (no .exe) or the AppImage path on Unix.

    line 65
  5. Distinctive:

    Use the bundled script only.

    line 113
  6. Very specific:

    Default model is general (realesrgan-plus).

    line 116
  7. Distinctive:

    Do not force fps. Keep the source frame rate.

    line 117

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

Convert a supported video to a unified 4K master:

SpecValue
Resolution3840×2160
Frame rateSource fps kept (no fps= filter, no RIFE)
VideoH.265 Main10 (libx265, yuv420p10le)
Video bitrate40 Mbps
AudioAAC 320 kbps
ContainerMP4 (.mp4, hvc1 tag)

Pipeline

  1. Probe with ffprobe (width, height, fps, audio).
  2. Already 4K? (width ≥ 3840 and height ≥ 2160) → skip Video2X.
  3. Below 4K → Video2X Real-ESRGAN upscale (scale 2 or 4) to intermediate under video-to-4k/upscaled/.
  4. Always FFmpeg final encode → video-to-4k/ at the unified specs above.

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-4k/ (final) and video-to-4k/upscaled/ (Video2X intermediate).
  • 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.

Setup (first run)

FFmpeg + Python

Populate ffmpeg and python under .dependency/ per dependency-manager.

Video2X (CLI)

Download the CLI release (not the Qt6 installer) from video2x releases and extract to .dependency/video2x/:

PlatformRelease asset
Windowsvideo2x-windows-amd64.zip → video2x.exe
LinuxVideo2X-x86_64.AppImage (or distro package) → register as bin

Register in .dependency/manifest.json:

"video2x": {
  "populated": true,
  "bin": ".dependency/video2x/video2x.exe"
}

Use video2x (no .exe) or the AppImage path on Unix. Requires a Vulkan GPU and AVX2 CPU. Docs: Command Line.

Quick Start

.dependency/python/python .ai/video-to-4k/convert.py --video path/to/clip.mp4

Example:

assets/video/clip.mp4
  → assets/video/video-to-4k/upscaled/clip.mkv   (Video2X, only if below 4K)
  → assets/video/video-to-4k/clip.mp4            (final master)

Already-4K source → only video-to-4k/clip.mp4 (FFmpeg only).

Anime / cartoon content (Real-ESRGAN anime model):

.dependency/python/python .ai/video-to-4k/convert.py --video clip.mp4 --anime

Defaults

SettingDefaultNotes
UpscalerReal-ESRGAN realesrgan-plusGeneral / live-action
--animerealesr-animevideov3Anime / illustration
ScaleAuto 2 or 4Smallest factor that meets or exceeds 4K
IntermediateHigh-bitrate HEVC MKV in video-to-4k/upscaled/Kept for re-encode; delete manually or --clean-upscaled
FinalAlways re-encodeEven if source already matches specs

Common Flags

--video · -o / --output · --anime · --gpu · --clean-upscaled

.dependency/python/python .ai/video-to-4k/convert.py --video clip.mp4
.dependency/python/python .ai/video-to-4k/convert.py --video clip.mp4 --gpu 0 --clean-upscaled
.dependency/python/python .ai/video-to-4k/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-4k/ (and video-to-4k/upscaled/ if used) outputs are; they swap assets manually.
  4. Default model is general (realesrgan-plus). Pass --anime for anime/cartoon.
  5. Do not force fps. Keep the source frame rate. Need 60fps interpolation → video-to-60fps first (RIFE at source resolution).
  6. Pipeline / FFmpeg / Video2X details: reference.md

Tests

From repo root:

.dependency/python/python .ai/video-to-4k/test_convert.py

Manual CLI examples: cli/video-to-4k.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.