- name
SKILL.md
O arquivo da skill permanece no repositório do publicador.
Cole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add scenario-labs/skills --skill scenario-blender-blockout -a cursor -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add scenario-labs/skills --skill scenario-blender-blockout -a claude-code -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add scenario-labs/skills --skill scenario-blender-blockout -a codex -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add scenario-labs/skills --skill scenario-blender-blockout -a grok -yEnvie a mensagem copiada em um chat do Grok Bot. O Bot busca este SKILL.md no GitHub e o adiciona às skills que todos os seus Bots compartilham.
Install this skill: https://github.com/scenario-labs/skills/tree/HEAD/skills/dcc/blender/scenario-blender-blockoutDo publicador
The blockout is the guide clip: the video model copies the camera path, framing, lens feel, easing,
cut points, shot lengths, the position and scale of every mass, figure facing and every trajectory,
and it invents the rest from text and images (materials, light, weather, what each proxy really is,
faces, wardrobe, extras, sound). So the blockout has full authority over motion and layout and none
over look. Ambiguity ruins the pass; crudeness does not: a bent lamppost comes back as a snake,
loose limb blocks as extra people, an unmarked car driving backward. Fix identity in geometry first,
in prompt text second, and judge the result on a synced side-by-side of playblast and video, never
in the viewport alone. 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).
Video generation: scenario-blender (the plugin's quote, generate and place flow), the scenario
skill (connection, uploads, jobs) and scenario-seedance (reference-video fields).
Toolkit: scripts/bx_blockout.py:
import sys; sys.path.insert(0, "<this skill>/scripts"); [sys.modules.pop(m, None) for m in ("bx_blockout", "bx_kits")]; import bx_blockout as B,
where <this skill> is the installed folder's absolute path. The pop drops a copy an earlier run
left in Blender's one Python. Builders are get-or-create by name, so a call can run again, and they
refuse a name the user's own work already holds (names are global to the file). An empty audit
result is a pass. The module docstring shows the call order.
scripts/bx_kits.py (import bx_kits as K, same rules) adds buildings,
stalls, trees, lamps, rocks and vehicles at three fidelity tiers, figures in four cast styles,
crowds, traffic, color schemes and K.audit_budget. Four worked scenes, simple to expert, with
render-pass results: examples (harness,
1, 2,
3, 4).
Which skill. This one: guides for a video model. Story previs and animatics judged by a director and an editor: scenario-blender-previs-storyboard; an approved animatic that must guide a video model is rebuilt here.
Before any call, write down:
list_models on the plugin
lane, recommend on the hosted route).B.PALETTE color, else the next free one: red, blue, green, yellow, purple, cyan. Two heroes in
one color, or black, white, gray, brown: contract.Decide what the brief leaves open and record the decision; do not stop to ask. Spending is the
exception: the user approves every Scenario price (section 6). With a reference image: list its
masses, block them at plausible scale, match camera height and lens, render_still from the camera,
compare, adjust until the composition matches, and only then animate.
Four deliverables: the scene, a locked camera timeline, the playblast, the hand-off sheet.
ENV_, FIG_, PRP_, CAM_, CRV_, RIG_, NULL_target_,
full table in the contract), one root collection with role sub-collections. Park the default Cube,
Light and Camera with B.park, never delete. If the file holds other work, build in a new scene
(B.make_scene) and touch nothing existing; every object must trace to one of your stages.REF_ figure.B.PALETTE), the
set in one K.scheme (category hues by default, identity grays, or material colors), extras in
mid grays, one light, a dark world. B.paint and the kits set object color and materials; a kit
carries several colors, so Solid view needs color type Material (B.solid_view()'s default and
the playblast's). An all-gray playblast has lost identity. Recolor a kit through its arguments:
its materials are shared per color. Grid or checker texture only where the camera travels and
depth must read, declared "replace, never inherit" in the sheet.B.lock_format before any geometry: integer fps, frames 1 to fps x seconds,
1920x1080 (2520x1080 for 21:9) at 100 %. One camera per shot, bound to a CUT_ marker on its
first frame (B.bind_cuts), hard cuts, zero transition frames.B.rail_camera (curve, dolly on Follow Path, aim with Track To, camera).
Handheld tracking, straight push-in and multi-shot masters: recipes in the contract. Reframe by
moving the aim target, never by rotating the camera.B.lens_for_coverage; 28 mm orbits, 42 to 45 mm
over-the-shoulder, 24 to 30 mm interiors, 85 mm macro), clip_start 0.05. A cut changes lens only
by changing camera: never key a lens step on a cut frame. A lens may ease inside a shot (a
deliberate zoom), never jump.B.smooth_keys); speed is key spacing on the
rail (B.key_rail), a pause is two near-equal values. LINEAR only for per-frame baked travel
(vehicles, wheels). Keys run past every cut so nothing stops on the boundary.The live channel is the plugin's local Scenario MCP server, scenario-blender (the guide at
blender.scenario.com calls the plugin Scenario for Blender). Tool
table, call limits and recovery after a timeout: plugin. The two that bite
first: execute_python stays off until the user enables Allow connected agents to run Python (a
PermissionError means ask), and a call stops after 120 s, so send one stage piece per call and run
B.stage_backup(label) after each stage.
The plugin's own tools (plugin): its paid Blockout suits a generic
Stage 2 set, with no figures, cameras or identity colors; camera_path keys one shot around a
static center, never tracking or multi-shot (B.rail_camera); Render Video is the video pass.
Headless, with no plugin: run each stage through scenario-blender-expert's headless helper. Load
the preceding .blend, check it with B.guard, extend it, then save a new B.stage_backup(label)
for the next stage. The examples harness is only for one-shot
builds from factory startup: start() deletes all objects, including prior stages. Never reuse it
to resume a backup. The 120 s limit is plugin-only.
A reset is recovered from the last backup (contract). Every call or stage
script starts with B.guard(expected_file=..., scene=...): queued calls land in whatever file is
open.
scene_summary, datablocks_summary (headless: bpy.data). Other work
present: new scene.B.make_scene, B.lock_format, B.collection tree, B.park, dark
world.K.building, K.stall, K.tree) or thick boxes (B.box)
at true scale, repeats as linked duplicates (K.instance). Or the plugin Blockout for a generic
set.K.figure(..., style=, features=) per hero in the chosen cast style, root at the
feet, facing along travel (cast). Travel with K.walk_path from a table of
(frame, position), stride 0.42 x height for a walk, about 0.7 for a run; gestures with K.pose;
extras with K.crowd(style=...).K.drive a "bicycle"
K.vehicle, K.pedal its rider, never K.walk_path. No loose blocks near a figure.B.bind_cuts.B.key_rail and B.smooth_keys, keys past cuts, handheld, vehicle travel as
one monotone curve keyed per frame.B.audit_frames, B.state_audit, final backup, then
playblast and hand-off sheet.Audit each shot's own subject (the wheel for a macro, the hand for an insert). Then look:
set_frame and render_still at the first, middle and last frame of every shot, and check what
numbers miss: a vehicle's front, connected figures, rigid props without organic curves, nothing
stray at frame edges, an ending as locked as the opening. Thresholds and readings:
audits. An audit samples every step frames; on a long shot raise step to
stay under the call limit.
Playblast. Headless, on the latest B.stage_backup copy, with scenario-blender-expert's
bx_review.playblast(out_path, res_pct=100): an H.264 MP4 of the scene camera over the frame range
in Workbench, cuts following the bound markers. Use the session's binary (bpy.app.binary_path): an
older blender on PATH refuses the file. With no shell, the same call through execute_python
blocks Blender while it renders: keep it to short clips, and after a timeout look for the file
before running it again. Add camera stills at each shot's start, middle and end.
Hand-off sheet, built from the scene (template):
K.cast() rows, the cut list from B.cut_list() with exact times;Video pass, always through Scenario, after the user approves the exact price. Unattended, stop
at the quote (estimate_cost or dry_run), report it, and skip local uploads that need the user's
file choice:
B.solid_view() so the capture shows identity colors,
force_solid false (it turns everything one gray), a timeline length the model accepts, then
list_models, model_schema, render_form (configure with parameters
{"duration": <clip seconds>}, prepare, inspect), estimate_cost, generate, wait_for_job
and the result application, steps in handoff Route 1. The capture is a
silent 1280x720 clip.scenario
skill shows, discover a model that takes a reference video, model_schema_get, model_run with
dry_run first, jobs_wait, asset_download.Write the prompt motion-first: the clip is rehearsal footage, the cast is described by role and
motion, never by the proxies' shapes, and style comes from a four-panel style board rather than one
restyled frame. A capsule cast adds a stand-in clause (the capsules only mark position, height, pace
and heading) and a gait clause (cast). On the plugin lane the plugin states
the clip's and images' roles itself, so look holds only cast and style. Grammar, clauses and
tested limits: handoff.
Brief: "10 s, 24 fps: a red runner sprints between crate rows toward camera in a warehouse; a blue guard steps out at second 6; handheld 35 mm backing away."
scene_summary {"fields": ["type"], "limit": 100}: the file holds other work, so build beside
it.execute_python: B.make_scene("BLK_warehouse"); next call B.guard(scene="BLK_warehouse"),
B.lock_format(24, 10) (1..240), collections, backup.B.box; backup.K.figure("red", 1.8, (0, 15, 0), style="featured", features=("hood",)), then K.walk_path to
(0, 1) by frame 200 with a sprint's stride (1.3 m); the blue guard, a capsule, steps into the
aisle over frames 144 to 156; backup.B.rail_camera("s1", [(0, 3, 1.5), (0, -1, 1.5), (0, -4, 1.5)], follow="FIG_red", target_offset=(0, 0, 1.2), lens=35),
B.key_rail("RIG_dolly_s1", [(1, 0), (260, 1)]), B.bind_cuts([(1, "CAM_s1")]), handheld noise
within budget.B.audit_frames(10, 24), B.audit_cuts(),
B.audit_framing({"CAM_s1": ["FIG_red", "FIG_blue"]}, whole=True),
B.audit_occlusion("FIG_red"), B.audit_handheld("CAM_s1"); move crates until clean.set_frame 1, 120, 240 with render_still each, and look. Backup, headless playblast,
B.cut_list() into the sheet.B.fcurves).Use when a text brief or a reference image must become a Blender blockout whose playblast guides a render-to-real video pass (a video model that takes a reference clip, such as Seedance, or the Render
---name: scenario-blender-blockoutdescription: Use when a text brief or a reference image must become a Blender blockout whose playblast guides a…---# skills/dcc/blender/scenario-blender-blockout/SKILL.mdVisão geral
Use when a text brief or a reference image must become a Blender blockout whose playblast guides a render-to-real video pass (a video model that takes a reference clip, such as Seedance, or the Render Video lane of the Scenario Blender Plugin): graybox or previs built for a video model, color-coded proxies at metric scale from rough to detailed, density levels from a simple shot to an expert scene with crowds, traffic and many cuts, character stand-ins chosen per video model (colored capsules, capsules with signature features, rigged gray mannequins), a camera locked to the timeline, rail or tracking camera rigs, lens per shot, framing and occlusion checks, a playblast, a hand-off sheet for the video prompt. Also when a render-to-real pass renders the proxies as boxes, reads one figure as two people, gives runners a stiff, lockstep or sliding gait, swaps a car's front and rear, drifts at the end, or the guide camera pops on a cut.
Perguntas frequentes
Baixe skills/dcc/blender/scenario-blender-blockout/SKILL.md do publicador ou copie o caminho e abra o repositório. O PlugMCP lista a skill e não hospeda o arquivo.
O publicador o mantém em https://github.com/scenario-labs/skills.
Claude, Cursor, Codex e Grok Build conseguem ler um SKILL.md que você adiciona a partir do repositório do publicador. O Grok Bot o instala quando você envia em um chat o link da pasta da skill no GitHub.
B.audit_handheldanimation_data_clear()