Terminal
Terminal/Skill
Produces narrated videos with several scenes, such as explainers, documentaries, and kids or fairy tale stories, with no visible presenter.
By Krea
Works with
npx skills add krea-ai/skills --skill faceless-videoCreate a coherent faceless video from a script, reusable visual assets, ordered
scenes, narration, and a verified final edit. This skill owns narrative and
production structure. Use the sibling krea-generate skill for live model
selection, model-specific prompting, and generation constraints.
Use this skill when the requested deliverable is a multi-scene production whose story is carried by an off-screen narrator or supplied narration. Topic alone is not enough: “make a video about Rome” is generic video generation unless the request also asks for a faceless channel, narrated explainer, documentary, storybook, picture story, or equivalent format.
Route elsewhere:
krea-generate.Resolve the real narration and post-production path before paid generation. A finished narrated video requires:
Separate model generations do not guarantee identical narrator identity, exact wording, or clean audio joins. If the user requires one locked voice and the available capabilities cannot provide it, explain that before spending and offer an ordered visual scene package.
Likewise, produce one assembled video only when the environment can actually combine and verify the clips and audio. Otherwise deliver the ordered clips, visual assets, script, and edit manifest, clearly labeled as a scene package. Never describe separate clips as a finished video.
Burn subtitles only when a real transcription or timestamp source is available. Do not estimate word timings from the script.
Collect only missing decisions:
For an ordinary production request, ask material questions together before generating. For an explicitly hands-off request, choose sensible defaults but state any narration or delivery limitation before the first paid generation.
For factual history, science, health, finance, or current-events scripts, research authoritative sources, retain their URLs, and cross-check important spoken numbers. Mark unsupported claims as unverified rather than filling gaps from uncertain memory.
Divide the total runtime into clip windows supported by the selected model. Ten-second blocks are a useful creative default, not a universal constraint.
Shape the story as hook → escalating build → turn → payoff:
For each block record its narration, location, required characters and props, through-line state, and timed shots. For a ten-second clip, three to five shots is a useful range; use proportionally fewer for shorter clips. Adjacent shots must change size or angle. Establish a location once, then return on coverage or detail rather than repeating the same wide shot.
Maintain an edit manifest containing:
Persist the manifest when the host supports durable files; otherwise keep it in working context. Never infer scene order from filenames, completion time, or a directory listing.
Write one reusable style formula describing medium, line or surface treatment, shading, palette, accent color, background treatment, depth, lighting, and motion character. Keep it non-photoreal unless the user asks otherwise. Translate named references into visible craft traits instead of imitating a living artist, studio, or brand.
Inspect supplied references before using them. Treat them as style donors unless the user owns and explicitly wants the depicted character. Do not copy logos, embedded text, or an identifiable real person's likeness without permission.
Create and inspect one style-sample vignette before producing the reusable asset set. Record its result and provenance before any dependent generation uses it.
Derive the smallest roster that covers the locked script:
Use the exact locked style formula throughout. Do not begin a dependent scene until every required asset has completed successfully, been inspected, and been recorded in the manifest. Prompt-only substitutes for missing characters, locations, or props create identity and style drift.
Default final scene generation to Seedance 2.5
(bytedance/seedance-2-5) when it is live and its current schema supports the
brief. Read ../krea-generate/references/models/seedance-2.md before writing
its prompts. Use a faster or cheaper model for explicitly economical drafts,
Seedance 2 when 4K is required, or another capable model when the references or
requested behavior are incompatible. Live model availability and schemas remain
authoritative.
Before an expensive run, present the scene count, seconds per scene, resolution, and retry allowance, then obtain approval unless the user already authorized that spend.
Generate blocks in manifest order. For each block:
Inspect each completed clip at the beginning, middle, and end. Reject the wrong aspect ratio, missing subjects, severe style drift, accidental speech, frozen openings, or broken continuity.
Retry only a terminal failure or a concrete manifest violation:
Record every attempt and defect in the manifest.
When assembly is available, normalize scene dimensions, frame rate, codecs, pixel format, and audio layout before concatenation. Preserve manifest order. For supplied narration, follow its approved scene timings without pitch shifting or speed changes; adjust visual timing instead. For native per-scene narration, verify every audio join when playback or audio inspection is available and state the limitation when it is not.
Verify the final media can be decoded and inspect the beginning, middle, end, and every scene boundary. Delivery passes only when:
Deliver either the verified final video or the explicitly labeled ordered scene package. Do not leave the user with raw job metadata as the deliverable.