Agent skill

Scenario Unreal Cinematics

by scenario-labs in scenario-labs/skills

A skill your agent uses when making a trailer, cutscene, cinematic or short film in Unreal Engine 5.8 with Sequencer: shot lists, master and shot sequences, cameras, lenses, depth of field, camera…

MITAuto-check passedGame Development

Install Scenario Unreal Cinematics

skills CLI
$ npx skills add scenario-labs/skills --skill scenario-unreal-cinematics -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install scenario-labs/skills scenario-unreal-cinematics --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/game-engines/unreal/scenario-unreal-cinematics .claude/skills/scenario-unreal-cinematics && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
scenario-unreal-cinematics
GitHub stars
946
Token cost
~5.1k tokens
SKILL.md length
2,058 words
Files
8 (incl. scripts, references)
Skills in repo
146
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when making a trailer, cutscene, cinematic or short film in Unreal Engine 5.8 with Sequencer: shot lists, master and shot sequences, cameras, lenses, depth of field, camera…

  • Works in 9 steps: Scaffold (once per project). Production… → Plan the cut as data (python3). Shots,… → Build in one transaction (editor).… → …
  • Making a trailer
  • SKILL.md covers Stance (the expert delta), Establish first, Workflow and Numbers, plus 5 more sections
  • Runs Python scripts from its folder; calls npx

What it does

Scenario Unreal Cinematics is an agent skill from scenario-labs/skills. Use when making a trailer, cutscene, cinematic or short film in Unreal Engine 5.8 with Sequencer: shot lists, master and shot sequences, cameras, lenses, depth of field, camera cuts, spawnables, character animation in shots, per-shot lighting, Movie Render Graph or Movie Render Queue EXR renders, "render darker than the viewport", "first frames pop", "last frame missing", ACES or OCIO to DaVinci Resolve, the 180-degree rule, Sequencer Python, or reviewing a cut.

Its SKILL.md is about 5.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts and reference files (for example `references/critique.md`, `references/expert-notes.md` and `references/gui-paths.md`).

It sits in Game Development, covering Game development. It works with Unreal Engine and Python. The repository describes itself as: Get production-ready images, video, audio, and 3D from any AI agent: skills that pick the right model, price before spending, and keep characters and brands consistent through… The licence is MIT.

When your agent uses it

  • Making a trailer
  • Short film in Unreal Engine 5.8 with Sequencer: shot lists
  • Master and shot sequences
  • Character animation in shots

Example prompts

  • “render darker than the viewport”
  • “first frames pop”
  • “last frame missing”
  • “/scenario-unreal-cinematics”

Requirements

  • Python 3
  • Node.js

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

  1. Scaffold (once per project). Production defaults recorded once (CAT Production Setup or Project Settings) and copied into…
  2. Plan the cut as data (python3). Shots, sizes, lenses, camera and subject positions, motion, flags, cast (joints, meshes), stingers…
  3. Build in one transaction (editor). C.build_from_plan(plan): master with Shots and music, a spawnable Cine Camera per shot (lens keyed, Use…
  4. Board and lock the cut (latent editor). C.board_generator(..., preroll=True): first, middle, last frame per shot plus each shot's first…
  5. Performance and camera polish. Rack focus as keyed Manual Focus Distance (P6), camera moves as base plus offset plus shake layers (P7)…
  6. Lighting (with scenario-unreal-lighting-rendering). Temp light renders unblock everyone; C.lighting_masters(plan), render only those…
  7. Draft render and review. The review graph or the 5.8 Basic config; C.review_movie_cmd with the music (P10). GATE: C.check_render_output…
  8. Final EXR. Template graph per P8 with the CineWrittenFiles Execute Script (Editor Only)…
  9. Deliver. EXRs per shot, C.edl(plan), review MP4, C.delivery_note(plan, settings) (Resolve interpretation), JSON reports; notes split…

What it can do on your machine

Read from SKILL.md and the folder at commit f6f8ab7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Scenario Unreal Cinematics loads about 5.1k tokens when it runs, and up to ~32k if it reads all its reference files. Until then it costs about 123 tokens; SKILL.md has 2,058 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~123
When it runs · the whole SKILL.md, loaded when a task matches
~5.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~32k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from scenario-labs/skills at commit f6f8ab7, republished under its MIT licence (© scenario-labs). 2,058 words, ~5,120 tokens.

Download SKILL.mdSave it as .claude/skills/scenario-unreal-cinematics/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
scenario-unreal-cinematics
description
Use when making a trailer, cutscene, cinematic or short film in Unreal Engine 5.8 with Sequencer: shot lists, master and shot sequences, cameras, lenses, depth of field, camera cuts, spawnables, character animation in shots, per-shot lighting, Movie Render Graph or Movie Render Queue EXR renders, "render darker than the viewport", "first frames pop", "last frame missing", ACES or OCIO to DaVinci Resolve, the 180-degree rule, Sequencer Python, or reviewing a cut.
license
MIT

Cinematics in Unreal Engine 5.8 (Sequencer and Movie Render Graph)

Expert level here means the cut is checked as data before anything is built and a render is judged on its files and frames, not the viewport. The core stance: plan offline, build in one transaction, lock timing against the music before animating, light from approved masters, render per shot through one template graph, hand linear EXRs, an edit and a color note to the grade. If a sibling skill named here is missing from your available skills, ask the user to install it (npx skills add scenario-labs/skills --skill <name>); unattended, proceed from tool schemas and flag the gap.

REQUIRED BACKGROUND: scenario-unreal-expert (channels, review loop, 5.8 traps).

Status (2026-09-24): scripts/ue_cine.py and scripts/cine_render_callbacks.py are not yet run in Unreal; offline tests pass (counts: references/sources.md). In the engine, run tests/code/unreal-cinematics/job_00_probe_cine.py first.

Stance (the expert delta)

  • The master is an edit; shots own the content. Cameras, characters and keys live in shots, per-discipline subsequences (lighting, FX) inside shots, so re-pacing moves sections, never animation (Sir Wade, ywtvn1uncZo [00:07:32]; Glitch, uzTo5vQchkk [00:35:24]). Per-shot things are spawnables, the set is possessable, so the cinematic plays in any level (yOcgYMcxr3Q [00:07:53] [00:13:50]); a possessable animated in one shot snaps back after it; Outliner visibility is not saved, Levels panel visibility is ([00:10:34] [00:02:23]). Duplicating a master shares its shots: "someone tweaks lighting, it changes seven shots" (Epic CAT, S4Iyzbl-oaE [00:41:34]); experiment with a New Take.
  • Structure is templated and scripted, never clicked together. Display rate, start frame, bias, naming and folder template are set once in DefaultEngine.ini under revision control (S4Iyzbl-oaE [00:15:22] [00:21:52]); CAT 5.8 schemas nest and can give each shot its own level (VP 5SJA1FfRPWs [00:19:07] [00:20:44]). Every tool is one ScopedEditorTransaction around a ScopedSlowTask, because "long running Python codes, they look really similar to a frozen engine" (SPI, moQTQzAOFVA [00:16:16]).
  • Lock timing before animating. Board with constant keys, music on its own track, stingers exactly on cuts; "you don't want to spend time working on frames that will never make it into the final film" (Toonen, mAMp6qCt7kc [00:15:04] [00:15:36] [00:04:55]). Retiming must carry intent: keys move with their shot, spanning subsequences are chopped and each half gets its own asset (moQTQzAOFVA [00:14:04] [00:24:19]).
  • Warm-up is three fixes, and end frames are exclusive. Idle CPU simulation: Engine Warm Up Count above 30; temporal history: Render Warm Up; anything moving at frame one: animation and camera cut extended before the start with camera-cut warm-up, which evaluates the lead-in instead of holding frame one (tips doc; Comly/Hoffman, demystifying MRQ). A 0 to 50 range renders 0 to 49.
  • Samples buy motion blur and anti-aliasing, nothing else. Noise goes back to its source (demystifying MRQ; Faucher, fVg5ihB8Wdc [00:09:15]). Temporal only, odd counts with Frame Center, or Blur's 24/48/64 with Frame Close (AAAhD5tEUBs [00:39:32]); AA None above 8 samples; zero console variables until a named shot problem needs one (fVg5ihB8Wdc [00:03:00]).
  • Grade outside from linear EXR, and say how to read it. Tone curve off gives linear sRGB, about one stop darker than the viewport because UE's tone curve is "ACES flavored, but not a true ACES" (Faucher, 2Q3CybANHKE [00:04:31] [00:09:39]). Resolve's ACES Transform: tone curve on, sRGB (Linear) to sRGB Texture; off, Linear sRGB to sRGB; ACEScg (only for a vendor), ACEScg to sRGB ([00:08:30] [00:09:05]). Light and review through the viewport's OCIO Display set to that view ([00:10:28] [00:11:00]).
  • The shot is the render unit. "The smallest unit of distributable work in Unreal Engine is a single camera cut" (MRQ command-line doc): one job per shot, one template graph, per-job variable overrides, never edits to the shared graph. Plain MRQ needs babysitting and a crash loses the shots, so unattended multi-shot renders go through a farm manager (Glitch [00:40:14]).
  • Lighting scales by process. A temp camera light from day one; then one or two signature shots per lighting scenario, locked with the director; then per-shot _LGT subsequences derived from them, graded by distance from their master (Glitch [00:27:18] [00:28:51] [00:29:23] [00:31:32] [00:36:59]).

Establish first

InputChangesDefault when silent
Delivery: graded or directtone curve, format, OCIO, color notegraded: EXR 16-bit half, tone curve off
Production record (rate, start, bias, naming)every sequence, EDLthe project's DefaultEngine.ini; else 24 fps, start 0 (SPI 101, CAT demo 1000: match editorial)
Duration, shots, musiclayout, stingersthe brief; a temp track before boarding
Aspect and filmbacklens, framing16:9 Digital Film [verify mm]; 2.39 crop for scope
Level and what existsbindingsset possessable; cameras, characters, shot lights spawnable; master lighting in the level
Castpre-roll, costexisting Animation Sequences; joints and meshes per character
Motion per shot, shutter timingsamples, pre-rollFrame Center, odd counts
ExposurecontinuityManual, physical camera, ISO compensates aperture changes
Channelbuild, board, renderlive editor (MCP, PythonRemote) for boards; ue_run or the command line for finals

Workflow

import ue_cine as C (skill scripts/, with scenario-unreal-expert's scripts/ on the path). Full code: references/procedures.md.

  1. Scaffold (once per project). Production defaults recorded once (CAT Production Setup or Project Settings) and copied into plan["production"]; folder template, shots in steps of 10; with CAT 5.8, shot schemas holding the _LGT schema, a level per shot when shots need unique set states (P2). Check the MCP SequencerTools toolset first [verify]. GATE: C.check_production(plan) no fail; audit_sequence seq.rate and seq.start.
  2. Plan the cut as data (python3). Shots, sizes, lenses, camera and subject positions, motion, flags, cast (joints, meshes), stingers, lighting scenarios. C.check_plan(plan): length, lenses, framing, 180-degree line, screen direction, jump cuts, DOF, pre-roll, exposure, cast, stingers, lighting groups (P1). GATE: no fail; every warn fixed or answered in the plan.
  3. Build in one transaction (editor). C.build_from_plan(plan): master with Shots and music, a spawnable Cine Camera per shot (lens keyed, Use Field of View for LOD on), camera cut from pre-roll to the exclusive end, pre-rolled performers, <shot>_LGT with the temp light (P3); never overwrites. GATE: C.audit_sequence no fail, bind.override answered; C.empty_level_test lists only set pieces.
  4. Board and lock the cut (latent editor). C.board_generator(..., preroll=True): first, middle, last frame per shot plus each shot's first pre-roll frame read in isolation (GUI: Evaluate Sub Sequences In Isolation); ue_review.image_checks, contact sheet (P4). Retime (C.retime_shot), takes (C.new_take), own tools inside C.editor_tool (P5). GATE: no all-white or all-black frame, the sheet and the cut with music judged, C.ready_to_animate(plan) passes.
  5. Performance and camera polish. Rack focus as keyed Manual Focus Distance (P6), camera moves as base plus offset plus shake layers (P7); Accumulation DOF only on DOF-centric shots. GATE: re-board; keyed focus equals subject distance; no pop at section boundaries.
  6. Lighting (with scenario-unreal-lighting-rendering). Temp light renders unblock everyone; C.lighting_masters(plan), render only those (render_jobs(plan, only=...)), director approval into plan["lighting_approved"]; then per-shot rim and kick lights in _LGT, lit through the viewport OCIO Display (P7b). GATE: C.ready_for_final_lighting(plan); luminance continuity and approval against the masters; stat unit or an Insights trace if a shot is slow.
  7. Draft render and review. The review graph or the 5.8 Basic config; C.review_movie_cmd with the music (P10). GATE: C.check_render_output, C.first_frame_pop, C.cut_flash, then watch it with sound.
  8. Final EXR. Template graph per P8 with the CineWrittenFiles Execute Script (Editor Only); C.audit_render_settings(C.normalize_graph_snapshot(C.graph_snapshot(graph))); C.render_jobs(plan, sequences=C.active_shot_paths(master, plan)), C.render_orchestration, then C.render_generator (executor held globally) or C.mrq_command_line per shot (always -notexturestreaming) (P9). GATE: settings audit pass; C.check_manifest, C.exr_checks per sampled frame; after a crash, re-render C.shots_to_render(...) whole.
  9. Deliver. EXRs per shot, C.edl(plan), review MP4, C.delivery_note(plan, settings) (Resolve interpretation), JSON reports; notes split technical or creative, three creative rounds, then a live session (Glitch [00:32:37] [00:33:40]) (P11).
Show full SKILL.md (811 more words)Show less

Numbers

ItemValueRelative to, source
Hierarchical biasroot 0, +100 per level, equal values blendshots doc
Pre-roll24 to 48 frames on cloth, hair, particles in motiondigest; tips doc
Engine Warm Up, idle clothmore than 30 framestips doc
Temporal samplesFrame Close: 24 base (95% of Blur's shots), 48 fast, 64 very fast; Frame Center: odd (15, 25, 49, 65; Faucher: 15 to 31 covers 95 to 98%)AAAhD5tEUBs [00:39:32] [00:40:05]; fVg5ihB8Wdc [00:06:01] [00:10:58]
AA methodNone above 8 total samplesMRG image quality doc
Warm-up samplingonly the last 5 warm-up frames are sampled5.6 and 5.8 notes
Linear vs viewportabout 1 stop darker2Q3CybANHKE [00:09:39]
Review MP4 video bitratefps x 2 x 1000 kb/s (48,000 at 24 fps)2Q3CybANHKE [00:22:54]
Charactersunder 200 jointsGlitch [00:05:33]
Master lighting10 to 13 per 400-shot episode, 1 to 2 days eachGlitch [00:28:51]

Quality gates

  • Measurable: check_plan, ready_to_animate, ready_for_final_lighting and audit_sequence without fail; audit_render_settings without fail or unanswered warn; frame counts with exclusive ends (check_render_output, check_manifest); EXR half, no NaN or Inf, not black, values above 1.0 in bright shots when linear, metadata present; first_frame_pop and cut_flash false; luminance jumps only where intended.
  • Visual: contact sheets, isolated pre-roll frames, first frames, every cut, DOF edges on hair and occluders, fastest motion blur, lighting against the masters through the grade's OCIO view, the cut with music.

Common mistakes

MistakeWhat it looks likeFix
Duplicating the master to experimenta change leaks into the "backup"New Take (new_take) inside the shot
Characters and cameras possessablebreaks in another mapspawnables; empty_level_test
Animating a set piece as a possessableit snaps back after its shotkey it where needed, or spawnable (bind.override)
Hiding actors with the Outliner eyeback after reopeningLevels panel or a Level Visibility track
Several skeletal meshes, one animation trackparts do not followSet Leader Pose Component (check_characters)
Long Python tool, no progress"frozen" editor killed mid-writeeditor_tool
Animating before timing is lockedwork on frames that get cutboard, stingers on cuts, ready_to_animate
Engine Warm Up for a running charactercloth snaps at frame onepre-roll plus camera-cut warm-up
Expecting the last frame"missing" frame 50 of 0 to 50end is exclusive; count end - start
Raising samples for noisetime up, noise unchangedfix the light or post-process setting
Even samples with Frame Center, mixed temporal and spatialstepping, wasteodd temporal only (or 24 with Frame Close)
Lighting shot by shot, no masterslate creative changesapproved masters first
Lighting in the default viewport, rendering linearlook shifts a stopviewport OCIO Display
Linear EXRs sent with no interpretationdark, odd colors in Resolvedelivery_note
Editing the shared graph per shotevery job changesexposed variables per job
Overnight local queue, or a local executora crash loses the queue; render stopsfarm manager or one process per shot; shots_to_render; start_render
Headless render without -notexturestreamingsoft first framesmrq_command_line

Handoffs

  • Receives from scenario-unreal-lighting-rendering: the lit level (sky, fog, key, unbound PPV, exposure policy, master lighting as a sub-level or data layer), noise fixed at the source, lit masters for approval. From scenario-unreal-animation: Animation Sequences with lengths and rate, characters under 200 joints with Set Leader Pose Component on multi-mesh Blueprints, cloth or physics flags. From scenario-unreal-vfx: Niagara systems with user parameters and warm-up needs. From scenario-unreal-world-building: the map and its set pieces.
  • Delivers to the editor and colorist: EXRs per shot ({sequence_name}/{sequence_name}.####.exr, linear, half, metadata), <prod>.edl, the delivery note, the review MP4, contact sheets, JSON reports, the master. To scenario-unreal-lighting-rendering: shots failing continuity or noise, with frames. Farm commands to scenario-unreal-pipeline-automation; slow shots to scenario-unreal-performance.

UE 5.8 notes

  • MRG is Production Ready, new features graph-only, the queue opens in a Basic config; new: Light Modifier, layer warm-ups, DWAA/DWAB EXR, Accumulation DOF (experimental plugin) (5.8 notes; VP [00:33:35]).
  • In MRG, Game Overrides act only while connected; tone curve on the renderer node, OCIO on the output node; the Execute Script node needs Editor Only mode for Python (transition doc; 5.8 notes).
  • Spawnables are custom bindings; create them with LevelSequenceEditorSubsystem.add_spawnable_from_class; no add_master_track; time functions take MovieSceneTimeUnit (seq-py doc; version deltas).
  • Playback honors the selection range; Sensor Aspect Ratio is not animatable; Take Recorder and VCam accept spawnables; Sandboxes for experiments.
  • OpenColorIO 2.5.1 with ACES 2.0: view names may differ from "ACES 1.0 SDR Video" [verify].
  • Mac: the MRG H.264 node is Windows only (encode with ffmpeg); ProRes on Mac is conflicting [verify]; path tracing needs macOS 26.4+.

References

  • references/procedures.md: P0 to P11, full code, plan fields, the template graph spec (P8). Load before writing Sequencer or render code.
  • references/expert-notes.md: judgment per expert, timestamps, deciding conditions.
  • references/critique.md: the rubric, mapped to code checks.
  • references/gui-paths.md: menus and settings for the same procedures.
  • references/sources.md: sources, credentials, URLs, timestamps; revision history.
  • scripts/ue_cine.py (toolkit; its docstring lists every call) and scripts/cine_render_callbacks.py (the Execute Script class).

© scenario-labs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (scripts, references) in skills/game-engines/unreal/scenario-unreal-cinematics of scenario-labs/skills.

  • SKILL.md
  • references/critique.md
  • references/expert-notes.md
  • references/gui-paths.md
  • references/procedures.md
  • references/sources.md
  • scripts/cine_render_callbacks.py
  • scripts/ue_cine.py

Open the folder on GitHubat commit f6f8ab7

Compare with similar skills

Scenario Unreal Cinematics next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Scenario Unreal Cinematics compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Scenario Unreal Cinematics this skillscenario-labs/skills946—~5.1kAutomated safety check: PassMIT
Unreal BridgeTornLux/UnrealBridge306—~8.4kAutomated safety check: NotesMIT
Unreal Animation Bone Editorkevinpbuckley/VibeUE730—~1.3kAutomated safety check: PassMIT
Unreal Enhanced Input Setupkevinpbuckley/VibeUE730—~2.4kAutomated safety check: PassMIT
Unreal Gameplay Tagskevinpbuckley/VibeUE730—~2.3kAutomated safety check: PassMIT
Vibeuekevinpbuckley/VibeUE730—~5.2kAutomated safety check: PassMIT

Similar skills

  • Unreal Bridge

    TornLux/UnrealBridge

    Execute Python scripts inside a running Unreal Engine 5.3+ editor via TCP bridge.

    306 GitHub stars~8.4k tokensUpdated 10 days ago
    Game DevelopmentAuto-check: notes
  • Unreal Animation Bone Editor

    kevinpbuckley/VibeUE

    Previews, validates and bakes bone-rotation edits on Unreal Engine AnimSequences, enforcing a coordinate space and a constraint-checked preview-validate-bake loop.

    730 GitHub stars~1.3k tokensUpdated 4 days ago
    Game DevelopmentAuto-check passed
  • Unreal Enhanced Input Setup

    kevinpbuckley/VibeUE

    Creates and wires Unreal Engine Enhanced Input assets through VibeUE's InputService: Input Actions, Mapping Contexts, key bindings, triggers and modifiers.

    730 GitHub stars~2.4k tokensUpdated 4 days ago
    Game DevelopmentAuto-check passed
  • Unreal Gameplay Tags

    kevinpbuckley/VibeUE

    Registers and queries Unreal Engine Gameplay Tags from the editor through VibeUE, including bulk registration and hierarchy lookups, with no restart needed.

    730 GitHub stars~2.3k tokensUpdated 4 days ago
    Game DevelopmentAuto-check passed
  • Vibeue

    kevinpbuckley/VibeUE

    Unreal Engine 5 development using the VibeUE Python API. An agent skill from kevinpbuckley/VibeUE.

    730 GitHub stars~5.2k tokensUpdated 4 days ago
    Game DevelopmentAuto-check passed
  • Unreal Animation Montage

    kevinpbuckley/VibeUE

    Creates and edits Unreal Engine Animation Montages through AnimMontageService: sections, slots, segments, branching points, notifies and blend settings.

    730 GitHub stars~3.6k tokensUpdated 4 days ago
    Game DevelopmentAuto-check passed

More from scenario-labs/skills

All 146 skills in this repo
  • Scenario Blender Grease Pencil

    scenario-labs/skills

    A skill your agent uses when drawing or animating with Grease Pencil in Blender 5.x from Python: 2D or 2.5D illustration, frame-by-frame animation, a cutout or part-based 2D character, strokes with…

    946 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check passed
  • Scenario Blender Hair

    scenario-labs/skills

    A skill your agent uses when grooming hair or fur in Blender with hair curves, such as a character hairstyle, animal fur, procedural fur in geometry nodes, or hair cards and mesh hair for games.

    946 GitHub stars~4.7k tokensUpdated yesterday
    Auto-check passed
  • A skill your agent uses when lighting, rendering or compositing in Blender: light a character, product or hero shot, interior at dusk or night, three-point or motivated lighting, sun and sky, HDRI…

    946 GitHub stars~5k tokensUpdated yesterday
    Auto-check passed
  • Scenario Chatgpt Pet Create

    scenario-labs/skills

    A skill your agent uses when creating a ChatGPT pet or Codex pet with Scenario: hatching an animated companion from a text idea, a character, mascot or brand cue, or reference photos and art; making…

    946 GitHub stars~3.6k tokensUpdated yesterday
    Auto-check passed
  • Scenario Godot Animation

    scenario-labs/skills

    A skill your agent uses when animating characters or scenes in Godot 4.7: AnimationPlayer clips and RESET, AnimationTree state machines and blend spaces built in code, Mixamo or glTF import, loop…

    946 GitHub stars~4.7k tokensUpdated yesterday
    Auto-check passed
  • Scenario Godot Audio

    scenario-labs/skills

    A skill your agent uses when adding or fixing sound in Godot 4.7: audio buses and effects, volume sliders, 'too many sounds', combat audio with hundreds of enemies, sounds clipping or distorting, 3D…

    946 GitHub stars~4.7k tokensUpdated yesterday
    Auto-check passed

Questions about Scenario Unreal Cinematics

What does Scenario Unreal Cinematics do?

A skill your agent uses when making a trailer, cutscene, cinematic or short film in Unreal Engine 5.8 with Sequencer: shot lists, master and shot sequences, cameras, lenses, depth of field, camera…. Scenario Unreal Cinematics is an agent skill from scenario-labs/skills.8 with Sequencer: shot lists, master and shot sequences, cameras, lenses, depth of field, camera cuts, spawnables, character animation in shots, per-shot lighting, Movie Render Graph or Movie Render Queue EXR renders, "render darker than the viewport", "first frames pop", "last frame missing", ACES or OCIO to DaVinci Resolve, the 180-degree rule, Sequencer Python, or reviewing a cut.

When should I use Scenario Unreal Cinematics?

Scenario Unreal Cinematics fits situations like: making a trailer; short film in Unreal Engine 5.8 with Sequencer: shot lists; master and shot sequences; character animation in shots.

How do I install Scenario Unreal Cinematics in Claude Code?

Run `npx skills add scenario-labs/skills --skill scenario-unreal-cinematics -a claude-code`. Or copy the skill folder (skills/game-engines/unreal/scenario-unreal-cinematics in scenario-labs/skills) into .claude/skills/scenario-unreal-cinematics in your project. Claude Code loads it when a task matches its description.

How do I install Scenario Unreal Cinematics in Codex?

Run `npx skills add scenario-labs/skills --skill scenario-unreal-cinematics -a codex`. Or copy the skill folder (skills/game-engines/unreal/scenario-unreal-cinematics in scenario-labs/skills) into .agents/skills/scenario-unreal-cinematics in your project. Codex loads it when a task matches its description.

Can I use Scenario Unreal Cinematics in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add scenario-labs/skills --skill scenario-unreal-cinematics -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/scenario-unreal-cinematics, .gemini/skills/scenario-unreal-cinematics, .github/skills/scenario-unreal-cinematics and .opencode/skills/scenario-unreal-cinematics in your project.

What does Scenario Unreal Cinematics need to run?

Going by SKILL.md and its folder, Scenario Unreal Cinematics needs Python for the scripts in its folder and the command-line tools its instructions call (npx). Our summary lists: Python 3; Node.js.

Does Scenario Unreal Cinematics access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Scenario Unreal Cinematics safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Scenario Unreal Cinematics use?

Scenario Unreal Cinematics is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Scenario Unreal Cinematics use?

About 5.1k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 27k tokens, read only when the agent opens those files.

What are the alternatives to Scenario Unreal Cinematics?

Skills that share tags, products or a category with Scenario Unreal Cinematics: Unreal Bridge (TornLux/UnrealBridge, 306 stars), Unreal Animation Bone Editor (kevinpbuckley/VibeUE, 730 stars), Unreal Enhanced Input Setup (kevinpbuckley/VibeUE, 730 stars) and Unreal Gameplay Tags (kevinpbuckley/VibeUE, 730 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Scenario Unreal Cinematics?

scenario-labs (a GitHub organization) maintains it in scenario-labs/skills, which has 946 GitHub stars. The repository holds 146 skills in this directory. The repository was last updated on October 10, 2026.

Source: scenario-labs/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.