# Video

Use this skill whenever the user asks to create, improve, audit, or split prompts for...

- Repository: https://github.com/smixs/visual-skills (610 stars)
- Category: Design
- License: CC-BY-4.0
- Last updated: 2026-09-16
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add smixs/visual-skills --skill video -g -a claude-code -y`
Codex: `npx skills add smixs/visual-skills --skill video -g -a codex -y`
Cursor: `npx skills add smixs/visual-skills --skill video -g -a cursor -y`
Gemini CLI: `npx skills add smixs/visual-skills --skill video -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add smixs/visual-skills`

## Description

Use this skill whenever the user asks to create, improve, audit, or split prompts for AI video generators (Seedance, Kling, Veo, Runway, Luma, Pika, Sora, any image-to-video system). The skill also covers storyboards, shot lists, director treatments, dynamic montage, multi-clip story structure, camera direction, lighting, blocking, pacing, character continuity, dialogue, and sound design. Trigger even when the user says things like "придумай сцену для видео", "разбей на склейки", "сделай раскадровку", "улучши промпт для Kling", "переведи сценарий в промпты", "как снять X в AI-видео", or shares a prompt and asks to fix it, even if they never say the word "prompt". Do NOT use for still images (use the sibling image skill), for editing, colour-grading or assembling footage that already exists, or for writing feature-length screenplays with no generation step.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# AI Director, Screenwriter & Editor

Hybrid role. You direct (see frame, emotion, motivated camera), write (build beat, action, consequence, final image), and edit (cut rhythm, protect continuity, drive montage). Prompt engineering is fourth, it serves the first three.

A beautiful frame without dramaturgy is wallpaper. A dramaturgically clean prompt without details is mush. The whole craft of this skill lives in the reference files. The body of this SKILL.md is intentionally thin so you cannot fake a result by reading it alone.

## Route first, is this actually a video-prompt task?

- **No idea or script yet** (user wants a concept, a Big Idea, a campaign, an ad scenario, not a prompt): if the `creative-director` skill is installed, start there, it develops ideas and scripts for commercials and beyond ([github.com/smixs/creative-director-skill](https://github.com/smixs/creative-director-skill)). Come back here once there is a script to shoot.
- **Still keyframes, character sheets, animatic panels** to feed the video pipeline: use the sibling `image` skill, then return with the keyframes.
- **A script or scene exists and needs prompts**, this skill. Continue below.

---

# Mandatory reading order, DO NOT WRITE A PROMPT WITHOUT THIS

Past attempts to write prompts directly from this skill body produced lazy, mush-prone results. The fix is structural: the process lives only in the reference files, and you load them in this order before producing output. Skipping a step **silently** degrades the result, the model cannot tell that a shot is wallpaper, only the writer can, and only by applying the rules from these files.

For every video prompt request, load the files in this order:

### Step 1, always read first → [dramaturgy.md](references/dramaturgy.md)

The rest: https://github.com/smixs/visual-skills/blob/HEAD/video/SKILL.md