Higgsfield Video Explainer

# Higgsfield Video Explainer

Run the MCP video-explainer workflow through Higgsfield CLI. Lock one visual style key, write one narration line and one matching visual prompt per 10-second block, generate every voice take first, generate every clip second, then immediately assemble the ordered pairs with `explainer_video`.

Never use the monolithic `video_explainer` job in this skill.

## MCP-to-CLI mapping

| MCP workflow operation | CLI equivalent | |---|---| | `get_explainer_presets` | `higgsfield preset list video-explainer --json` | | `resolve_explainer_preset` | `higgsfield preset resolve video-explainer <preset_id> --json` | | `generate_image` / `nano_banana_pro` | `higgsfield generate create nano_banana_2 ...` | | `list_voices` | `higgsfield voices list --json` | | `generate_audio` / `seed_audio` | `higgsfield generate create seed_audio ...` | | `generate_video` / `gemini_omni` | `higgsfield generate create gemini_omni ...` | | `job_status` | `--wait --json` or `higgsfield generate wait <job_id> --json` | | `explainer_video` | `higgsfield generate create explainer_video ...` |

`nano_banana_2` is the public CLI id for the Nano Banana Pro style-key model used by the MCP workflow.

## Bootstrap

1. If `higgsfield` is unavailable, install it:

```bash curl -fsSL https://raw.githubusercontent.com/higgsfield-ai/cli/main/install.sh | sh ```

2. If `higgsfield account status` fails, ask the user to run `higgsfield auth login`, then wait. 3. Inspect the live contracts before the first submission:

```bash higgsfield model get nano_banana_2 higgsfield model get seed_audio higgsfield model get gemini_omni higgsfield model get explainer_video ```

## Phase 0 — ask first

Collect choices in two separate turns, in this order. Never merge them.

### Turn 1 — style only

Always load the live CMS catalog:

```bash higgsfield preset list video-explainer --json ```

Show the preset names with their thumbnail/video preview URLs. Say one short line asking the user to pick a preset, describe a custom style, or attach style-reference images, then end the turn. Do not ask production questions in the same turn. Choosing a style is mandatory; never choose silently unless the user explicitly says “you choose.”

Skip this turn only when the request already contains `explainer preset id: <uuid>`. Confirm that UUID exists in the live catalog and keep it for Phase 1.

### Turn 2 — production settings

Only after style selection, collect every unresolved setting:

- Duration: one to ten whole minutes. `N = duration_minutes × 6` fixed 10-second blocks. - Narration language: English by default, but still offer the choice. - Character: recurring mascot or faceless stylistic scenes. Always ask. - Aspect: `16:9` by default or `9:16` vertical. - Subtitles: off by default. Explain that subtitles cost 0.05 credit per voiced block. If enabled, make the user choose `patrick`, `caveat`, `marker`, or `anton`; never choose silently.

Every choice belongs to the user unless they explicitly delegate it.

## Inputs

- Topic or personal/philosophical story. - Optional local source documents; read/extract them before scripting. They are factual input, not generation media. - Optional preset UUID, mutually exclusive with custom style-reference images. - Optional style-reference images. Use only their rendering style and color grading; never copy their people, text, logos, or objects unless requested. - Duration, language, character mode, aspect, and subtitle choice from Phase 0.

For local style donors, pass each path with a repeated `--image`. For a web image, download it locally first or use an existing uploaded media ID.

## Hard rules

- Keep every visual strictly non-photorealistic. Repeat the same STYLE descriptor and non-realism negatives in every clip prompt. - Keep all spoken words out of video generation. Clip audio is ambient sound or music only; no dialogue, lip-sync, or baked narration. - Use exactly one narration take and one clip per labeled block. Block N audio always maps to Block N video. - Attach the same style-key image to every clip. - Write all image/video prompts in English. Only narration uses the selected language. - Research real topics before scripting. Do not invent quotes, dates, numbers, or events. - Assemble automatically in the same run. Returning loose clips is a failure.

## Pipeline

| Phase | Output | CLI | |---|---|---| | 0 Ask | style first; then duration, language, character, aspect, subtitles | `preset list` + user questions | | R Research | verified facts and sources | available research tools | | 1 Style key | one universal style image | `preset resolve` or `nano_banana_2` | | 2 Narration | N labeled narration lines | reasoning | | 3 Block prompts | N labeled video prompts | reasoning | | 4 Voice | user selects one voice; generate N takes | `voices list` + `seed_audio` | | 5 Clips | generate N 10-second clips | `gemini_omni` | | 6 Assemble | one final MP4 | `explainer_video` |

Re