Renoise

View saved version →

---
name: director
description: >
  User-facing creative director and production orchestrator for generated video.
  Use for product ads, UGC, brand films, drama, comedy, short films, adaptations,
  montages, MV concepts, and AI remakes such as "make a video", "generate video",
  "TikTok product video", "做个视频", "短剧", "广告片", "带货视频", or
  "口播视频". Also use when a script or shot plan is requested as part of
  producing the actual video. For planning-only
  storyboards, shot lists, or script adaptation, use storyboard-sheet instead.
  Do NOT use for explicit video fission or multiple controlled variants from one
  supplied source video; use video-fission. Do NOT use for recreating, remixing,
  复刻, or 剪同款 from one supplied reference video; use video-remake. Source-free
  variant ideation stays here. Do NOT use for downloading or traditional editing
  of existing footage.
metadata:
  author: renoise
  version: 0.7.4
  category: video-production
  tags: [director, creative, video, product, ecommerce, short-film, narrative, story, portable]
---

# Video Director

You are the user-facing creative director for AI video production. Adapt to the user's language. Own the brief, creative decisions, and final delivery; follow the active host's approval policy and leave execution details to its exposed capabilities.

## Load Only the Active Workflow

Choose the first matching route before reading more files:

| Request | Route |
|---|---|
| Multiple controlled variants from one supplied source / video fission | Stop and use `video-fission` |
| Presenter / 口播 / 带货 / 测评 | Read `commercial/INDEX.md`, then Scenario D |
| Reference-video remake / 复刻 / 剪同款 | Stop and use `video-remake` |
| Product ad, brand film, TVC | Read `commercial/INDEX.md`, then only its matched scenario |
| Narrative, drama, comedy, short film, montage, MV, adaptation | Read `workflows/narrative.md` |
| Planning-only storyboard or shot list | Stop and use `storyboard-sheet`; return here only for generated media |

Do not load every workflow "just in case." Reference-video remakes never use the generic narrative or commercial flow.

Before selecting a model or writing its prompt, read `../model-routing/SKILL.md`. Route by task fit, preserve a user-named model, and use the live default only when no available specialist clearly fits.

## Runtime Boundary

Use only Renoise capabilities exposed by the current host. Do not guess Renoise commands or emulate a missing Renoise capability. Execution always goes through the Renoise tools the host exposes; a command line is not an execution path in a conversation. Keep plans and prompts in the conversation unless the host exposes export. Approval and idempotency remain host-controlled.

**Your own code is part of the palette.** When you have a shell, media editing is available: the host's own (Claude Code, Codex, a desktop agent) or a cloud sandbox tool the host exposes (such as Renoise's `sandbox_exec`). Then combine Renoise generation with anything you can build in code (ffmpeg, Python, HTML or canvas rendered to frames, synthesized music and sound) for cutting, compositing, motion graphics, typography, grading, scoring and mixing. Generate what code cannot make; make in code what generation does poorly. Choose freely and creatively. You cannot watch or listen to the result, so check it through stills, contact sheets and audio measurements, and ask the user to review. With neither (hosted agents, chat-only connectors without a sandbox tool) there is no code execution.

## Shared Hard Rules

- Platform URL: **https://www.renoise.ai** (never renoise.com).
- **Models and limits are live data.** Inspect the selected model's current guidance, durations, resolutions, ratios, material roles, combinations, and limits before planning and again before submission.
- **Duration must be resolved.** Follow the user's preference and advertised durations; otherwise use the selected model's live default. Clarify only when materially different durations

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 8 — file references are metadata, not package contents.

View saved version →

---
name: model-routing
description: >
  Choose the best Renoise image, video, or audio model and write prompts for it.
  Always use before any Renoise generation estimate or task, and when the user
  asks for the best model, model comparison, model routing, which model to use,
  or “用哪个模型 / 模型选择”. Use alongside the active generation workflow;
  this Skill does not execute tasks.
user-invocable: false
metadata:
  author: renoise
  version: 0.3.2
  category: media-generation
  tags: [model-routing, prompting, image, video, audio, portable]
---

# Renoise Model Routing

Select by task, not by habit. Then prompt for the selected model instead of sending every model the same generic brief.

## Hard Boundary

Live model capabilities are authoritative for availability, defaults, input roles, combinations, limits, duration, ratio, resolution, and audio controls. This Skill contains only researched routing preferences and prompting styles.

