Agent skill

Stage Consistency

by Orkas-AI in Orkas-AI/Orkas-VideoStudio

Multi-shot narrative & character consistency — a character bible with a locked front-portrait anchor, view-matched reference selection, recent-frame carry-forward, Cameo (a user photo as the lead)…

MITAuto-check passedMedia & Creative

Install Stage Consistency

skills CLI
$ npx skills add Orkas-AI/Orkas-VideoStudio --skill stage-consistency -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Orkas-AI/Orkas-VideoStudio stage-consistency --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Orkas-AI/Orkas-VideoStudio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/skills/stage-consistency .claude/skills/stage-consistency && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
stage-consistency
GitHub stars
499
Token cost
~1.8k tokens
SKILL.md length
916 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
MIT

At a glance

Multi-shot narrative & character consistency — a character bible with a locked front-portrait anchor, view-matched reference selection, recent-frame carry-forward, Cameo (a user photo as the lead)…

  • Works in 6 steps: Character bible (extract once, lock the… → Portrait anchor (generate once, then LOCK) → Storyboard with character binding → …
  • Top of the generation line when the SAME character must look the same across many shots/scenes
  • SKILL.md covers 1. Character bible (extract…, 2. Portrait anchor (generate…, 3. Storyboard with character… and 4. Per-shot reference…, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Stage Consistency is an agent skill from Orkas-AI/Orkas-VideoStudio. Multi-shot narrative & character consistency — a character bible with a locked front-portrait anchor, view-matched reference selection, recent-frame carry-forward, Cameo (a user photo as the lead), and global planning for long scripts/novels. Trigger on top of the generation line when the SAME character must look the same across many shots/scenes, or for long-form story→video; do NOT trigger for one-off single-shot generation.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Media & Creative, covering Creative writing and fiction and AI video generation. The repository describes itself as: Turn your coding agent into a video studio: describe a video in plain language, and your agent writes the timeline and produces the file. The licence is MIT.

When your agent uses it

  • Top of the generation line when the SAME character must look the same across many shots/scenes
  • For long-form story→video
  • Do NOT trigger for one-off single-shot generation

Example prompts

  • “/stage-consistency”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Character bible (extract once, lock the look)
  2. Portrait anchor (generate once, then LOCK)
  3. Storyboard with character binding
  4. Per-shot reference selection (the core consistency mechanism)
  5. Carry-forward (continuity between shots)
  6. Long script / novel → movie (global planning first)

What it can do on your machine

Read from SKILL.md and the folder at commit c0c3c3e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are json).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Stage Consistency loads about 1.8k tokens when it runs. Until then it costs about 112 tokens; SKILL.md has 916 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~112
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Orkas-AI/Orkas-VideoStudio at commit c0c3c3e, republished under its MIT licence (© Orkas-AI). 916 words, ~1,770 tokens.

Download SKILL.mdSave it as .claude/skills/stage-consistency/SKILL.md (or your agent's skills folder).
name
stage-consistency
description
Multi-shot narrative & character consistency — a character bible with a locked front-portrait anchor, view-matched reference selection, recent-frame carry-forward, Cameo (a user photo as the lead), and global planning for long scripts/novels. Trigger on top of the generation line when the SAME character must look the same across many shots/scenes, or for long-form story→video; do NOT trigger for one-off single-shot generation.

stage-consistency

How to keep characters, settings, and style consistent across many generated shots (and across scenes in a long story). This is the depth layer on top of the generation line: the generation line makes clips; this skill makes the SAME character look the same in every clip. Describe the outcome; the tools are ovs image for portraits (incl. reference-image editing), ovs video for image-to-video, ovs edit extract-frame to pull an anchor frame, and a long-document strategy (chunking + retrieval/RAG over the source) for long sources (or the equivalent MCP tools).

1. Character bible (extract once, lock the look)

From the script/idea, extract every recurring character into project/characters/bible.json. For each character separate:

  • static features — the immutable visual identity: face, hair, body shape, ethnicity, age range. These NEVER change shot-to-shot.
  • dynamic features — changeable: clothing, accessories, expression.
  • a single canonical name (merge every alias/pronoun for the same person to one id).
json
{
  "alice": {
    "static": "early-20s East-Asian woman, oval face, long black hair, slim build",
    "dynamic": "green linen dress, small gold earrings",
    "portrait": { "front": "characters/alice_front.png", "side": "characters/alice_side.png", "back": "characters/alice_back.png" }
  }
}

2. Portrait anchor (generate once, then LOCK)

For each character, generate ONE front portrait (full-body, front view, plain background) from its static+dynamic features with ovs image. This is the anchor — never regenerate it. Derive side/back views by reference-image editing the front portrait (so all three views are the same person). Save paths into the bible.

  • Cameo (the user uploads a photo to BE a character): use that photo AS the front portrait — skip generation for that character. Everything downstream references it.

3. Storyboard with character binding

Decompose the script into shots. Each shot records:

  • which characters are visible (and at what camera angle — front / side / back),
  • a first-frame description and the motion,
  • describe motion by VISUAL FEATURES, not names — write "the figure in the green dress turns to the figure in the blue shirt", NOT "Alice turns to Bob". (Generators ground on appearance, not names.)

4. Per-shot reference selection (the core consistency mechanism)

For each shot, before generating it, assemble the reference images and bind them explicitly:

  1. Candidates = for every visible character, the portrait view that MATCHES the shot's camera angle (front shot → front portrait, profile → side portrait) plus the most recent already-generated frame that shares this scene/camera.
  2. Priority: a recent prior frame of the same camera > an older frame > portrait-only; same-camera > different-camera. Keep relative positions (if a character was on the left, keep them on the left). Don't pick two references that show the same face.
  3. Explicit binding: write a generation prompt that maps each reference to what it's for — "ref 1 (front portrait) → facial features & hair; ref 2 (previous frame) → lighting & background".
  4. Generate the shot with ovs video image-to-video using those reference images.

4b. Verify the keyframe BEFORE you pay to animate

For a character-critical shot, generate the first-frame image first (cheap), check it, and only then drive the video from that locked frame — catching drift at the still is far cheaper than discovering it after paying to animate.

  • Check the keyframe against the bible on the identity axes, in priority order: 1) character — gender, age, ethnicity, facial features, body shape, hairstyle; 2) spatial — relative positions/perspective match the reference (left stays left); 3) accuracy — matches the shot's description. Read it yourself if multimodal; if you cannot see images, mark it unverified and lean harder on a strong locked reference.
  • Re-roll the cheap image, not the expensive video, until it matches; generate a few candidates and keep the most consistent one. Never hard-fail — pick the best and note its shortcoming.
