SkillAgentSearch skills...

scenario-blender-previs-storyboard

Use when turning a script or story into previs, layout, storyboards or an animatic in Blender: beats to shot list, camera and lens per shot, staging, camera height, 180-degree rule, screen direction, shot sizes, when to cut, camera moves, timing stills in the Video Sequencer, markers bound to camera…

Install / Use

npx skills add scenario-labs/skills --skill scenario-blender-previs-storyboard

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Supported Platforms

Universal

Tags

Our assessment of scenario-blender-previs-storyboard

scenario-blender-previs-storyboard scores 86/100 on our quality scale, 2367th of 4,705 Development & Engineering skills we index.

Its SKILL.md is 20 KB long, well organised into 10 sections and no code examples: a thorough specification that gives an agent plenty to work with.

With 1,048 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
13/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 35 days ago, so scenario-blender-previs-storyboard is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.

Automated pattern scan on 2026-11-20. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

scenario-blender-previs-storyboard compared with similar skills

All 4 of these similar skills score higher than scenario-blender-previs-storyboard; compare them before choosing.

SkillScoreStarsUpdatedFormat
scenario-blender-previs-storyboard (this skill)by scenario-labs861.0k35d agoSKILL.md
taste-skillby Leonxlnx100120.0ktodayCLAUDE.md
hyperframesby heygen-com10088.2ktodayCLAUDE.md
ai-job-searchby ai-job-search-dev10073.0ktodayCLAUDE.md
claude-howtoby luongnv8910047.5k1d agoCLAUDE.md

Frequently asked questions

How do I install scenario-blender-previs-storyboard?
Run npx skills add scenario-labs/skills --skill scenario-blender-previs-storyboard. The install tabs above show the steps for each supported agent.
Which AI agents does scenario-blender-previs-storyboard work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is scenario-blender-previs-storyboard safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is scenario-blender-previs-storyboard still maintained?
The repository was last updated 35 days ago, so scenario-blender-previs-storyboard is actively maintained.

name: scenario-blender-previs-storyboard description: "Use when turning a script or story into previs, layout, storyboards or an animatic in Blender: beats to shot list, camera and lens per shot, staging, camera height, 180-degree rule, screen direction, shot sizes, when to cut, camera moves, timing stills in the Video Sequencer, markers bound to cameras, Story Tools, Grease Pencil or 2D/3D hybrid boards. Also when an animatic shows the wrong frame, blocking keys are not stepped, Rigify operators are missing, or viewport render fails headless." license: MIT

Previs, layout and storyboarding

Expert previs conveys an idea well enough to be judged, as cheaply as possible: one fact per beat, every shot designed for what the audience must feel, timing found in the edit from stills. The camera is the audience's body; where it stands, how high and through which lens decides the emotion, so every non-neutral choice needs a stated reason. If a sibling skill named here is missing from your available skills, load it with skill_get (Scenario MCP) or ask the user to install it (https://github.com/scenario-labs/skills#install); unattended, proceed from tool schemas and flag the gap.

REQUIRED BACKGROUND: scenario-blender-expert (execution channel, review loop, 5.2 API changes).

Toolkit: scripts/bx_previs.py (tested on 5.2.1): import sys; sys.path += ["<this skill>/scripts", "<scenario-blender-expert>/scripts"]; import bx_previs as P.

Which skill. This one: story previs and animatics judged by a director and an editor. Out of scope: a playblast that guides a render-to-real video model (Seedance). It follows other rules (saturated color identities, no lens jump on a cut, eased moves, a hand-off sheet) that the workflow and P.audit below do not apply or check, so do not hand a director's animatic to a video model as is: rebuild it with scenario-blender-blockout, where characters usually become colored capsules the video model animates itself. Shared: metric Z-up, roots at the feet, one camera per shot bound to a marker, to_track_quat('-Z','Y') look-at. Strokes: scenario-blender-grease-pencil. Animation after layout: scenario-blender-animation. Real rigs: scenario-blender-rigging.

Stance (the expert delta)

  • Hjalti Hjalmarsson: write the beats-of-information list before any shot. One fact per line, because a viewer takes in one thing at a time. Group consecutive beats into shots; a new treatment re-orders the same facts. A missing beat means the idea never gets a fair test.
  • Hjalti: theater first, then cinematic; shots cost time. A locked-off version judges the acting; the same beats told in shots ran about 2x (up to 3x) because every cut must be read (13/22/25 s vs 47/40 s). The oversimplified version is always too short and hides logistics (a character cannot cross the room in 10 frames).
  • Charge recipe (Hjalti): treat every frame as a storyboard drawing. 10 frames per shot, keys CONSTANT, an A/B alternative on the next frame, the winner on the decade frame, stills exported with versioned names, timing done in a separate edit.
  • Hjalti: when in doubt, eye height; lock the lens early by A/B. Two characters: split their eye heights. Low or high is a statement. Poses built for one lens do not survive a lens change.
  • Dillon Gu: composition and focal length are separate decisions, and cuts can kill a mood. The audience stands where the camera is. Leaving the space removes the danger; two inanimate inserts in a row lower tension.
  • Cheat for the camera, but key before you cheat (Hjalti, Charge, Renato Roldan). Resize, float, swap props per shot; in a shared timeline an unkeyed cheat breaks the earlier shots.
  • Previs is the cheapest version that still conveys the idea (Hjalti, Charge). Animate only shots whose camera move is the storytelling; everything else is one still, push-ins faked on the still in the edit. Grays in Workbench, no mood lighting, mannequins before rigs. P.audit refuses a camera moving inside a still shot, keys between block starts and a non-Workbench engine.
  • After each cut the eye must find one thing (Hjalti). Restage a character in front of a competing subject; keep the angle that preserves the emotion (he refused a side cut that turned Rex into a silhouette).

