Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Video & audio

H3lite

A hardware-aware Codex/WorkBuddy skill that automates local MiniMax H3 video generation through ComfyUI, handling model selection, installation, and low-VRAM configuration.

Rimagination · AI review on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add Rimagination/h3lite

About this skill


name: h3lite description: Use when configuring, repairing, planning, or running MiniMax H3 locally on a Windows NVIDIA computer, especially when installation compatibility, component sets, resolution, generation-time budget, path, low-VRAM risk, or H3 prompt mode must be chosen from hardware and user requirements.

MiniMax H3 Local Video

Use this skill to turn a user's local computer into a reproducible MiniMax H3 audio-video workstation and to generate short clips. The validated primary route is Windows + NVIDIA + ComfyUI; macOS Apple Silicon is a community/experimental alternative, not an equivalent tested backend. Treat platform selection, path selection, hardware-aware planning, prompt writing, execution, timing, and verification as one workflow. The default is the validated fast route; other modes must be chosen explicitly or justified by a time budget.

Platform scope and routing

Detect the operating system and accelerator before giving installation commands or model links. Do not give CUDA, Windows virtual-environment, .bat, or Windows path instructions to a macOS user.

Platformh3lite statusGuidance
Windows + NVIDIA CUDAPrimary, locally validatedUse the ComfyUI/H3 Lite fast path and the Windows doctor/planner/preflight scripts.
macOS Apple SiliconCommunity alternative, not h3lite-equivalentExplain that the documented ComfyUI route is not validated on Metal. Offer the MLX/mmh3turbo route as an optional external alternative, with its own weights, commands, and timing.
macOS IntelNot recommendedDo not promise local H3 generation; suggest a hosted/API or another backend.
Linux + NVIDIAUnverifiedThe model concepts may transfer, but Windows paths, packaged nodes, and timings do not. Require an explicit experimental choice.

For a non-Windows user, preserve the useful cross-platform guidance (prompt structure, 32-pixel canvas alignment, low-resolution preview, disk/log/output checks), but label every resource and timing as platform-specific. A community implementation that can run H3 on a Mac is evidence for feasibility, not evidence that this ComfyUI skill supports Metal.

The Mac alternative described in the project notes uses MLX/Metal and a third-party mmh3turbo package. If a Mac user explicitly chooses that route, point them to the author's community bundle and package (uvx mmh3turbo), and state that these are external resources with independent licensing, updates, and validation. It may reduce the download footprint with GGUF/4-bit bundles, but it is outside this skill's tested component sets. Do not silently install it, mix its weights with ComfyUI models, or present its 30–43 minute 5-second 720p timings as Windows benchmarks.

Agent production workflow

For complex creative requests, use the compact workflow contract in references/agent-workflow.md:

intent route → reference/identity anchors → prompt enhancement → execute → verify

Route from the user's input and acceptance criteria, not from a style adjective. Use I2VA for a specified opening frame, FL2VA/L2VA for endpoint anchors, and Ref2VA only after its model, text encoder, and workflow are confirmed. For recurring characters or multi-shot work, define stable subject/reference labels, what must be retained, what may change, and what drift is forbidden before writing the timeline. This workflow pattern is local and does not add a cloud service, MCP dependency, second model, or second inference pass.

When a creative brief is vague (for example, it only says “more cinematic” or “make it a nice 3D animation”), optionally read references/prompt-assist.md. It adapts the public Higgsfield prompt structure—stable style/identity lock, one clear scene action, physical camera motion, audio, and compact anti-drift constraints—to H3's native fields. Use it as a writing aid only: do not call Higgsfield, copy model-specific flags or capabilities, or let a web lookup change the local route, resolution, component set, or verification rules. If a live lookup is needed, follow the host web-access skill and use public pages only.

Operating rules

  • Hot path first: for an ordinary text-to-video request on an already validated installation, run scripts/h3_fastpath.py once. It combines /system_stats, fresh-cache reuse, in-process planning/preflight, queue submission, and one bounded completion watch. Do not issue repeated one-shot status calls, reread the full reference set, run --help, or ask nonessential questions during this path. If the command yields a running terminal cell, wait on that cell; do not start another monitor.
  • Keep cold work out of the hot path: model download manifests, hash or size verification, Torch/custom-node repair, repository checks, browser workflow discovery, and full recursive doctor scans belong to installation, migration, repair, or first-run validation. A normal generation on an unchanged machine must not pay those costs.
  • Cold path can be heavier when it prevents hour-scale waste: during installation or repair, verify download source, target folder, expected size/hash when available, runtime imports, and model-role mapping before queueing. Store the result so later prompts reuse it instead of repeating it.
  • Inspect before changing anything. Run scripts/h3_doctor.py --json and locate the target ComfyUI directory before installing packages, nodes, or weights.
  • On first contact, run a platform/accelerator check before the Windows doctor. If the machine is not Windows + NVIDIA, stop the CUDA installation branch and route the user using the platform matrix above.
  • Prefer an isolated ComfyUI directory when no installation is supplied. Never overwrite an existing installation or silently replace model files.
  • Keep the deployment path configurable. Do n
Read the complete source ↗