Show full SKILL.md (353 more words)Show less

5. Carry-forward (continuity between shots)

After a shot is generated, pull its representative frame with ovs edit extract-frame (e.g. its last frame) into project/frames/. That frame becomes a high-priority reference for the NEXT shot in the same scene — this is what carries lighting, composition, and the exact current look forward, so drift doesn't accumulate.

Cache the decision, not just the pixels. Record each shot's chosen references + the binding prompt (e.g. in the plan/segment) alongside the produced frame. A resumed run then reuses the SAME references and prompt and reproduces the same frame, instead of re-rolling the selection and silently drifting from the earlier run.

6. Long script / novel → movie (global planning first)

For long-form, plan globally BEFORE generating:

  1. Chunk the source; for a very long novel, use a long-document strategy (chunking + retrieval/RAG over the source) and retrieve the relevant chunks per event instead of holding it all at once.
  2. Extract events → scenes; extract characters per scene.
  3. Merge characters so the bible is global: same person across scenes → one entry (track the name variant each scene uses); same name but conflicting static features (e.g. a child vs. the adult years later) → split into two characters. New character → append.
  4. Carry the ONE global bible (locked portraits) through every scene, so a character looks identical across the whole story.

Default scope caps (cost control)

A story multiplies billable calls (portraits per character + clips per shot + carry-forward frames). Default bounds unless the user explicitly asks for more: ≤ 3 characters, ≤ 3 scenes, ≤ 6 shots total. Above these, state the full count + the rough number of billable image/video generations in the pre-generation confirmation and get the user's explicit OK before generating anything.

