← Creative ClawCONTENT HISTORY

Update to Creative Claw

Snapshot Nov 20, 2026 · 00:10 UTC · version 5.7.3

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for creativeclaw-plan-video

Skill instructions — Now says: give the user the click path: open the [Creative Claw plugin...

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save Creative Claw and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Oct 24, 2026 · 12:48 UTC

tell the user to open the plugin's Connectors tab in their app (or the MCP server list in a terminal client), connect Creative Claw, sign in, and ask again. Do not substitute other tools or describe a result that was not generated. Unles...

After

Nov 20, 2026 · 00:10 UTC

give the user the click path: open the [Creative Claw plugin page](https://claude.ai/customize/plugins/id/3b9e3067-1092-46a5-b613-f52ddf9476ca%40anthropic-plugin-directory/connectors) in Claude, then the **Connectors** tab, press **Conne...

Supporting files

Before

Oct 24, 2026 · 12:48 UTC

[{"relative_path":"agents/openai.yaml","size_in_bytes":534},{"relative_path":"references/images/gpt-image-2.md","size_in_bytes":11212},{"relative_path":"references/images/index.md","size_in_bytes":575},{"relative_path":"references/images...

After

Nov 20, 2026 · 00:10 UTC

[{"relative_path":"agents/openai.yaml","size_in_bytes":534},{"relative_path":"references/images/gpt-image-2.md","size_in_bytes":11814},{"relative_path":"references/images/index.md","size_in_bytes":1055},{"relative_path":"references/image...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -7,7 +7,7 @@
 
 For each Creative Claw tool call that exposes it, pass the optional `skills_used` array with `creativeclaw-plan-video`, any other Creative Claw skills actually followed, and guide entries in the form `<skill-name>/<relative-guide-path>` (for example, `creativeclaw-plan-video/references/workflow-basics.md`). Include only skills and guides followed for that call. Omit attribution if the user declines tracking or the field is unavailable. Never send other plugin names, private data, or local paths.
 
-**Not connected yet?** If no Creative Claw tools (such as `list_models` or `generate_image`) are available, the plugin is installed but the server is not connected. Stop and tell the user to open the plugin's Connectors tab in their app (or the MCP server list in a terminal client), connect Creative Claw, sign in, and ask again. Do not substitute other tools or describe a result that was not generated.
+**Not connected yet?** If no Creative Claw tools (such as `list_models` or `generate_image`) are available, the plugin is installed but the server is not connected. Stop and give the user the click path: open the [Creative Claw plugin page](https://claude.ai/customize/plugins/id/3b9e3067-1092-46a5-b613-f52ddf9476ca%40anthropic-plugin-directory/connectors) in Claude, then the **Connectors** tab, press **Connect**, press **Add** if an "Add custom connector" dialog opens, and sign in. In Claude Code they run `/mcp` instead. Then they ask again. Do not substitute other tools or describe a result that was not generated.
 
 Read [video model selection](references/video/index.md) when choosing shot models. Load a specific model guide only when planning its timing, references or controls. These references are packaged locally; no sibling model skill is required. Planning alone does not authorize video generation.
 
@@ -19,30 +19,27 @@
 
 ## Reference-first pipeline
 
-Unless the user asked for direct text-to-video, supplied a ready shot image, or is editing footage, follow this before `generate_video`. For a planning-only request, show the plan and stop: make keyframes only when the user asked for a visual storyboard, and do not call `generate_video`. New clips start from one keyframe image per shot, so the video model animates images the user has seen instead of inventing the face, product, outfit or location: tell the user how many images that is before making them.
+For a text plan, specify the set, cast, blocking and required frame for each shot and stop there. When the user requests a visual storyboard, produce the frames below. Start video production only when requested.
 
-1. Anchors, reuse first: `search_assets`, `list_characters`, `get_theme`. Person: Character sheet + face portrait (real person: also their best original photo). Product: real photo or packshot, plus a label/logo close-up when text matters. A recurring person or product with no anchor: create it first (creativeclaw-create-avatar, creativeclaw-product-photoshoot).
-2. Look line: one sentence (palette, light, lens, medium), pasted into every keyframe and video prompt.
-3. Keyframe per shot: `generate_image` with the same image model all project (default `image/nano-banana-2`), `aspect_ratio` = the video's ratio, main anchor in `image_url`, others in `extras.image_urls`, roles named. From shot 2 on, add the first approved keyframe (and the previous one when the scene continues) as a look reference alongside the anchors. One clean full-bleed frame; no text, grid or labels.
-4. Compare it to the anchors (face, label, logo, colors); fix with one targeted edit.
-5. Show keyframes and the plan (model, duration, ratio) in one message. Review mode: call `generate_video` now; the card is the approval. Auto: ask once unless the user said go.
-6. One mode per shot. People, several subjects or big motion: `image_urls` = [keyframe, identity anchor, product anchor], 2–4 total; `character_id` is fine here. Exact opening (product hero, logo reveal): `image_url` = keyframe, no `image_urls` or `character_id`.
-7. Next shot: same anchors and look line, plus the earlier keyframes as references. A previous clip's last frame is only an extra composition cue.
+Prepare the actual opening frame of every new shot before generating motion. Use an existing ready shot frame or make one at the delivery ratio. For a recurring location, reuse or design one set image and establish where everyone stands or sits in a wide frame. Build each shot image from that set, the sheet of every visible recurring Character (create missing sheets), and the established positions. Change the camera angle while preserving eyelines, wardrobe, props and positions unless the action moves them. Send the finished shot image to video as a literal start frame or a model-supported visual reference. Follow [reference production](references/video/reference-production.md) for the exact fields, including the approved start/end-frame route. Honor an explicit text-only request or an existing-footage edit.
+
+Choose the speaking workflow before selecting the general video model. For one visible presenter delivering a recording or a line in a chosen voice, use HeyGen Avatar 6 with the approved shot image and finished speech (Turbo for drafts, H3 Max Lip Sync when HeyGen is unavailable for the account). For interacting speakers or a shot driven by body or camera movement, use audio-capable Seedance with the shot image and prepared lines. Gemini Omni 1.2 Flash is the general choice when audio input is unnecessary. Check the requested spoken language for the exact model in `get_model_params`. If native dialogue is unsupported or unverified, tell the user which applies before generation. For a cinematic shot that needs visible speech in that language, plan the visuals to the recording's timing and explain the separate lip-sync step and its cost before committing. A presenter rendered from audio is already synchronized. See [voice in video](references/video/voice-in-video.md).
 
 Details: [reference production](references/video/reference-production.md). Image prompting: [image model index](references/images/index.md) and only the chosen guide.
 
 ## Plan the story
 
-1. Define objective, audience, channel, aspect ratio, target runtime, brand, required Characters or products, audio approach, and call to action. Give each speaking shot a voice path (native dialogue, speech first, or voiceover) from [voice in video](references/video/voice-in-video.md), and note whose voice it is. Check the requested spoken language in `get_model_params({ model })`. For unsupported or unverified languages, plan the [spoken-language workflow](references/video/spoken-languages.md): one audio-driven talking shot when one is requested; consistent images from the same character references at the requested camera positions, per-shot speech and concatenation when multiple shots are requested. Keep the normal route for documented languages; planning does not authorize these generations.
+1. Define objective, audience, channel, aspect ratio, target runtime, brand, required Characters or products, audio approach, and call to action. Give each speaking shot a voice path (native dialogue, speech first, or voiceover) from [voice in video](references/video/voice-in-video.md), and note whose voice it is. A shot where one person says exact lines plans as speech first, then `video/heygen-avatar-6` with that shot's image (`video/minimax-h3-max-lip-sync` when HeyGen is unavailable for the account). A person who speaks in several shots gets a saved voice and Character first. Check the requested spoken language in `get_model_params({ model })`. For unsupported or unverified languages, plan the [spoken-language workflow](references/video/spoken-languages.md): one audio-driven talking shot when one is requested; consistent images from the same character references at the requested camera positions, per-shot speech and concatenation when multiple shots are requested. Keep the normal route for documented languages; planning does not authorize these generations.
 2. Write a concise beat outline and script. Prefer a clear opening hook, progression, payoff, and ending.
 3. Break the piece into shots. Each shot gets one primary action, one camera idea, a start state, end state, dialogue or narration, and a model-supported duration. Keep speech to at most 2.5 spoken words per clip second, with about 0.5 s of air at each end; lock durations from the audio's `wordTimings`.
+   Plan a camera change at every cut. Two shots that join inside a scene differ in shot size (wide, medium, close-up) or angle (about 30° or more, a reverse, high, low, or an insert of a hand or object). Two clips of the same subject from the same framing back to back read as a jump cut: when the action must continue from one camera, make it one longer clip or extend the clip instead of cutting. Cut on action where you can: end a shot mid-movement and start the next on that movement from the new angle. Begin each shot prompt with its shot size and angle, for example "Low-angle close-up: …".
 4. Choose likely models with `list_models` and inspect them with `get_model_params`. Duration and reference limits are per model; never impose a universal clip length.
 
 Write the plan in the user's language and preserve approved dialogue or on-screen copy exactly.
 
 ## Build the storyboard
 
-For a visual storyboard request, create the needed artifacts with `creativeclaw-generate-image`. A text-only plan does not require images; reuse approved frames and skip duplicate review boards when unnecessary:
+For a standalone visual storyboard use `generate_image`. Within a Film project save the plan and use `render_film_shots` for the authorized boards. A text-only plan does not require images; reuse approved frames and skip duplicate review boards when unnecessary:
 
 - A review board or contact sheet for fast approval of composition, pacing, and continuity, only when useful.
 - One clean, text-free keyframe per shot, made as in the pipeline above. Never feed a labeled grid to a video model.
@@ -51,7 +48,7 @@
 
 ## Optional Film project
 
-If the user intends to continue into production, call `create_film_project` and persist the approved shots with `update_film_project`. Use stable shot IDs and the actual tool fields: `description`, `prompt`, `narration`, `storyboardUrl`, `durationS`, `model`, and `status`. Set the project to `script_ok` only after script approval and `storyboard_ok` only after storyboard approval.
+For an intended Film, save the whole plan with stable scene and shot IDs in `create_film_project`. Give each shot its prompt, cast, reference images, dialogue lines and speaker. Resume or patch an existing plan with `get_film_project` and `update_film_project`. Film tracks boards and clips as takes. A plan-only request ends with the saved plan.
 
 ## Approval gate
 
Full technical diff · 2 changed fields

changed /included_files

BEFORE
[
  {
    "relative_path": "agents/openai.yaml",
    "size_in_bytes": 534
  },
  {
    "relative_path": "references/images/gpt-image-2.md",
    "size_in_bytes": 11212
  },
  {
    "relative_path": "references/images/index.md",
    "size_in_bytes": 575
  },
  {
    "relative_path": "references/images/nano-banana-2.md",
    "size_in_bytes": 9762
  },
  {
    "relative_path": "references/images/nano-banana-pro.md",
    "size_in_bytes": 8798
  },
  {
    "relative_path": "references/images/seedream-5-pro.md",
    "size_in_bytes": 10038
  },
  {
    "relative_path": "references/job-recovery.md",
    "size_in_bytes": 3786
  },
  {
    "relative_path": "references/media-assembly.md",
    "size_in_bytes": 8654
  },
  {
    "relative_path": "references/platform-upload.md",
    "size_in_bytes": 1416
  },
  {
    "relative_path": "references/video/gemini-omni.md",
    "size_in_bytes": 10394
  },
  {
    "relative_path": "references/video/h3-max-recast.md",
    "size_in_bytes": 1987
  },
  {
    "relative_path": "references/video/heygen-lipsync.md",
    "size_in_bytes": 11997
  },
  {
    "relative_path": "references/video/index.md",
    "size_in_bytes": 3340
  },
  {
    "relative_path": "references/video/kling-motion-control.md",
    "size_in_bytes": 4834
  },
  {
    "relative_path": "references/video/minimax-h3-max.md",
    "size_in_bytes": 11845
  },
  {
    "relative_path": "references/video/motion-transfer.md",
    "size_in_bytes": 3517
  },
  {
    "relative_path": "references/video/other-models.md",
    "size_in_bytes": 5898
  },
  {
    "relative_path": "references/video/recipe-character-scene.md",
    "size_in_bytes": 3076
  },
  {
    "relative_path": "references/video/recipe-product-ad.md",
    "size_in_bytes": 3265
  },
  {
    "relative_path": "references/video/recipe-source-edit.md",
    "size_in_bytes": 5428
  },
  {
    "relative_path": "references/video/reference-production.md",
    "size_in_bytes": 7198
  },
  {
    "relative_path": "references/video/review.md",
    "size_in_bytes": 1876
  },
  {
    "relative_path": "references/video/seedance-2-5.md",
    "size_in_bytes": 15610
  },
  {
    "relative_path": "references/video/seedance-mini.md",
    "size_in_bytes": 1579
  },
  {
    "relative_path": "references/video/spoken-languages.md",
    "size_in_bytes": 7949
  },
  {
    "relative_path": "references/video/ugc-paths.md",
    "size_in_bytes": 3391
  },
  {
    "relative_path": "references/video/voice-in-video.md",
    "size_in_bytes": 4887
  },
  {
    "relative_path": "references/video/wan-3.md",
    "size_in_bytes": 9117
  },
  {
    "relative_path": "references/voices/speech-localization.md",
    "size_in_bytes": 3869
  },
  {
    "relative_path": "references/workflow-basics.md",
    "size_in_bytes": 10396
  }
]
AFTER
[
  {
    "relative_path": "agents/openai.yaml",
    "size_in_bytes": 534
  },
  {
    "relative_path": "references/images/gpt-image-2.md",
    "size_in_bytes": 11814
  },
  {
    "relative_path": "references/images/index.md",
    "size_in_bytes": 1055
  },
  {
    "relative_path": "references/images/nano-banana-2.md",
    "size_in_bytes": 10010
  },
  {
    "relative_path": "references/images/nano-banana-pro.md",
    "size_in_bytes": 8780
  },
  {
    "relative_path": "references/images/seedream-5-pro.md",
    "size_in_bytes": 10038
  },
  {
    "relative_path": "references/images/seedream-5.5.md",
    "size_in_bytes": 11118
  },
  {
    "relative_path": "references/job-recovery.md",
    "size_in_bytes": 3774
  },
  {
    "relative_path": "references/media-assembly.md",
    "size_in_bytes": 11689
  },
  {
    "relative_path": "references/platform-upload.md",
    "size_in_bytes": 1416
  },
  {
    "relative_path": "references/video/gemini-omni.md",
    "size_in_bytes": 10659
  },
  {
    "relative_path": "references/video/h3-max-recast.md",
    "size_in_bytes": 2075
  },
  {
    "relative_path": "references/video/heygen-lipsync.md",
    "size_in_bytes": 11847
  },
  {
    "relative_path": "references/video/index.md",
    "size_in_bytes": 5545
  },
  {
    "relative_path": "references/video/kling-4.md",
    "size_in_bytes": 18258
  },
  {
    "relative_path": "references/video/kling-motion-control.md",
    "size_in_bytes": 4854
  },
  {
    "relative_path": "references/video/minimax-h3-max.md",
    "size_in_bytes": 12863
  },
  {
    "relative_path": "references/video/motion-transfer.md",
    "size_in_bytes": 4587
  },
  {
    "relative_path": "references/video/other-models.md",
    "size_in_bytes": 6177
  },
  {
    "relative_path": "references/video/recipe-character-scene.md",
    "size_in_bytes": 3469
  },
  {
    "relative_path": "references/video/recipe-product-ad.md",
    "size_in_bytes": 3308
  },
  {
    "relative_path": "references/video/recipe-source-edit.md",
    "size_in_bytes": 5493
  },
  {
    "relative_path": "references/video/reference-production.md",
    "size_in_bytes": 8027
  },
  {
    "relative_path": "references/video/review.md",
    "size_in_bytes": 2075
  },
  {
    "relative_path": "references/video/seedance-2-5-flash.md",
    "size_in_bytes": 9328
  },
  {
    "relative_path": "references/video/seedance-2-5.md",
    "size_in_bytes": 16199
  },
  {
    "relative_path": "references/video/seedance-mini.md",
    "size_in_bytes": 1798
  },
  {
    "relative_path": "references/video/spoken-languages.md",
    "size_in_bytes": 10240
  },
  {
    "relative_path": "references/video/ugc-paths.md",
    "size_in_bytes": 3618
  },
  {
    "relative_path": "references/video/voice-in-video.md",
    "size_in_bytes": 9077
  },
  {
    "relative_path": "references/video/wan-3.md",
    "size_in_bytes": 10156
  },
  {
    "relative_path": "references/voices/speech-localization.md",
    "size_in_bytes": 5972
  },
  {
    "relative_path": "references/workflow-basics.md",
    "size_in_bytes": 10299
  }
]

changed /skill_md_contents

BEFORE
"---\nname: creativeclaw-plan-video\ndescription: \"Plan a video as an approved script, shot list, and storyboard with clean generation references. Use before costly multi-shot work, when continuity matters, or when the user asks to storyboard without producing a final film yet.\"\n---\n\n# Plan Video\n\nFor each Creative Claw tool call that exposes it, pass the optional `skills_used` array with `creativeclaw-plan-video`, any other Creative Claw skills actually followed, and guide entries in the form `<skill-name>/<relative-guide-path>` (for example, `creativeclaw-plan-video/references/workflow-basics.md`). Include only skills and guides followed for that call. Omit attribution if the user declines tracking or the field is unavailable. Never send other plugin names, private data, or local paths.\n\n**Not connected yet?** If no Creative Claw tools (such as `list_models` or `generate_image`) are available, the plugin is installed but the server is not connected. Stop and tell the user to open the plugin's Connectors tab in their app (or the MCP server list in a terminal client), connect Creative Claw, sign in, and ask again. Do not substitute other tools or describe a result that was not generated.\n\nRead [video model selection](references/video/index.md) when choosing shot models. Load a specific model guide only when planning its timing, references or controls. These references are packaged locally; no sibling model skill is required. Planning alone does not authorize video generation.\n\nRead [shared execution guidance](references/workflow-basics.md) once per task before using tools. It covers existing authorization, model discovery, optional cost checks, imports, and recovery.\n\nConvert a concept into an execution-ready video plan before spending on clips. This skill stops at an approved plan or storyboard unless the user also asks for production.\n\nFor worked production flows, read only the relevant recipe: [product ad](references/video/recipe-product-ad.md), [consistent Character scene](references/video/recipe-character-scene.md), or [source edit, person replacement and extension](references/video/recipe-source-edit.md). These explain asset preparation, shot prompting, assembly and output checks, without authorizing extra paid drafts.\n\n## Reference-first pipeline\n\nUnless the user asked for direct text-to-video, supplied a ready shot image, or is editing footage, follow this before `generate_video`. For a planning-only request, show the plan and stop: make keyframes only when the user asked for a visual storyboard, and do not call `generate_video`. New clips start from one keyframe image per shot, so the video model animates images the user has seen instead of inventing the face, product, outfit or location: tell the user how many images that is before making them.\n\n1. Anchors, reuse first: `search_assets`, `list_characters`, `get_theme`. Person: Character sheet + face portrait (real person: also their best original photo). Product: real photo or packshot, plus a label/logo close-up when text matters. A recurring person or product with no anchor: create it first (creativeclaw-create-avatar, creativeclaw-product-photoshoot).\n2. Look line: one sentence (palette, light, lens, medium), pasted into every keyframe and video prompt.\n3. Keyframe per shot: `generate_image` with the same image model all project (default `image/nano-banana-2`), `aspect_ratio` = the video's ratio, main anchor in `image_url`, others in `extras.image_urls`, roles named. From shot 2 on, add the first approved keyframe (and the previous one when the scene continues) as a look reference alongside the anchors. One clean full-bleed frame; no text, grid or labels.\n4. Compare it to the anchors (face, label, logo, colors); fix with one targeted edit.\n5. Show keyframes and the plan (model, duration, ratio) in one message. Review mode: call `generate_video` now; the card is the approval. Auto: ask once unless the user said go.\n6. One mode per shot. People, several subjects or big motion: `image_urls` = [keyframe, identity anchor, product anchor], 2–4 total; `character_id` is fine here. Exact opening (product hero, logo reveal): `image_url` = keyframe, no `image_urls` or `character_id`.\n7. Next shot: same anchors and look line, plus the earlier keyframes as references. A previous clip's last frame is only an extra composition cue.\n\nDetails: [reference production](references/video/reference-production.md). Image prompting: [image model index](references/images/index.md) and only the chosen guide.\n\n## Plan the story\n\n1. Define objective, audience, channel, aspect ratio, target runtime, brand, required Characters or products, audio approach, and call to action. Give each speaking shot a voice path (native dialogue, speech first, or voiceover) from [voice in video](references/video/voice-in-video.md), and note whose voice it is. Check the requested spoken language in `get_model_params({ model })`. For unsupported or unverified languages, plan the [spoken-language workflow](references/video/spoken-languages.md): one audio-driven talking shot when one is requested; consistent images from the same character references at the requested camera positions, per-shot speech and concatenation when multiple shots are requested. Keep the normal route for documented languages; planning does not authorize these generations.\n2. Write a concise beat outline and script. Prefer a clear opening hook, progression, payoff, and ending.\n3. Break the piece into shots. Each shot gets one primary action, one camera idea, a start state, end state, dialogue or narration, and a model-supported duration. Keep speech to at most 2.5 spoken words per clip second, with about 0.5 s of air at each end; lock durations from the audio's `wordTimings`.\n4. Choose likely models with `list_models` and inspect them with `get_model_params`. Duration and reference limits are per model; never impose a universal clip length.\n\nWrite the plan in the user's language and preserve approved dialogue or on-screen copy exactly.\n\n## Build the storyboard\n\nFor a visual storyboard request, create the needed artifacts with `creativeclaw-generate-image`. A text-only plan does not require images; reuse approved frames and skip duplicate review boards when unnecessary:\n\n- A review board or contact sheet for fast approval of composition, pacing, and continuity, only when useful.\n- One clean, text-free keyframe per shot, made as in the pipeline above. Never feed a labeled grid to a video model.\n\nPreserve Character identity, product geometry, wardrobe, palette, screen direction, time of day, and recurring locations across frames. Use one image model for the whole project, Nano Banana 2 by default.\n\n## Optional Film project\n\nIf the user intends to continue into production, call `create_film_project` and persist the approved shots with `update_film_project`. Use stable shot IDs and the actual tool fields: `description`, `prompt`, `narration`, `storyboardUrl`, `durationS`, `model`, and `status`. Set the project to `script_ok` only after script approval and `storyboard_ok` only after storyboard approval.\n\n## Approval gate\n\nPresent the requested plan/storyboard and honor review stages and existing approval. Planning alone does not authorize video generation. When production is also requested and its applicable stage is approved, continue with `creativeclaw-build-film`.\n"
AFTER
"---\nname: creativeclaw-plan-video\ndescription: \"Plan a video as an approved script, shot list, and storyboard with clean generation references. Use before costly multi-shot work, when continuity matters, or when the user asks to storyboard without producing a final film yet.\"\n---\n\n# Plan Video\n\nFor each Creative Claw tool call that exposes it, pass the optional `skills_used` array with `creativeclaw-plan-video`, any other Creative Claw skills actually followed, and guide entries in the form `<skill-name>/<relative-guide-path>` (for example, `creativeclaw-plan-video/references/workflow-basics.md`). Include only skills and guides followed for that call. Omit attribution if the user declines tracking or the field is unavailable. Never send other plugin names, private data, or local paths.\n\n**Not connected yet?** If no Creative Claw tools (such as `list_models` or `generate_image`) are available, the plugin is installed but the server is not connected. Stop and give the user the click path: open the [Creative Claw plugin page](https://claude.ai/customize/plugins/id/3b9e3067-1092-46a5-b613-f52ddf9476ca%40anthropic-plugin-directory/connectors) in Claude, then the **Connectors** tab, press **Connect**, press **Add** if an \"Add custom connector\" dialog opens, and sign in. In Claude Code they run `/mcp` instead. Then they ask again. Do not substitute other tools or describe a result that was not generated.\n\nRead [video model selection](references/video/index.md) when choosing shot models. Load a specific model guide only when planning its timing, references or controls. These references are packaged locally; no sibling model skill is required. Planning alone does not authorize video generation.\n\nRead [shared execution guidance](references/workflow-basics.md) once per task before using tools. It covers existing authorization, model discovery, optional cost checks, imports, and recovery.\n\nConvert a concept into an execution-ready video plan before spending on clips. This skill stops at an approved plan or storyboard unless the user also asks for production.\n\nFor worked production flows, read only the relevant recipe: [product ad](references/video/recipe-product-ad.md), [consistent Character scene](references/video/recipe-character-scene.md), or [source edit, person replacement and extension](references/video/recipe-source-edit.md). These explain asset preparation, shot prompting, assembly and output checks, without authorizing extra paid drafts.\n\n## Reference-first pipeline\n\nFor a text plan, specify the set, cast, blocking and required frame for each shot and stop there. When the user requests a visual storyboard, produce the frames below. Start video production only when requested.\n\nPrepare the actual opening frame of every new shot before generating motion. Use an existing ready shot frame or make one at the delivery ratio. For a recurring location, reuse or design one set image and establish where everyone stands or sits in a wide frame. Build each shot image from that set, the sheet of every visible recurring Character (create missing sheets), and the established positions. Change the camera angle while preserving eyelines, wardrobe, props and positions unless the action moves them. Send the finished shot image to video as a literal start frame or a model-supported visual reference. Follow [reference production](references/video/reference-production.md) for the exact fields, including the approved start/end-frame route. Honor an explicit text-only request or an existing-footage edit.\n\nChoose the speaking workflow before selecting the general video model. For one visible presenter delivering a recording or a line in a chosen voice, use HeyGen Avatar 6 with the approved shot image and finished speech (Turbo for drafts, H3 Max Lip Sync when HeyGen is unavailable for the account). For interacting speakers or a shot driven by body or camera movement, use audio-capable Seedance with the shot image and prepared lines. Gemini Omni 1.2 Flash is the general choice when audio input is unnecessary. Check the requested spoken language for the exact model in `get_model_params`. If native dialogue is unsupported or unverified, tell the user which applies before generation. For a cinematic shot that needs visible speech in that language, plan the visuals to the recording's timing and explain the separate lip-sync step and its cost before committing. A presenter rendered from audio is already synchronized. See [voice in video](references/video/voice-in-video.md).\n\nDetails: [reference production](references/video/reference-production.md). Image prompting: [image model index](references/images/index.md) and only the chosen guide.\n\n## Plan the story\n\n1. Define objective, audience, channel, aspect ratio, target runtime, brand, required Characters or products, audio approach, and call to action. Give each speaking shot a voice path (native dialogue, speech first, or voiceover) from [voice in video](references/video/voice-in-video.md), and note whose voice it is. A shot where one person says exact lines plans as speech first, then `video/heygen-avatar-6` with that shot's image (`video/minimax-h3-max-lip-sync` when HeyGen is unavailable for the account). A person who speaks in several shots gets a saved voice and Character first. Check the requested spoken language in `get_model_params({ model })`. For unsupported or unverified languages, plan the [spoken-language workflow](references/video/spoken-languages.md): one audio-driven talking shot when one is requested; consistent images from the same character references at the requested camera positions, per-shot speech and concatenation when multiple shots are requested. Keep the normal route for documented languages; planning does not authorize these generations.\n2. Write a concise beat outline and script. Prefer a clear opening hook, progression, payoff, and ending.\n3. Break the piece into shots. Each shot gets one primary action, one camera idea, a start state, end state, dialogue or narration, and a model-supported duration. Keep speech to at most 2.5 spoken words per clip second, with about 0.5 s of air at each end; lock durations from the audio's `wordTimings`.\n   Plan a camera change at every cut. Two shots that join inside a scene differ in shot size (wide, medium, close-up) or angle (about 30° or more, a reverse, high, low, or an insert of a hand or object). Two clips of the same subject from the same framing back to back read as a jump cut: when the action must continue from one camera, make it one longer clip or extend the clip instead of cutting. Cut on action where you can: end a shot mid-movement and start the next on that movement from the new angle. Begin each shot prompt with its shot size and angle, for example \"Low-angle close-up: …\".\n4. Choose likely models with `list_models` and inspect them with `get_model_params`. Duration and reference limits are per model; never impose a universal clip length.\n\nWrite the plan in the user's language and preserve approved dialogue or on-screen copy exactly.\n\n## Build the storyboard\n\nFor a standalone visual storyboard use `generate_image`. Within a Film project save the plan and use `render_film_shots` for the authorized boards. A text-only plan does not require images; reuse approved frames and skip duplicate review boards when unnecessary:\n\n- A review board or contact sheet for fast approval of composition, pacing, and continuity, only when useful.\n- One clean, text-free keyframe per shot, made as in the pipeline above. Never feed a labeled grid to a video model.\n\nPreserve Character identity, product geometry, wardrobe, palette, screen direction, time of day, and recurring locations across frames. Use one image model for the whole project, Nano Banana 2 by default.\n\n## Optional Film project\n\nFor an intended Film, save the whole plan with stable scene and shot IDs in `create_film_project`. Give each shot its prompt, cast, reference images, dialogue lines and speaker. Resume or patch an existing plan with `get_film_project` and `update_film_project`. Film tracks boards and clips as takes. A plan-only request ends with the saved plan.\n\n## Approval gate\n\nPresent the requested plan/storyboard and honor review stages and existing approval. Planning alone does not authorize video generation. When production is also requested and its applicable stage is approved, continue with `creativeclaw-build-film`.\n"
Full snapshot data
{
  "description": "Plan a video as an approved script, shot list, and storyboard with clean generation references. Use before costly multi-shot work, when continuity matters, or when the user asks to storyboard without producing a final film yet.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 534
    },
    {
      "relative_path": "references/images/gpt-image-2.md",
      "size_in_bytes": 11814
    },
    {
      "relative_path": "references/images/index.md",
      "size_in_bytes": 1055
    },
    {
      "relative_path": "references/images/nano-banana-2.md",
      "size_in_bytes": 10010
    },
    {
      "relative_path": "references/images/nano-banana-pro.md",
      "size_in_bytes": 8780
    },
    {
      "relative_path": "references/images/seedream-5-pro.md",
      "size_in_bytes": 10038
    },
    {
      "relative_path": "references/images/seedream-5.5.md",
      "size_in_bytes": 11118
    },
    {
      "relative_path": "references/job-recovery.md",
      "size_in_bytes": 3774
    },
    {
      "relative_path": "references/media-assembly.md",
      "size_in_bytes": 11689
    },
    {
      "relative_path": "references/platform-upload.md",
      "size_in_bytes": 1416
    },
    {
      "relative_path": "references/video/gemini-omni.md",
      "size_in_bytes": 10659
    },
    {
      "relative_path": "references/video/h3-max-recast.md",
      "size_in_bytes": 2075
    },
    {
      "relative_path": "references/video/heygen-lipsync.md",
      "size_in_bytes": 11847
    },
    {
      "relative_path": "references/video/index.md",
      "size_in_bytes": 5545
    },
    {
      "relative_path": "references/video/kling-4.md",
      "size_in_bytes": 18258
    },
    {
      "relative_path": "references/video/kling-motion-control.md",
      "size_in_bytes": 4854
    },
    {
      "relative_path": "references/video/minimax-h3-max.md",
      "size_in_bytes": 12863
    },
    {
      "relative_path": "references/video/motion-transfer.md",
      "size_in_bytes": 4587
    },
    {
      "relative_path": "references/video/other-models.md",
      "size_in_bytes": 6177
    },
    {
      "relative_path": "references/video/recipe-character-scene.md",
      "size_in_bytes": 3469
    },
    {
      "relative_path": "references/video/recipe-product-ad.md",
      "size_in_bytes": 3308
    },
    {
      "relative_path": "references/video/recipe-source-edit.md",
      "size_in_bytes": 5493
    },
    {
      "relative_path": "references/video/reference-production.md",
      "size_in_bytes": 8027
    },
    {
      "relative_path": "references/video/review.md",
      "size_in_bytes": 2075
    },
    {
      "relative_path": "references/video/seedance-2-5-flash.md",
      "size_in_bytes": 9328
    },
    {
      "relative_path": "references/video/seedance-2-5.md",
      "size_in_bytes": 16199
    },
    {
      "relative_path": "references/video/seedance-mini.md",
      "size_in_bytes": 1798
    },
    {
      "relative_path": "references/video/spoken-languages.md",
      "size_in_bytes": 10240
    },
    {
      "relative_path": "references/video/ugc-paths.md",
      "size_in_bytes": 3618
    },
    {
      "relative_path": "references/video/voice-in-video.md",
      "size_in_bytes": 9077
    },
    {
      "relative_path": "references/video/wan-3.md",
      "size_in_bytes": 10156
    },
    {
      "relative_path": "references/voices/speech-localization.md",
      "size_in_bytes": 5972
    },
    {
      "relative_path": "references/workflow-basics.md",
      "size_in_bytes": 10299
    }
  ],
  "name": "creativeclaw-plan-video",
  "skill_md_contents": "---\nname: creativeclaw-plan-video\ndescription: \"Plan a video as an approved script, shot list, and storyboard with clean generation references. Use before costly multi-shot work, when continuity matters, or when the user asks to storyboard without producing a final film yet.\"\n---\n\n# Plan Video\n\nFor each Creative Claw tool call that exposes it, pass the optional `skills_used` array with `creativeclaw-plan-video`, any other Creative Claw skills actually followed, and guide entries in the form `<skill-name>/<relative-guide-path>` (for example, `creativeclaw-plan-video/references/workflow-basics.md`). Include only skills and guides followed for that call. Omit attribution if the user declines tracking or the field is unavailable. Never send other plugin names, private data, or local paths.\n\n**Not connected yet?** If no Creative Claw tools (such as `list_models` or `generate_image`) are available, the plugin is installed but the server is not connected. Stop and give the user the click path: open the [Creative Claw plugin page](https://claude.ai/customize/plugins/id/3b9e3067-1092-46a5-b613-f52ddf9476ca%40anthropic-plugin-directory/connectors) in Claude, then the **Connectors** tab, press **Connect**, press **Add** if an \"Add custom connector\" dialog opens, and sign in. In Claude Code they run `/mcp` instead. Then they ask again. Do not substitute other tools or describe a result that was not generated.\n\nRead [video model selection](references/video/index.md) when choosing shot models. Load a specific model guide only when planning its timing, references or controls. These references are packaged locally; no sibling model skill is required. Planning alone does not authorize video generation.\n\nRead [shared execution guidance](references/workflow-basics.md) once per task before using tools. It covers existing authorization, model discovery, optional cost checks, imports, and recovery.\n\nConvert a concept into an execution-ready video plan before spending on clips. This skill stops at an approved plan or storyboard unless the user also asks for production.\n\nFor worked production flows, read only the relevant recipe: [product ad](references/video/recipe-product-ad.md), [consistent Character scene](references/video/recipe-character-scene.md), or [source edit, person replacement and extension](references/video/recipe-source-edit.md). These explain asset preparation, shot prompting, assembly and output checks, without authorizing extra paid drafts.\n\n## Reference-first pipeline\n\nFor a text plan, specify the set, cast, blocking and required frame for each shot and stop there. When the user requests a visual storyboard, produce the frames below. Start video production only when requested.\n\nPrepare the actual opening frame of every new shot before generating motion. Use an existing ready shot frame or make one at the delivery ratio. For a recurring location, reuse or design one set image and establish where everyone stands or sits in a wide frame. Build each shot image from that set, the sheet of every visible recurring Character (create missing sheets), and the established positions. Change the camera angle while preserving eyelines, wardrobe, props and positions unless the action moves them. Send the finished shot image to video as a literal start frame or a model-supported visual reference. Follow [reference production](references/video/reference-production.md) for the exact fields, including the approved start/end-frame route. Honor an explicit text-only request or an existing-footage edit.\n\nChoose the speaking workflow before selecting the general video model. For one visible presenter delivering a recording or a line in a chosen voice, use HeyGen Avatar 6 with the approved shot image and finished speech (Turbo for drafts, H3 Max Lip Sync when HeyGen is unavailable for the account). For interacting speakers or a shot driven by body or camera movement, use audio-capable Seedance with the shot image and prepared lines. Gemini Omni 1.2 Flash is the general choice when audio input is unnecessary. Check the requested spoken language for the exact model in `get_model_params`. If native dialogue is unsupported or unverified, tell the user which applies before generation. For a cinematic shot that needs visible speech in that language, plan the visuals to the recording's timing and explain the separate lip-sync step and its cost before committing. A presenter rendered from audio is already synchronized. See [voice in video](references/video/voice-in-video.md).\n\nDetails: [reference production](references/video/reference-production.md). Image prompting: [image model index](references/images/index.md) and only the chosen guide.\n\n## Plan the story\n\n1. Define objective, audience, channel, aspect ratio, target runtime, brand, required Characters or products, audio approach, and call to action. Give each speaking shot a voice path (native dialogue, speech first, or voiceover) from [voice in video](references/video/voice-in-video.md), and note whose voice it is. A shot where one person says exact lines plans as speech first, then `video/heygen-avatar-6` with that shot's image (`video/minimax-h3-max-lip-sync` when HeyGen is unavailable for the account). A person who speaks in several shots gets a saved voice and Character first. Check the requested spoken language in `get_model_params({ model })`. For unsupported or unverified languages, plan the [spoken-language workflow](references/video/spoken-languages.md): one audio-driven talking shot when one is requested; consistent images from the same character references at the requested camera positions, per-shot speech and concatenation when multiple shots are requested. Keep the normal route for documented languages; planning does not authorize these generations.\n2. Write a concise beat outline and script. Prefer a clear opening hook, progression, payoff, and ending.\n3. Break the piece into shots. Each shot gets one primary action, one camera idea, a start state, end state, dialogue or narration, and a model-supported duration. Keep speech to at most 2.5 spoken words per clip second, with about 0.5 s of air at each end; lock durations from the audio's `wordTimings`.\n   Plan a camera change at every cut. Two shots that join inside a scene differ in shot size (wide, medium, close-up) or angle (about 30° or more, a reverse, high, low, or an insert of a hand or object). Two clips of the same subject from the same framing back to back read as a jump cut: when the action must continue from one camera, make it one longer clip or extend the clip instead of cutting. Cut on action where you can: end a shot mid-movement and start the next on that movement from the new angle. Begin each shot prompt with its shot size and angle, for example \"Low-angle close-up: …\".\n4. Choose likely models with `list_models` and inspect them with `get_model_params`. Duration and reference limits are per model; never impose a universal clip length.\n\nWrite the plan in the user's language and preserve approved dialogue or on-screen copy exactly.\n\n## Build the storyboard\n\nFor a standalone visual storyboard use `generate_image`. Within a Film project save the plan and use `render_film_shots` for the authorized boards. A text-only plan does not require images; reuse approved frames and skip duplicate review boards when unnecessary:\n\n- A review board or contact sheet for fast approval of composition, pacing, and continuity, only when useful.\n- One clean, text-free keyframe per shot, made as in the pipeline above. Never feed a labeled grid to a video model.\n\nPreserve Character identity, product geometry, wardrobe, palette, screen direction, time of day, and recurring locations across frames. Use one image model for the whole project, Nano Banana 2 by default.\n\n## Optional Film project\n\nFor an intended Film, save the whole plan with stable scene and shot IDs in `create_film_project`. Give each shot its prompt, cast, reference images, dialogue lines and speaker. Resume or patch an existing plan with `get_film_project` and `update_film_project`. Film tracks boards and clips as takes. A plan-only request ends with the saved plan.\n\n## Approval gate\n\nPresent the requested plan/storyboard and honor review stages and existing approval. Planning alone does not authorize video generation. When production is also requested and its applicable stage is approved, continue with `creativeclaw-build-film`.\n"
}

SHA-256 of public snapshot: fadff4f0689c2aa44a18c294eb995f58c97bb7643f66655d78c0541f5c027660