# Storyboard

> >-

- **Type:** Skill
- **Install:** `agentstack add skill-godot-fun-godot-framework-storyboard`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [godot-fun](https://agentstack.voostack.com/s/godot-fun)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [godot-fun](https://github.com/godot-fun)
- **Source:** https://github.com/godot-fun/godot-framework/tree/main/.cursor/skills/storyboard

## Install

```sh
agentstack add skill-godot-fun-godot-framework-storyboard
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Storyboard

From **user materials only**, produce:

1. **Narration** per shot — **Chinese and English** (both required unless user opts out)
2. **Video prompt** per shot — ready for i2v / t2v
3. **Cover** — one still prompt for thumbnail/poster (after Spine + Assembly in the markdown)

Do not invent product facts, prices, logos, or claims not in the materials.
Style and length are agent-chosen from the content (no fixed genre or duration).

## Inputs

Any mix of stills, clips, text brief, and constraints. Optional: a delivery file path.

If goal/audience is ambiguous, state one short assumption and proceed. Ask only when a missing fact would make the storyboard unusable.

## Delivery

| Mode | Behavior |
|------|----------|
| User gives a file path | Write the **full** storyboard markdown to that path. Chat: short confirm (path, runtime, shot count) only |
| No path | Full storyboard in chat |

Treat a path as the **output file** when:

1. User says write to / save as / put in + path
2. Skill request is paired with **one** main `.md` / `.txt` document
3. Path is an empty or draft file clearly opened for this output

**Rules:**

- Always **read** the target file first if it exists. Non-empty body = text material; then **replace** with the full storyboard (keep useful facts in `## Materials` / Spine).
- One doc + images → write to the doc; images are materials only.
- Explicit output path + separate brief → write only to the output path.
- Several docs, unclear target → prefer the path next to the skill invoke; if still ambiguous, ask once.
- User names a directory only → create `storyboard.md` there.

## Workflow

1. Detect delivery target (file vs chat)
2. Inventory materials (read delivery file if present)
3. Infer Visual Style (once for the whole piece)
4. Design story spine (hook → develop → payoff / CTA)
5. Break into shots (one clear idea each; duration free) — **Shot 01 is the eyeball grab** (see Shot 01)
6. Write bilingual VO + video prompt per shot
7. Write Assembly (after Spine), then Cover (after Assembly)
8. Consistency pass; deliver in required format

### Visual Style (once)

Medium, mood, color/light, camera language, motion energy, aspect (default **16:9**). Keep consistent across prompts unless a deliberate style shift is story.

### Spine patterns

- Product → desire/problem → reveal → benefit → close
- Character → setup → turn → resolution
- Trailer → hooks and escalating beats
- Explain → claim → show → reinforce
- Attention-scarce / fragmented viewing → **grab in Shot 01** → develop → payoff / CTA

Spine may note what Shot 01 uses to stop the scroll; that hook is **not** a summary of the whole piece.

### Shot rules

- One idea per shot; prefer a **visible cause of motion**
- Reference still present → **i2v** (motion relative to that frame)
- No frame → **t2v** (full self-contained scene)
- Respect user aspect; default 16:9
- No invented logo text, legal claims, or competitor names

### Shot 01 (hook — grab attention)

Attention is fragmented: **Shot 01 must catch the eye**. It is an opening line that stops the scroll—not a summary of the video, and not necessarily the piece’s main thesis.

- Prefer a sharp cold open: tension, curiosity, contrast, surprise, or a vivid concrete moment
- VO + picture work as a hook; soft mood builds, empty atmosphere, or early detail dumps fail here
- The main argument / product reveal can land in later shots; Shot 01 only needs to pull the viewer in
- If materials already give a hook line, keep it and amplify — do not invent facts

### Narration (bilingual default)

| Field | Use |
|-------|-----|
| **Chinese** | Spoken Chinese for TTS / record (or `(no VO)`) |
| **English** | Spoken English for TTS / record (or `(no VO)`) |

- Same idea in both languages (natural spoken, not word-for-word).
- Length vs duration: Chinese ~3–4 chars/sec; English ~2–3 words/sec. Tighten the side that overruns.
- **Sync on edit:** if either VO changes, update the other VO and related fields (`Duration`, `Visual`, `Camera`, `Video prompt`, Cover if the beat changes) in the same edit.
- User gives one language verbatim → keep it; write a natural equivalent for the other.
- User asks for only one language → omit the other field.

### Video prompts

Self-contained for a generic model. Include: subject + action in time order, camera (frame + move), environment, light/color, motion intensity, continuity anchors.

- i2v: start with `Image-to-video from provided still: …` then motion (+ keep composition unless changing)
- t2v: full scene + Visual Style cues
- Prefer concrete verbs; avoid named living artists / unlicensed IP not in materials
- Optional: `Avoid: flicker, morphing faces, extra limbs, watermark, text overlay`
- **English** prompt body unless user requires Chinese

### Cover (required unless user skips)

Place `## Cover` **immediately after** `## Assembly`, before `## Shots`.

- One focal subject; thumbnail-readable; match Visual Style
- Still only (no camera motion as main instruction)
- On-image text only from materials; else `no on-image text`
- Aspect: match video, else 16:9
- Prefer i2i from hero still when available; else t2i
- Optional: `Avoid: watermark, blurry text, extra fingers, cluttered UI, low-contrast mud`

## Output format (required)

Section order is fixed: Materials → Visual Style → Spine → Assembly → Cover → Shots.

```markdown
# Storyboard — [working title]

## Materials
- [asset or note → role]

## Visual Style
- Medium:
- Mood:
- Color / light:
- Camera:
- Motion energy:
- Aspect: [e.g. 16:9]

## Spine
[1–4 sentences: arc + rough total runtime]

## Assembly
[shot order, total runtime, TTS/BGM/stitch notes if obvious]

## Cover
- **Aspect:** [e.g. 16:9]
- **Source:** [t2i / i2i from …]
- **Visual:** [one-sentence composition]
- **On-image text:** [from materials, or none]
- **Image prompt:**
  ```
  [still prompt — English preferred]
  ```
- **Avoid (optional):** …

## Shots

### Shot 01 — [short title — cold open / hook]
- **Duration:** ~Xs
- **Source:** [file / t2v / i2v from …]
- **Visual:** [composition]
- **Camera:** [framing + move]
- **Chinese:** [spoken Chinese, or (no VO)]
- **English:** [spoken English, or (no VO)]
- **Video prompt:**
  ```
  [full prompt — English preferred]
  ```
- **Avoid (optional):** …

### Shot 02 — …
…
```

## Quality bar

- [ ] File path given → full markdown **saved there** (UTF-8); not chat-only
- [ ] Section order: Spine → Assembly → Cover → Shots; every shot has Chinese + English + Video prompt (or user opt-out)
- [ ] VO languages sense-aligned; durations match speak length
- [ ] **Shot 01** grabs attention as a cold open (not a thesis summary; no slow-burn open)
- [ ] Facts trace to materials; style coherent; i2v points at the right still
- [ ] No video/image generation APIs unless user separately asks
- [ ] No invented output path when user gave none → chat delivery only

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [godot-fun](https://github.com/godot-fun)
- **Source:** [godot-fun/godot-framework](https://github.com/godot-fun/godot-framework)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** yes
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-godot-fun-godot-framework-storyboard
- Seller: https://agentstack.voostack.com/s/godot-fun
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.