Rules & boundary

  • The anchor is sacred: a character's front portrait is generated once and reused; never silently regenerate it (that's how looks drift).
  • Cost discipline: portraits + per-shot generation are billable; state the exact character/shot counts in the pre-generation confirmation and never start generating before the user approves.
  • This skill is the consistency METHOD; it does not itself author HTML (stage-compose) or cut user footage (stage-edit). It sits on top of the generation line.

© Orkas-AI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in packages/skills/stage-consistency of Orkas-AI/Orkas-VideoStudio.

Open the folder on GitHubat commit c0c3c3e

Compare with similar skills

Stage Consistency next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Stage Consistency compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Stage Consistency this skillOrkas-AI/Orkas-VideoStudio499—~1.8kAutomated safety check: PassMIT
Emotion Performance Directorkangarooking/director-skills181—~2.4kAutomated safety check: PassMIT
Film Creatorhappycapy-ai/Happycapy-skills137—~3kAutomated safety check: NotesMIT
Video Generationbytedance/deer-flow84k3 repos~1.4kAutomated safety check: PassMIT
Video Cover Imageitwanger/toBeBetterJavaer18k—~3.3kAutomated safety check: PassNone
Seedancesongguoxs/seedance-prompt-skill2.9k1 repos~2.5kAutomated safety check: PassNone

Similar skills

  • Emotion Performance Director

    kangarooking/director-skills

    A skill your agent uses when the user wants to design, rewrite, refine, or vary emotional acting prompts for live-action AI video characters.

    181 GitHub stars~2.4k tokensUpdated 4 days ago
    Media & CreativeAuto-check passed
  • Film Creator

    happycapy-ai/Happycapy-skills

    AI-powered film creation assistant that transforms a single sentence or image into a complete 30-second film.

    137 GitHub stars~3k tokensUpdated 1 mo ago
    Media & CreativeAuto-check: notes
  • Video Generation

    bytedance/deer-flow

    Generates short videos from a structured JSON prompt, optionally guided by a reference image used as the first or last frame.

    84k GitHub starsUsed in 3 repos~1.4k tokens
    Media & CreativeAuto-check passed
  • Video Cover Image

    itwanger/toBeBetterJavaer

    Generate matched 3:4, 16:9, and 4:3 short-video cover images from toBeBetterJavaer video scripts or AI/Java technical topics.

    18k GitHub stars~3.3k tokensUpdated yesterday
    Media & CreativeAuto-check passed
  • Seedance

    songguoxs/seedance-prompt-skill

    This skill should be used when the user asks to "generate video prompts", "create Seedance prompts", "write video descriptions", mentions "Seedance", "seedance", "即梦", "即梦平台", "视频提示词", "视频生成"…

    2.9k GitHub starsUsed in 1 repo~2.5k tokens
    Media & CreativeAuto-check passed
  • HyperFrames Video Entry Point

    heygen-com/hyperframes

    Entry point for making, editing and rendering videos from HTML compositions with HyperFrames, routing each request to the right workflow.

    60k GitHub starsUsed in 3 repos~5.2k tokens
    Media & CreativeAuto-check passed

More from Orkas-AI/Orkas-VideoStudio