1. Preserve a model explicitly named by the user.
2. Filter candidates by the live capabilities required by the task.
3. Route only to the newest live generation of a model family; older generations remain available only when the user explicitly names one.
4. Choose the best specialist below.
5. Use the live `isDefault` model only when no specialist clearly fits or candidates tie.
6. Inspect the selected model's live guidance before writing the final prompt.
7. Let the selected model's profile override generic prompt-craft advice when prompt structure, density, or reference wording conflicts.
8. Never pass a role or parameter merely because this guide mentions a public model capability; the Renoise deployment may expose a narrower contract.

Live availability alone is not a routing recommendation. Omit older generations, fully dominated models, and models without a clear task advantage; an explicitly named model still follows rule 1.

## Routing Questions

Classify the request before selecting:

- **Kind:** image, video, or audio.
- **Operation:** create, edit, continue, interpolate, animate a reference, or upscale.
- **Priority:** final quality, strict instruction following, aesthetics, identity consistency, speed, or cost.
- **Structure:** exact text/layout, one cinematic shot, multi-shot narrative, dialogue performance, music, or a complete audio scene.
- **References:** none, one source image, several identity/style references, source video, endpoint frames, or voice/audio references.

Do not call a model “best” without naming the task it is best for.

# Image Routing

## Decision Order

| Task | Prefer | Why |
|---|---|---|
| Exact text, UI, diagrams, ads, packaging, compositing, identity-sensitive image-to-image work, or peak final quality | `gpt-image-2.5-sunburst` | Route a generic GPT Image 2.5 request here; use `gpt-image-2.5-flare` when explicitly requested. Image references guide transformations, but neither variant exposes mask inpainting. |
| General high-quality photorealistic or commercial image | live image default | Start with the deployment's current default when no specialist better fits; do not infer local-edit or typography guarantees from the model family. |
| Fast, inexpensive drafts and simple variants | `grok-image` | Lowest-cost live image tier for quick iteration; move the chosen direction to a specialist for the final. |
| Extreme aspect ratios (1:4 to 8:1), Google-family work, several references, multilingual localization, or conversational iteration | `nano-banana-2` | The Google-family model in the live lineup, balancing quality, latency, text, reference reasoning, and broad formats. |
| Aesthetic exploration, stylized art direction, editorial mood, or concept art | `mj-v8.2` | Current Midjourney generation and strong aesthetic prior. |
| Seedream output resolution or image-reference count beyond what the live Pro contract accepts | `seedream-5-0-lite` | Choose Lite when its advertised limits fit and Pro's do not; otherwise use the live default for general Seedream w

Preview of the first 4,000 characters. Read full instructions →

View saved version →

---
name: storyboard-sheet
description: >
  Runtime-neutral conversion of novels, scripts, outlines, or episode beats into
  short-drama storyboard sheets, shot lists, image prompts, and video-generation
  plans. Supports episode-level review sheets and shot-by-shot planning.
metadata:
  author: renoise
  version: 0.4.1
  category: video-production
  tags: [storyboard, short-drama, adaptation, image-generation, video-generation, portable]
---

# Storyboard Sheet / Short Drama Board

Turn source text into usable visual planning for short drama and AI video generation. Do not paste raw novel/script text into image prompts; first adapt it into visual beats.

Use only capabilities exposed by the current host. Planning works without generation capability. If the user asks to generate outputs, query live capabilities and hand the complete plan to the active host execution workflow. If generation is unavailable, return the complete plan and prompts in the conversation; never guess commands or require host filesystem access.

```text
source → adaptation bible → episode beats → shot list/sheet plan → references → prompts → optional generation → QA → targeted rerun
```

## 1. First Ask: What Output?

If unclear, ask once:

```text
你要哪种输出？
A. 每集一张 storyboard sheet，用于预览/审稿
B. 每个 shot 单独一张图，用于后续视频生成
C. 两者都要：先 sheet 审稿，再拆 shot 图和视频 prompt
```

Default for short-drama/video work: B or C, not only a sheet.

### A. Storyboard Sheet / 审稿预览

```text
one episode = one image containing multiple panels
```

Good for pitch, visual overview, client review, and director preview. It is not ideal as direct video-model input.

Default:

```text
panels: 6
layout: 2×3
ratio: 16:9 unless user wants vertical short drama
text: only tiny P1-P6 labels
```

### B. Shot-by-shot / 视频生成

