higgsfield-shotlist-director

Converts briefs and scripts into a connected Seedance 2.0 shotlist as a single editable HTML artifact.

Updated Jul 15, 2026
One-click install
npx skills add https://github.com/executiveusa/buffer-blaster- --skill higgsfield-shotlist-director-executiveusa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: higgsfield-shotlist-director
Source: https://github.com/executiveusa/buffer-blaster-/tree/main/skills/higgsfield/skills/higgsfield-shotlist-director
Command: npx skills add https://github.com/executiveusa/buffer-blaster- --skill higgsfield-shotlist-director-executiveusa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a script or brief into dozens of separate video prompts loses continuity: characters drift, styles diverge, and edits must be repeated in every prompt. This Skill produces one connected director's shotlist where a global style prefix and an @-asset glossary keep every per-scene prompt in sync. ## Core Features & Use Cases - Single HTML deliverable: Generates one self-contained shotlist.html with a collapsible global Style Prefix, an @-asset glossary, and named per-scene prompts (1a, 1b, 2a) with copy buttons and progress checkboxes saved in localStorage. - Structured prompt law: Every prompt follows the Style → Characters → Scene → CUT 1..N form targeting 15 seconds, with density heuristics for grouping or splitting beats, tempo budgeting, and a monotony audit across the whole sequence. - Edit-once propagation and preflight linting: Style prefix edits propagate to all prompts, per-scene overrides are supported, and each prompt is validated with the seedance_lint.py preflight linter before delivery. - Use Case: Paste a 60-second ad script and ask for a director's shotlist; receive an HTML file with numbered scenes, continuity-carrying prompts, and checkboxes to tick off as you generate each clip in Seedance. ## Quick Start Turn this script into a director's shotlist for Seedance 2.0 with a global style prefix and per-scene 15-second prompts.

Frequently Asked Questions about higgsfield-shotlist-director

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a script into Seedance 2.0 prompts?

Provide the brief or script and ask for a director's shotlist. The Skill breaks it into numbered scenes, writes each as a 15-second prompt in Style → Characters → Scene → CUT form, and delivers everything as one editable HTML file with copy-ready prompt blocks.

How do I keep character and style consistency across many video prompts?

The shotlist locks a global Style Prefix applied verbatim to every prompt and declares recurring cast, props, and locations once in an @-asset glossary with fidelity grades. Multi-state variants like a sweaty post-run hero get their own locked glossary entry to prevent face drift.

Can I edit one scene or change the style across the whole shotlist?

Yes. Asking to change the style prefix propagates it to every prompt in one pass, while a per-scene override lets a single scene break the global look. The same HTML file is re-rendered with numbering preserved so checkbox progress in localStorage survives.

How long should each Seedance prompt be in a shotlist?

Each prompt targets a 15-second clip holding one to three cuts, and longer scenes split into named chunks like 3a, 3b, 3c. When beats genuinely fill only 4-8 seconds, a deliberately shorter clip is generated rather than padding dead air.

What checks run before the shotlist is delivered?

Every prompt passes through the seedance_lint.py preflight linter in block regime to catch real names, brand or IP issues, and invalid parameters. The full sequence also gets a tempo budget check that cut durations sum to the runtime and a monotony audit against repeated framing.