All 14 skills in this repo
  • Gate Control

    Orkas-AI/Orkas-VideoStudio

    Canonical VideoStudio review authorization and state-transition policy.

    499 GitHub stars~2.7k tokensUpdated 19 days ago
    Auto-check passed
  • Stage Compose

    Orkas-AI/Orkas-VideoStudio

    Authoring knowledge for Orkas/OVS HTML video compositions -- write an index.html, drive animation from a paused timeline, declare canvas + duration, then run the VideoStudio draft gate to render an…

    499 GitHub stars~4.2k tokensUpdated 19 days ago
    Auto-check passed
  • Stage Edit

    Orkas-AI/Orkas-VideoStudio

    Intelligent editing of real user-supplied footage—understand it with transcript/inspected-frame/scene/silence/quality evidence, then choose deterministic timeline operations or a constrained…

    499 GitHub stars~2.4k tokensUpdated 19 days ago
    Auto-check passed
  • Stage Plan

    Orkas-AI/Orkas-VideoStudio

    The "ingest + plan" half of end-to-end video orchestration — ingest the user's material from evidence, then decompose intent into ONE cross-modal EDL (plan.json: edit/generate/compose/provided…

    499 GitHub stars~4k tokensUpdated 19 days ago
    Auto-check passed
  • Frontend Design

    Orkas-AI/Orkas-VideoStudio

    Aesthetic direction for OrkasVideoStudio HTML and motion-graphics compositions.

    499 GitHub stars~4.3k tokensUpdated 19 days ago
    Auto-check passed
  • Video Craft

    Orkas-AI/Orkas-VideoStudio

    The craft standard that makes a video GOOD, not just rendered — hooks, story pacing, visual hierarchy, type & safe zones, motion/easing, captions, audio mix, platform conventions, shot language…

    499 GitHub stars~3.3k tokensUpdated 19 days ago
    Auto-check passed

Questions about Stage Consistency

What does Stage Consistency do?

Multi-shot narrative & character consistency — a character bible with a locked front-portrait anchor, view-matched reference selection, recent-frame carry-forward, Cameo (a user photo as the lead)…. Stage Consistency is an agent skill from Orkas-AI/Orkas-VideoStudio. Multi-shot narrative & character consistency — a character bible with a locked front-portrait anchor, view-matched reference selection, recent-frame carry-forward, Cameo (a user photo as the lead), and global planning for long scripts/novels.

When should I use Stage Consistency?

Stage Consistency fits situations like: top of the generation line when the SAME character must look the same across many shots/scenes; for long-form story→video; do NOT trigger for one-off single-shot generation.

How do I install Stage Consistency in Claude Code?

Run `npx skills add Orkas-AI/Orkas-VideoStudio --skill stage-consistency -a claude-code`. Or copy the skill folder (packages/skills/stage-consistency in Orkas-AI/Orkas-VideoStudio) into .claude/skills/stage-consistency in your project. Claude Code loads it when a task matches its description.

How do I install Stage Consistency in Codex?

Run `npx skills add Orkas-AI/Orkas-VideoStudio --skill stage-consistency -a codex`. Or copy the skill folder (packages/skills/stage-consistency in Orkas-AI/Orkas-VideoStudio) into .agents/skills/stage-consistency in your project. Codex loads it when a task matches its description.

Can I use Stage Consistency in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Orkas-AI/Orkas-VideoStudio --skill stage-consistency -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/stage-consistency, .gemini/skills/stage-consistency, .github/skills/stage-consistency and .opencode/skills/stage-consistency in your project.

What does Stage Consistency need to run?

SKILL.md names no scripts, command-line tools or credentials: Stage Consistency is instructions for the agent only.

Does Stage Consistency access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Stage Consistency safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Stage Consistency use?

Stage Consistency is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Stage Consistency use?

About 1.8k tokens (SKILL.md is roughly 7.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Stage Consistency?

Skills that share tags, products or a category with Stage Consistency: Emotion Performance Director (kangarooking/director-skills, 181 stars), Film Creator (happycapy-ai/Happycapy-skills, 137 stars), Video Generation (bytedance/deer-flow, 84k stars) and Video Cover Image (itwanger/toBeBetterJavaer, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Stage Consistency?

Orkas-AI (a GitHub user) maintains it in Orkas-AI/Orkas-VideoStudio, which has 499 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 22, 2026.

Source: Orkas-AI/Orkas-VideoStudio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.