Establish first

| Input | Changes | Default when silent | | ---------------------- | ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Format | every composition (Charge: lock it first) | 1920x1080, 24 fps, stills at 50 % | | Treatment | shot count, runtime | theater pass, then cinematic | | Method | agent has no tablet | 3D previs with mannequins; drawn boards only on provided art; Rigify proxies only on request (P.rigify_proxy, Rigify is off under --factory-startup: P.ensure_rigify() first) | | Mood or director style | lens, height, motion per shot | neutral grammar, deviations stated per shot | | Runtime budget | durations | about 1.6 to 1.9 s per beat for a cinematic cut (derived from Hjalti's slide: 25 beats, 8 shots, 40 to 47 s) | | Journeys | screen direction | out left to right, back right to left (Charge) | | Deliverable | outputs | shot list, contact sheet, floor plan, animatic MP4 clean plus burn-in, versioned .blend |

Workflow

  1. Script to beats. Asset list, then numbered beats, one fact each; mark every beat you add. GATE: P.shot_list(BEATS, SHOTS) raises on a missing, duplicated or reordered beat.
  2. Set and proxies. P.setup_scene (format, Workbench, grays, Standard view transform); P.prop for real-scale set pieces; P.mannequin for characters (root at the feet with eye_height, four pivot controls as the layout subset). Grays, one pop color for the hero (Renato: red). GATE: scale reads next to a door (2.1 m) and counter (1.0 m).
  3. Theater pass. One locked-off camera (cam shared, fit="all", 35 mm, mean eye height) framing the action's extremes; one block per beat group. GATE: in the P.audit rows every subject's head_in and feet_in is true at every block; theater edit timed.
  4. Cinematic plan. List several openings, re-order beats, group them into shots with intent, size, lens, height, dur. P.floor_plan with the action line and journey paths before judging cameras. GATE: one side of the line; journeys follow the direction rule.
  5. Blocking. For each block: sc.frame_set(f) (holds the previous pose), set only what changes, P.key_block(all_movables, f); cheats go through the same keys; then P.make_stepped. GATE: P.stepped_report == {}; the cheat check at neighboring shots.
  6. Cameras. P.build_shots places each camera from size, lens and eye height (or explicit loc/aim), sets an opaque passepartout (Charge: see only the composition; P.passepartout(sc) for other cameras) and binds a marker at its first frame. P.ab_lens on key shots before posing further. GATE: P.audit(...)["problems"] == [].
  7. Look. P.contact_sheet and open it. Characters merging with a dim set: P.fog_for_shot(sc, t, chars) (Hjalti: depth fog for readability, not lighting; behind the subjects, keyed to that shot), P.values_at hero vs backdrop. GATE: the visual list under Quality gates (in S6 only the pictures caught the occlusions and the cut-off wide).
  8. Edit. P.render_stills, then P.animatic (image strips held dur seconds, push on stills, live shots as scene strips, sounds, burn_in). One continuous action from several angles (Pablo, Story Tools): a live shot plus cover=True shots become one scene strip soft-split per camera; retime with P.retime_cut (the marker follows), never by moving keys. GATE: runtime within budget; frames pulled from the MP4 match the cut list.
  9. Iterate in a new scene pair (02_blend/02_edit) and new version numbers; nothing overwritten.

Numbers

| Value | Relative to | Source | | ------------------------------------------------------------------------------ | ------------------------------------------ | ----------------------------------------------------- | | 10 frames per shot block, 20 only when justified; starts on 10, 20, 30 | previs timeline | Charge | | Shots named in tens (sh010, sh020) | markers | Hjalti on screen | | 35 mm theater frame; about 60 mm for an isolating key shot | 36 mm sensor | Hjalti | | F-stop 5.6, clip 0.01 to 200 m on the camera rig | Hjalti's rig | Hjalti | | 13 / 22 / 25 s theater vs 47 / 40 s cinematic | same script | Hjalti slide 00:46:01 | | 3 poses for an anger burst (anticipation, overshoot, settle) | one beat | Hjalti | | 6 fps boarding, retimed in the edit | board scene | BouncyBrain | | Eye tolerance 0.15 m; drawing breaks past 70 degrees from camera | audit thresholds | [added] | | Visible height = subject height x 4 / 2 / 1.15 / 0.8 / 0.6 / 0.4 / 0.25 / 0.12 | ews, wide, full, mws, medium, mcu, cu, ecu | [added] | | Distance = visible height x lens / sensor height (20.25 mm at 16:9) | lens swap at equal size: d2 = d1 x f2 / f1 | [added] | | Handheld NOISE 0.010 to 0.018 rad, 18 to 26 frame scale | camera rotation | video guides; measured peak-to-peak = 0.66 x strength |

Camera language

| Choice | Reads as | Source | | ------------------------------------------------------------------------------- | ---

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars1.0k
CategoryDevelopment
Updated1mo ago
Forks129

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions