SkillAgentSearch skills...

scenario-blender-blockout

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…

Install / Use

npx skills add scenario-labs/skills --skill scenario-blender-blockout

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Supported Platforms

Universal

Our assessment of scenario-blender-blockout

scenario-blender-blockout scores 86/100 on our quality scale, 2449th of 4,698 Development & Engineering skills we index.

Its SKILL.md is 19 KB long, well organised into 9 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 29 days ago, so scenario-blender-blockout 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. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-11-10. Automated pattern scan on 2026-11-10. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

scenario-blender-blockout compared with similar skills

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

SkillScoreStarsUpdatedFormat
scenario-blender-blockout (this skill)by scenario-labs861.0k29d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install scenario-blender-blockout?
Run npx skills add scenario-labs/skills --skill scenario-blender-blockout. The install tabs above show the steps for each supported agent.
Which AI agents does scenario-blender-blockout 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-blockout safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. 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-blockout still maintained?
The repository was last updated 29 days ago, so scenario-blender-blockout is actively maintained.

name: scenario-blender-blockout description: "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." license: MIT

Blender blockout for a render-to-real video pass

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.

1. Restate the brief as a build plan

Before any call, write down:

  • Elements and their primitive: "bus = long box with a marked front", "figures = colored capsules". Never model past what the brief names.
  • Dimensions in meters for everything; when the brief is silent, take them from the contract tables and say so.
  • Format: integer fps, aspect, seconds. The range is 1 to fps x seconds (8 s at 24 fps: 1..192).
  • Shots: count, move, lens, framing invariants ("hero always in frame, full figure"), cut style; beats pinned to seconds, converted to frames now.
  • Levels: density (simple, medium, advanced, expert: footprint, elements, heroes, extras, shots), fidelity (rough, shaped, detailed) and color scheme, read off the brief and set apart: levels. Where the brief is silent (naming only heroes and shots is silent): advanced, shaped, category colors, and say so; drop to simple or medium only for one actor in one place. Expert means many elements, movers and cuts, never finer blocks.
  • Video model, now: cast style and prompt grammar depend on it (list_models on the plugin lane, recommend on the hosted route).
  • Cast style per character (cast): a stand-in with limbs hands the model a gait to copy; one without limbs lets it invent body and motion. Default heroes to colored capsules, featured (two or three signature features: goggles, a hood, a held lantern) when characters must stay apart or carry the story's object; a rigged gray mannequin only when the blockout must own limb motion. Tell the user the style chosen, its cost in control, and that the others can be A/B tested on a short window.
  • Identity colors: a hero takes the brief's color ("yellow raincoat": yellow) as the nearest 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.
  • Deliberate gaps the video model fills, and acceptance tests the brief states: they become mandatory audits.

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.

2. Output contract

Four deliverables: the scene, a locked camera timeline, the playblast, the hand-off sheet.

  • Scene hygiene. Role prefixes (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.
  • Scale. Meters, Z up, ground at z = 0, figure roots at the feet. The model keeps every mass where it is at its size, mistakes included. Nothing familiar for scale: add a REF_ figure.
  • Color separates masses and names identities. One saturated color per hero (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.
  • Timeline. 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.
  • Camera rigs. Rail: 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.
  • Lens. One lens per shot from shot size (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.
  • Easing. Bezier keys with auto-clamped handles (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.
  • Handheld is NOISE F-curve modifiers, never keyed jitter. Measure the result with B.audit_handheld against the budget in the contract; animation_data_clear() removes the modifiers, so re-add them after rekeying.

3. Channel: the plugin or headless

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.

4. Build order

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.

  1. Probe, read-only: scene_summary, datablocks_summary (headless: bpy.data). Other work present: new scene.
  2. Format and scaffolding: B.make_scene, B.lock_format, B.collection tree, B.park, dark world.
  3. Set: kits at the chosen fidelity (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.
  4. Figures: 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=...).
  5. Props and vehicles: literal primitives at true position. Mark a vehicle's front in geometry (light blocks and grille in front, dark red behind); wheels at z = radius (kit wheels: body mesh). Spinning wheels, cyclists (contract): K.drive a "bicycle" K.vehicle, K.pedal its rider, never K.walk_path. No loose blocks near a figure.
  6. Light: one area light; named key, fill, rim only when the brief designs light.
  7. Cameras: rigs and lenses per shot, B.bind_cuts.
  8. Motion polish: B.key_rail and B.smooth_keys, keys past cuts, handheld, vehicle travel as one monotone curve keyed per frame.
  9. Audit (section 5) until clean. When set dressing hides the hero, move the blockers and keep the camera plan.
  10. Finalize: frame 1, shot 1's camera, B.audit_frames, `

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars1.0k
CategoryDevelopment
Updated29d 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