by igorls
A timeline video editor for MiniMax H3 inside ComfyUI: write shots, render them on your own GPU, cut picture and sound together, or let an agent make the video.
# Add to your Claude Code skills
git clone https://github.com/igorls/comfyui-h3-editorGuides for using ai agents skills like comfyui-h3-editor.
See how comfyui-h3-editor compares with popular alternatives.
comfyui-h3-editor is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by igorls. A timeline video editor for MiniMax H3 inside ComfyUI: write shots, render them on your own GPU, cut picture and sound together, or let an agent make the video. It has 58 GitHub stars.
comfyui-h3-editor's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/igorls/comfyui-h3-editor" and add it to your Claude Code skills directory (see the Installation section above).
comfyui-h3-editor is primarily written in Python. It is open-source under igorls on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh comfyui-h3-editor against similar tools.
No comments yet. Be the first to share your thoughts!
Available after the catalog security scan passes.
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
A timeline video editor for MiniMax H3, inside ComfyUI. Write your shots, render them on your own GPU, and cut them together, picture and sound.
Project site: watch a cut made with it, shot by shot.

Everything else needs no other custom node pack.
You need a recent ComfyUI with its built-in MiniMax H3 support: 0.43 or newer.
The pack is tested on 0.44. In ComfyUI's custom_nodes folder:
git clone https://github.com/igorls/comfyui-h3-editor
pip install -r comfyui-h3-editor/requirements.txt
On the Windows portable build, run the second step as
..\python_embeded\python.exe -m pip install -r comfyui-h3-editor\requirements.txt.
The requirements bring ffmpeg, for importing and exporting video, and the gguf
reader for HyperFlow's GGUF models.
Restart ComfyUI. H3 Editor appears in the sidebar.
The pack does not download models. These are the ones a first video needs, about 54 GB:
| File | Folder | Size | Where to get it |
|---|---|---|---|
qwen3vl_32b_minimax_h3_nvfp4_awq.safetensors |
models/text_encoders |
15.7 GB | Comfy-Org/MiniMax-H3, text_encoders/ |
minimax_h3_video_vae_fp16.safetensors |
models/vae |
5.2 GB | Comfy-Org/MiniMax-H3, vae/ |
minimax_h3_audio_vae_fp32.safetensors |
models/vae |
0.6 GB | Comfy-Org/MiniMax-H3, vae/ |
minimax_h3_ref2va_hyperflow_flash_14b-int8_convrot.safetensors |
models/diffusion_models/hyperflow |
16.4 GB | VideoRebirthAI/hyperflow-h3-flash, ref2va_int8_convrot_comfyui/ |
minimax_h3_fl2va_hyperflow_flash_14b-int8_convrot.safetensors |
models/diffusion_models/hyperflow |
16.0 GB | VideoRebirthAI/hyperflow-h3-flash, fl2va_int8_convrot_comfyui/ |
HyperFlow's model page recommends these INT8 files on RTX GPUs with 24 GB or
more. On a smaller GPU, take its GGUF files in their place, from Q8_0 at 15.2 GB
down to Q3_K_M at 7.2 GB, anywhere in models/diffusion_models; see
models and quality.
The text encoder and the video VAE also come in other precisions in the same
repository: qwen3vl_32b_minimax_h3_int8_convrot.safetensors (25 GB) and
qwen3vl_32b_minimax_h3_bf16.safetensors (48 GB), and
minimax_h3_video_vae_int8_convrot.safetensors (2.6 GB). Any one of each is
enough: the editor renders with what it finds, and with more than one installed
you pick in the Project tab. A Qwen3-VL 4B or 8B can also stand in for the 32B text
encoder, in about a third of the memory: see
a smaller text encoder.
These are optional, and worth having:
| File | Folder | Size | Where to get it | For |
|---|---|---|---|---|
minimax_h3_latent_upscaler_3d_conv_v1_bf16.safetensors |
models/latent_upscale_models |
0.7 GB | LBH-123-AI/Minimax_h3_latent_Upscaler | Finals at up to 1920 pixels |
MMH3-Realism-V2.safetensors |
models/loras |
71 MB | Civitai model 3041489 | Natural skin in finals |
taeh3.safetensors |
models/vae_approx |
23 MB | OzzyGT/taeh3 | The moving live preview |
Other H3 checkpoints work as well; see models and quality.
h3take_projects/<project>/exports.The panel on the right. Select a clip and it shows the clip in tabs: Shot for what happens, the cast, sound and model, Takes for its renders, and Timeline for its speed and transition. The Project tab is always there, with the look, format, model and LoRAs that every clip shares. Esc selects nothing.
Clips and takes. Every render of a clip is a take with its own seed and the
prompt that made it. Run the pointer across a take's picture to look through
it, flip between takes with [ and ], keep a seed to render variations of
one result, or restore a take's prompt. Rendered clips stay on disk: moving,
trimming or splitting them never renders anything again. Render all drafts
renders every clip that has no take yet, the ones that share a model one after
another.
Cast and voices. Add in the Cast panel adds a reference picture or a voice. Choose who is in each clip, and write @Name in What happens to place them, or drag their card into the text. Write @Name in Who speaks to use their voice. A voice can be uploaded, or taken from a clip on the timeline.
The cast catalog. Press Save beside Catalog on a cast member to keep them for every project, with their pictures and voice. In another project, Add, From the catalog brings in a copy. When you change someone and save them to the catalog again, the other projects show Newer in the catalog with an Update button, or you can bring every project up to date at once from the catalog. A copy you changed in its project is never overwritten without you.
Joining shots. Select a clip on the timeline, open Generate and choose Extend forward or Extend back to generate what happens next or before. Bridge to next generates what leads from it into the following clip, landing on a short run of its first frames, and Bridge into its movement holds more of them, for a following clip that starts in mid-movement. Merge with next replaces the join between two clips with a generated crossing. These clips hold 39 real frames and their sound from the clips they join, so the cut does not show. If a clip they join changes, they are marked: render them again. An empty space between two rendered clips shows a plus that generates the bridge.
First and last frames. Give a clip an exact first or last frame by dropping a picture on it, uploading one, or using the frame at the playhead, with the buttons beside each frame in the Shot tab.
Picture to a track. A clip can hold a recorded sound, and its picture is generated to it. Extend forward carries on with the next part of the same track, so a long talking performance can be built from short shots.
Your own footage. Import brings in a video or a picture, fitted to the project's format. You can trim it, and extend or bridge from it like a