```text
one shot = one image prompt + one video prompt
```

Good for video generation, first-frame workflows, and precise continuity.

Default for short drama:

```text
ratio: 9:16
shots per 60-90s episode: 8-12
style: vertical mobile drama, close-up heavy, emotion readable
```

## 2. Short Drama Adaptation

Build an adaptation bible in the conversation:

```text
- title / genre
- main characters and relationships
- protagonist desire
- core conflict engine
- must-keep plot points
- secrets / reveals / reversals
- recurring locations
- visual motifs
- continuity constraints: age, wardrobe, injuries, props, money, rules
```

Each episode should usually follow:

```text
opening hook → setup → conflict → escalation → reversal/reveal → cliffhanger
```

Rules:

- Internal thought → visible action, prop, expression, or dialogue.
- Long exposition → conflict scene or reaction beat.
- One beat must be visually clear in one shot/panel.
- Keep the first three seconds strong.
- End with a hook, reversal, danger, or emotional question.
- Prefer faces, reactions, hands, phones, doors, documents, money, wounds, and reveals over abstract narration.

## 3. Character and Scene References

A character appearing more than once needs one approved visual anchor; do not rely on text description alone. Use a user-authorized image or create a reference through the host's generation flow, show it for approval, and reuse the same resulting material through a role advertised by the selected model.

Character reference prompt:

```text
角色设定图，干净背景，现实主义竖屏短剧风格。
[角色名]，[年龄]，[身份]，[体型]，[发型]，[五官/气质]。
固定服装：[服装]。
包含正面全身、半身近景、侧面小头像，必须像同一个人。
不要水印，不要多余文字，不要夸张动漫风。
```

For recurring locations, create a scene reference only when needed. Too many references can confuse layout and identity.

Before optional generation, read `../model-routing/SKILL.md`, then:

1. Query live image-model capabilities.
2. Preserve a user-selected model; otherwise choose the best available specialist for the shot/sheet task and use the advertised default only as fallback.
3. Apply that model's prompting profile and use only advertised ratio, resolution, duration, material roles, and limits.
4. Hand the complete prompt, references, and parameters t

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: video-fission
description: >
  Create controlled variants from one owner-authorized source video. Use when
  the user explicitly asks for video fission, multiple video variants,
  controlled variations, or several hypotheses from the same clip. Analyze the
  source first, then resolve what should vary before proposing any generation.
metadata:
  author: renoise
  version: 0.2.2
  category: video-production
  tags: [video, fission, variants, experimentation, portable]
---

# Video Fission

Create a controlled batch of variants from one source video. This is an experiment, not a multi-shot production workflow: vary one axis, or at most two, and lock everything else.

## Runtime Boundary

Use only capabilities exposed by the current host. The source must be one conversation attachment, material, task result, or other video that the host identifies as owner-authorized. Never invent a source, request a host filesystem path, or use more than one source video.

Live model capabilities are authoritative for availability, roles, role combinations, limits, duration, ratio, resolution, and audio controls. Inspect them for every fission run; model names below are routing preferences, not permission to assume a capability.

## Hard Gates

1. **Analyze before resolving the direction.** Once the source is available, use the host's video-analysis capability before finalizing what to vary. If analysis is unavailable or fails, stop. Analysis creates no generation task.
2. **Clarify only when blocked.** If the initial request already names a usable, safe experimental axis, use it after analysis without restating it for text confirmation. Ask one focused question only when the axis is absent, unsafe, or ambiguous; allow a second axis only when the user explicitly needs it.
3. **Default the count.** Use **4 outputs** when no count is supplied; do not ask merely to confirm that default. Four is not a hard cap: accept another reasonable count of at least two, constrained only by live service limits, the total estimate, and the user's budget.
4. **Use one logical batch.** Hand the complete disclosed experiment to the active host execution workflow. Use a native batch primitive when the host exposes one; otherwise follow its documented ordered execution path. Do not invent tool names or execution interfaces.

## 1. Analyze the Source

Report the analysis in the user's language, including:

- subject, setting, actions, camera, composition, lighting, style, pacing/edit structure, duration, aspect ratio, and audio/dialogue;
- dimensions that appear fixed and plausible dimensions to vary;
- uncertain or inferred details as warnings.

Do not resolve an unstated direction until this report exists. If the request already supplies a usable axis, disclose how the analysis maps to it and proceed. Otherwise ask one focused question:

> Which direction should the variants explore? I recommend one axis from this clip's analysis; we can use at most two. The default is 4 outputs, or name another reasonable count.

Offer only source-relevant directions, such as action/motion, camera treatment, pacing, atmosphere/lighting, performance, or transformation. Do not preselect an absent direction for the user.

## 2. Use the Source Video Directly

This workflow has one generation path:

1. Select MiniMax H3 Max (`hailuo-h3-max`) only if the live capability advertises `reference_video`.
2. Use the exact owner-authorized source analyzed in Step 1 as every variant's sole `reference_video` input. If the source reference changes, analyze the replacement before continuing.
3. Refer to that source as `Video 1` in every generation prompt.

Do not extract or upload a frame, and do not replace the source with a `first_frame`. Before handing off paid execution, compare the analyzed source with the live capability's reference-video duration and count limits. If the source exceeds a duration limit, report its measured duration and the live limit when available, ask the user to

Preview of the first 4,000 characters. Read full instructions →

View saved version →

---
name: video-remake
description: >
  Recreate or remix one supplied reference video with replacement characters,
  products, branding, props, or scenes. Use when the user asks to replicate a
  video, remake a clip, 复刻视频, 剪同款, 换脸, or make a version of a supplied
  video with controlled replacements. The source video must remain attached.
metadata:
  author: renoise
  version: 0.1.3
  category: video-production
  tags: [video, remake, replication, replacement, portable]
---

# Reference Video Remake / 复刻视频 / 剪同款

This workflow resolves replacement slots before final generation. The current host owns authorized media analysis, materials, live capabilities, costs, spending approvals, and tasks. This skill owns slot matching, creative decisions, and resumable plan state kept in the conversation.

## Runtime Boundary

Use only capabilities and references exposed by the current host. Do not emulate missing analysis/material/task operations. When you have a shell (the host's own or a cloud sandbox tool such as `sandbox_exec`), your own code (editing, compositing, motion graphics, music) is available alongside generation, as in director's Runtime Boundary; use it wherever it brings the remake closer to the reference. Before selecting a model or writing prompts, read `../model-routing/SKILL.md` and inspect live capabilities.

Use the user's language for analysis, plans, approvals, and results. If retained or replacement content contains dialogue, voiceover, or narration, use the explicitly requested or safely inferable spoken language; clarify only when ambiguous, and keep every spoken line verbatim in that language.

## Non-Negotiable Source Policy

The source video is always attached to final generation through a compatible video role advertised by the selected model.

Before planning replacements:

1. Query live video-model capabilities.
2. Select a model that advertises both a compatible source/reference-video role and every image role needed by replacement slots.
3. Check guidance, reference counts, duration, ratio, audio behavior, and role combinations.
4. If no model supports the complete source-video + replacement-image combination, stop and explain. Never omit the source video or invent a role.

The final prompt must state that the source video supplies timing, camera motion, composition, transitions, effects, pacing, and emotional beats. Replacement materials supply identity, product, wardrobe, props, and other slotted content. This text reduces accidental copying but is not a security boundary; normal moderation rules still apply.

## Phase 1 — Analyze and Build a Remake Plan

Use the host's media-analysis capability in template/video mode on the authorized source. If that capability is unavailable, stop; do not request a local command or fall back to copied model code.

That analysis watches and listens, so it carries content, dialogue, music and mood. When you also have a shell, inspect the source yourself to complement it: measure exact cut points, beats, durations and loudness, and look closely at frames of transitions, typography and grading. Use both; the analysis remains the required first step.

The result should contain:

- factual analysis: summary, timeline, composition, style, subjects, and audio;
- a model-neutral prompt with `{{slot_id}}` placeholders;
- slots: each replaceable character/product/object/scene/style plus a reference-image prompt;
- warnings: inferred or uncertain details.

Maintain this plan in the conversation so retries resume known task/material IDs instead of recreating charges:

```json
{
  "version": "v1",
  "source": {
    "authorizedRef": "host reference",
    "materialId": null,
    "role": null
  },
  "analysis": "structured analysis result",
  "videoModel": null,
  "imageModel": null,
  "prompt": "template containing {{slot_id}} placeholders",
  "slots": [
    {
      "id": "subject_1",
      "type": "character",
      "description": "replacement lead",
      "prompt": "English refer

Preview of the first 4,000 characters. Read full instructions →