From great-publishers
Compose great-filmmakers' render scripts into a single trailer-build pipeline. Reads a production doc (.veo3.md or .kling.md), runs the keyframe → image-to-video → assembly chain, surfaces engine choice and content-policy implications when the project genre signals it. Use when the production doc is ready and the project wants a finished trailer MP4 in one command instead of running the three render scripts manually.
How this skill is triggered — by the user, by Claude, or both
Slash command
/great-publishers:publishers-build-trailerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Build a finished trailer MP4 from a production doc.
Build a finished trailer MP4 from a production doc.
This skill is a thin orchestrator around great-filmmakers' three render scripts (scripts/render_keyframes.py, scripts/render_kling.py, scripts/render_veo.py), copied into the project by /filmmakers-project-init (v1.6+ of great-filmmakers). It:
.great-authors/project.md to determine genre and surface content-policy implications.film/screenplay/<slug>.veo3.md or <slug>.kling.md).render_keyframes.py → render_kling.py (image-to-video)render_veo.py (text-to-video)film/render/<slug>-trailer.mp4.The skill does not invent the engine choice or rewrite the production doc. If you need a different engine, run /filmmakers-crew --backend <name> first to regenerate the doc, then run this skill.
/filmmakers-crew and reviewed.scripts/render_*.py) have been copied into the project by /filmmakers-project-init (v1.6+ of great-filmmakers).~/.config/dev-secrets/secrets.env.Not for: the first render of a new project (run /filmmakers-crew and the individual render scripts manually first to validate); experimentation with engine choices (use the individual scripts directly with --only and --dry-run).
When this skill is invoked with a <project> argument (or no argument):
Resolve the project root the same way /publishers-build-book-site does. Verify .great-authors/project.md, film/, and scripts/render_*.py all exist. If any are missing, report and stop.
Read the bible for content-policy signals:
.great-authors/project.md — genre fieldLocate the production doc. Look for film/screenplay/<slug>.veo3.md or film/screenplay/<slug>.kling.md. Determine engine from filename. If both exist, ask the user which to use. If neither exists, report and stop with a recommendation to run /filmmakers-crew first.
Pre-flight: surface the content-policy implications.
For Veo (*.veo3.md):
<genre>. Veo content policy refuses prompts naming bodies, blood, violence, or weapons. Review <doc> for refusal-prone prompts before continuing — the render will fail mid-pipeline if any shot is rejected. Continue? (y/N)"For Kling (*.kling.md):
Verify API credentials are sourced:
GEMINI_API_KEY (or GOOGLE_API_KEY)KLING_ACCESS_KEY and KLING_SECRET_KEYOPENAI_API_KEYset -a && source ~/.config/dev-secrets/secrets.env && set +a
Run the keyframe pass (always, for both engines if the production doc has keyframes):
film/render/kling/keyframes/PROMPTS.md (the director's keyframe prompt set, generated by Hitchcock-persona or another visual director in great-filmmakers' pipeline)python3 scripts/render_keyframes.pyRun the engine-specific render:
python3 scripts/render_kling.py film/screenplay/<slug>.kling.mdpython3 scripts/render_veo.py film/screenplay/<slug>.veo3.mdAssemble the trailer:
film/render/<engine>/<shot-id>.mp4 for each shotffmpeg -f concat -safe 0 -i <concat-list> -c copy film/render/<slug>-trailer.mp4--only <shot-id>Report:
🎬 Trailer rendered.
Source doc: film/screenplay/<slug>.<engine>.md
Engine: <Kling 2.5 / Veo 3.0 Fast>
Shots: <N>
Total length: <M>s
Output: film/render/<slug>-trailer.mp4 (<size>)
Next:
- Review locally: open film/render/<slug>-trailer.mp4
- Embed in book site: copy into <project>-book/public/clips/<slug>-trailer.mp4
- Save trailer concept brief: /publishers-channel chip → "save as trailer concept"
This skill consumes great-filmmakers' artifacts. The dependency chain:
/filmmakers-crew <source> → produces .veo3.md or .kling.md production doc
/filmmakers-channel hitchcock → produces PROMPTS.md keyframe set (when image-to-video)
/filmmakers-project-init → copies render scripts into <project>/scripts/
/publishers-build-trailer → composes the renders into a finished trailer
If the user invokes this skill before any of those upstream pieces are in place, the skill reports what's missing and points them at the right upstream command. It does not try to substitute for them.
The pre-flight content-policy check is non-negotiable. Hitting MOVIO_PAYMENT_INSUFFICIENT_CREDIT or Veo's content-policy refusal mid-render after the user has already paid for half the shots is the worst outcome. Surface the risk before submission. The user should make an informed choice, not discover the constraint at render time.
/filmmakers-crew.--mixed-engine flag in v1.x.--only rather than this skill. This skill assumes a full-trailer build.cp film/render/<slug>-trailer.mp4 film/render/launch-trailer.mp4).npx claudepluginhub sethshoultes/great-minds-constellation --plugin great-publishersProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.