kinema

Orchestrates topic-to-finished-video production through scripted storyboard, image, voice, and assembly stages.

131|10|Updated Aug 14, 2026
One-click install
npx skills add https://github.com/chillzhuang/Kinema --skill kinema-chillzhuang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kinema
Source: https://github.com/chillzhuang/Kinema/tree/main/.claude/skills/kinema
Command: npx skills add https://github.com/chillzhuang/Kinema --skill kinema-chillzhuang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Producing short-form video with AI normally means juggling separate tools for copywriting, storyboarding, image generation, voiceover, subtitles, animation, and final assembly, with character and scene consistency easily lost between sessions. This Skill turns a topic into a finished short video through one deterministic pipeline where assets stay reusable, traceable, and versioned across an entire series. ## Core Features & Use Cases - End-to-end production state machine: Guides copywriting, storyboard linting, character/prop/scene reference sheets, image generation, voice casting and TTS, animatic review, video generation, and final assembly, with mandatory human confirmation at each starred node. - Three render modes and multi-aspect output: Supports kenburns (zero-cost stills), dubbed (fixed-voice lip-synced image-to-video), and native (model-native audio-video) modes across 16:9, 9:16, and 1:1 canvases. - Consistency and cost guardrails: Enforces reference-sheet binding for characters and scenes, dry-run cost review before any paid video generation, review/version-stack management, and pre-delivery lint, verify, and consistency checks. - Use Case: Give it a topic like a book review or a short drama episode; it produces the script, shot list with bilingual prompts, character sheets, storyboard images, voiceover, subtitles, and a finished assembled video under a single project directory. ## Quick Start Ask the agent to turn your topic into a short video, for example: "Use kinema to make a 60-second narrated video about the Pomodoro Technique, starting with the script and storyboard for my review."

Frequently Asked Questions about kinema

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

FAQPage Schema
How do I turn a topic into a finished short video with AI?▼

Create a project and chapter with the kinema CLI, then follow the staged workflow: script and storyboard, reference sheets, image generation, voiceover, assembly, and optional video animation. Each stage pauses for your confirmation before spending money on generation.

What render modes does the video pipeline support?▼

Three modes: kenburns renders still images with camera moves at zero video API cost, dubbed generates image-to-video clips with fixed-voice lip-synced narration, and native uses the video model's native audio-video generation for on-screen dialogue.

How does it keep characters consistent across shots?▼

Characters, props, and scenes get registered reference sheets generated once per project, and the engine automatically attaches those sheets to every shot that names them. A consistency scan then pairs representative frames against the sheets for human verdicts.

Can I control costs before generating paid video clips?▼

Yes. Every paid video generation requires a dry-run first, which lists per-shot prompts and price quotes for your approval. 4K resolution and over-budget runs additionally require explicit authorization flags that the agent will not add on your behalf.

What aspect ratios and platforms does it support?▼

It outputs 16:9 landscape by default, plus 9:16 vertical and 1:1 square, with per-aspect safe-area composition rules and subtitle placement. Platform templates for Douyin, Kuaishou, Bilibili, and others preset style, ratio, and episode specs.

Why does the workflow stop between production stages?▼

Each starred node delivers reviewable artifacts and waits for confirmation so mistakes are caught before they cost money downstream. Only an explicit --auto request runs the full pipeline end to end, and even then budget and release authorizations still apply.