Agent skill

Scenario Unreal Vfx

by scenario-labs in scenario-labs/skills

A skill your agent uses when a UE5 task involves Niagara or Chaos destruction: a Niagara fireball, projectile trail, impact explosion, muzzle flash, spell, smoke, sparks, debris, Niagara fluids or…

MITAuto-check passedGame Development

Install Scenario Unreal Vfx

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

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

GitHub CLI
$ gh skill install scenario-labs/skills scenario-unreal-vfx --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-vfx .claude/skills/scenario-unreal-vfx && 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-vfx
GitHub stars
946
Token cost
~5.1k tokens
SKILL.md length
2,111 words
Files
7 (incl. scripts, references)
Skills in repo
146
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when a UE5 task involves Niagara or Chaos destruction: a Niagara fireball, projectile trail, impact explosion, muzzle flash, spell, smoke, sparks, debris, Niagara fluids or…

  • Works in 11 steps: Probe once per engine.… → Classify elements, group them into… → Timing plan before building. Write the… → …
  • A UE5 task involves Niagara
  • SKILL.md covers Stance (the expert delta), Establish first, Workflow and Numbers, plus 5 more sections
  • Runs Python scripts from its folder; calls npx and python3

What it does

Scenario Unreal Vfx is an agent skill from scenario-labs/skills. Use when a UE5 task involves Niagara or Chaos destruction: a Niagara fireball, projectile trail, impact explosion, muzzle flash, spell, smoke, sparks, debris, Niagara fluids or flipbooks; "Niagara is too expensive", stat NiagaraOverview, Effect Types, pooling, Data Channels, lightweight emitters, VFX scalability; judging an effect's readability, value, color, timing, white blowout or strobing; or a wall that shatters, geometry collection fracture, Dataflow, damage thresholds, floating chunks, debris cost, Chaos…

Its SKILL.md is about 5.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 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. 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

  • A UE5 task involves Niagara
  • Chaos destruction: a Niagara fireball
  • Projectile trail
  • Impact explosion

Example prompts

  • “Niagara is too expensive”
  • “/scenario-unreal-vfx”

Requirements

  • Python 3
  • Node.js

Workflow steps

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

  1. Probe once per engine. job_00_vfx_probe.py (headless). GATE: probe.json answers the [verify] items.
  2. Classify elements, group them into systems. classify_element per element, then system_plan: one Effect Type per system (its most critical…
  3. Timing plan before building. Write the spawn schedule (wind-up from the cast animation, build-up ending at the hit, flash on the hit…
  4. Template and contract. duplicate_template, user_parameters, contract_verdict; a missing control becomes one GUI request. Curves in that…
  5. Look: materials and textures. Master material and instances from scenario-unreal-materials (erosion, gradient-map LUT, depth fade); reuse…
  6. System properties and scalability. set_system_properties: effect_type, max_pool_size = the type's system cap, prime 0 for mid-play loads…
  7. Wire to gameplay. scenario-unreal-gameplay spawns with the pooling method, sets User parameters from gameplay data, spawns the wind-up…
  8. Destructible asset. Watertight, non-intersecting source (mesh_watertight_check); fixed seed; pattern by material (concrete noise and…
  9. Review loop. Textured review level, Manual exposure, the gameplay camera; live_capture_series.py or capture_ages with clean plates…
  10. Measure. Fixed worst fight at the target core count: stat unit, stat NiagaraOverview, Debug HUD, Insights with -statnamedevents (Niagara…
  11. Deliver the budget sheet to scenario-unreal-performance.

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 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • npx
    • python3

    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 Vfx loads about 5.1k tokens when it runs, and up to ~51k if it reads all its reference files. Until then it costs about 138 tokens; SKILL.md has 2,111 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~138
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
~51k

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,111 words, ~5,143 tokens.

Download SKILL.mdSave it as .claude/skills/scenario-unreal-vfx/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
scenario-unreal-vfx
description
Use when a UE5 task involves Niagara or Chaos destruction: a Niagara fireball, projectile trail, impact explosion, muzzle flash, spell, smoke, sparks, debris, Niagara fluids or flipbooks; "Niagara is too expensive", stat NiagaraOverview, Effect Types, pooling, Data Channels, lightweight emitters, VFX scalability; judging an effect's readability, value, color, timing, white blowout or strobing; or a wall that shatters, geometry collection fracture, Dataflow, damage thresholds, floating chunks, debris cost, Chaos Visual Debugger.
license
MIT

Unreal VFX (Niagara, Chaos destruction, VFX critique)

Expert level means an effect that tells the player the truth (where it hurts, when it is over), costs what its gameplay class allows across the whole world, and is proven by per-thread numbers on the target core count plus captures scored against a written rubric. Python cannot author Niagara emitters or modules (5.8 API): the agent works through templates with a User parameter contract, Material Instances, Effect Types and Dataflow recipes, and escalates the few graph edits as precise GUI requests. 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): Unreal is not installed. Offline checks pass (python3 tests/code/unreal-vfx/run_all.py --offline); every in-editor snippet is not yet run in Unreal; job_00_vfx_probe.py answers the [verify] names.

Stance (the expert delta)

  • Gameplay truth first. The boldest edge sits on the collision boundary (missile head, AoE rim) and reads the gameplay number (User.Radius = damage radius), never a hand-matched constant; lingering says "still dangerous" (Keyser #1 [00:09:44], [00:15:21]).
  • Contrast is a screen budget. Near-white core, never pure white; saturation in the fringe; dark saturated halo; contrast highest at the head; a weak projectile gets a hotter core and dark wisps, not a brighter trail (Keyser #3 [00:08:13], [00:12:03]; #4 [00:19:55]). Unexpected white is usually stacked additive duplicates: count spawns before touching color, then back the additive core with an alpha-blended saturated layer (Shishido [00:17:42]-[00:18:14]).
  • Timing is a story. Anticipation rides the character's cast animation (no window: put the interest in the falloff); build-up stops spawning exactly at the hit; the flash peaks on the hit frame ("intensity is not size"); consequences follow causes (flash, then debris and sparks, then smoke); dissipation is shorter than build-up and ends inside the gameplay window. A fast round head strobes: stretch it along velocity and bake motion blur into its texture (Keyser #5 [00:08:13]-[00:09:54], [00:14:34], [00:18:07]; #2 [00:03:31]; Shishido [00:30:00], [00:37:02]).
  • Optimize the world, not the effect. An Effect Type on every system first: Lyra went from 227 to 103 active systems, RT 5.07 to 1.51 ms, same look (Kiraly [00:20:48]). The Effect Type is set per system, never per emitter; secondary emitters get Scalability Mode Self. Read GT, GT Concurrent and RT separately at the target core count [00:05:15], then pick a lever that saves that thread: distance culling stops ticking, not rendering, and the scalability manager pays for the check; cull proxies save the tick, not the RT [00:16:57], [00:18:02]; every GPU system pays an RT dispatch even unseen [00:05:47]. FX budgets only on non-critical types, with fx.Budget.AdjustedUsageDecayRate against oscillation [00:36:50]-[00:37:21].
  • Spawn architecture by class and rate (Kiraly's table [00:45:57]): pool moderate one-shots (Manual Release means Release to Pool), a Data Channel listener for spam, stateless emitters with system state off for simple bursts (footsteps GT 1,387 to 271 us [00:39:24]); NDC and stateless are exclusive; small counts stay on CPU.
  • Destruction cost is active bodies and contacts. Fix in order: rendering (Nanite on the GC, root proxy with the ISM renderer), body count and lifetime (clusters, Remove on Break with random timers and Cluster Crumbling, a per-platform removal multiplier, Tiny Geo), collision (one-way debris, one convex per cluster, boxes under 0.3 relative size), throttles last (Caillaud wPgd1J1Tf70 [00:03:47]-[00:16:18]; Xiao Yue zFiHDRREv7E [00:29:27]).
  • Weapons break walls with strain, not fields. Apply External Strain plus Apply Breaking Linear Velocity scaled by projectile speed, no strain falloff; fields are "heavy and slow" (Van Allen [00:29:29]). Pick one damage model: Material Strength and Connectivity (tune tensile strength on the physical material) or per-level thresholds (tune the array); size-specific is a flag, not a model (Xiao Yue [00:19:54]-[00:20:27]). Heft comes from friction (combine Max) and low restitution; stone density is 2 g/cm3, 2000 is a unit error (Van Allen [00:26:11]).
  • Recipes, not clicks. Templates with exposed parameters and Dataflow graphs with per-asset variables survive art changes and are what an agent reaches reliably (Caillaud t_jyTILDYo8 [00:02:46]).

Establish first

InputWhy it changes the planDefault when silent
Platform, frame rate, min-spec coresper-thread budgets, quality tablesPC 60 fps; cores from scenario-unreal-performance, 4 if unknown (Kiraly)
Gameplay numbers (scenario-unreal-gameplay)radius, speed, damage window, fire rate, max simultaneous, cast animation timingask; never guess a radius
Camera and environmentread at gameplay distance over the real ground colorsthe game's camera and level
Style pillars, importance tierbrightness budget: idle, basic, defensive, damaging, game changer, ultimate (Keyser #1 [00:13:08])three pillars from the art lead
Crowd and destruction scopecopies on screen; walls per level, must-break objects, low-end platformsworst realistic fight; real time, Nanite on
Budgetsno source gives per-effect ms[added] all Niagara at or under about 2 ms GT + GT Concurrent and 1.5 ms RT at min spec; confirm with scenario-unreal-performance

Workflow

  1. Probe once per engine. job_00_vfx_probe.py (headless). GATE: probe.json answers the [verify] items.

  2. Classify elements, group them into systems. classify_element per element, then system_plan: one Effect Type per system (its most critical element); the rest get Scalability Mode Self, or their own system when spammy or on GPU.

    System (examples)Effect TypeCritical emittersSecondary (Scalability Mode Self)
    Projectile, beam, tracerNET_OneShotCriticalheadtrail, wisps, embers
    Impact, hit, muzzle flashNET_OneShotCriticalflash, damage ringsmoke, sparks (split if spammy or GPU)
    Debris or impact listener (NDC)NET_OneShot, budget only with decay dampingnoneall
    AoE, status, pickupNET_PersistentCriticalriminterior flavor
    Ambient dust, leaves, rainNET_Ambientnoneall

    GATE: system_plan has no error.

  3. Timing plan before building. Write the spawn schedule (wind-up from the cast animation, build-up ending at the hit, flash on the hit, debris and sparks, smoke, window end) and run spawn_schedule_verdict; strobe_risk(speed, head length) gives the stretch a fast head needs. GATE: no error; stretch in the template spec.

  4. Template and contract. duplicate_template, user_parameters, contract_verdict; a missing control becomes one GUI request. Curves in that request pass fade_curve_verdict (opacity fades from mid-life, never shrink-only) and flipbook_playback_verdict (fast then slow). GATE: contract ok.

  5. Look: materials and textures. Master material and instances from scenario-unreal-materials (erosion, gradient-map LUT, depth fade); reuse textures first (Trümpler [00:16:33]), generate glows, LUTs and noise in Python. Import masks with sRGB off, TEXTUREGROUP_Effects, big sources capped by Maximum Texture Size; baked flipbooks are premultiplied, so the material must divide RGB by A (premultiplied_check). Smoke and fire: baked flipbooks by default; Fluids are Beta. GATE: audit_vfx_textures, flipbook_check clean.

  6. System properties and scalability. set_system_properties: effect_type, max_pool_size = the type's system cap, prime 0 for mid-play loads, warmup 0, current-frame data off for static effects; world-space trails need fixed bounds of speed x lifetime (fixed_bounds_check). Effect Types from EFFECT_TYPE_PRESETS (create_effect_type [verify] or GUI once). GATE: no NO_EFFECT_TYPE in audit_niagara; caps_verdict, budget_verdict clean.

  7. Wire to gameplay. scenario-unreal-gameplay spawns with the pooling method, sets User parameters from gameplay data, spawns the wind-up from the cast animation, writes Data Channel payloads, applies strain on hit (strain_plan; collision plus strain for must-break objects). On hit, deactivate the trail and let its particles finish [added]. GATE: a PIE hit spawns from the pool (FX Outliner InUse / FreeInPool).

  8. Destructible asset. Watertight, non-intersecting source (mesh_watertight_check); fixed seed; pattern by material (concrete noise and grout, wood shrink-fracture-stretch, glass slices or a crack material); two or three levels, anchored; Proximity graph with an area threshold; one damage model; one convex per cluster; interior material with a distance-to-surface bake (Caillaud t_jy [00:29:14]); Remove on Break ranges plus Cluster Crumbling; removal multiplier in the low-end device profile; disable settled debris that never wakes (Xiao Yue [00:28:45]). VFX on breaks needs Chaos data generation in Project Settings plus break notification on the component (enable_break_events, Xiao Yue [00:08:42]); switch only broken bones to a debris profile. Then harden_gc; piece count in a gym at 10, 50, 100 (Caillaud t_jy [00:35:12]). GATE: gc_recipe_verdict, gc_verdict, physmat_check clean.

  9. Review loop. Textured review level, Manual exposure, the gameplay camera; live_capture_series.py or capture_ages with clean plates; score_captures.py (a blank frame voids the series); LOOK at the color, grayscale and squint sheets; repeat in PIE ("the viewport lies", Shishido [00:05:05]), over green and brown ground for the color-blind check, in a crowd grid and at sg.EffectsQuality 0 to 3. On white-out run duplicate_spawn_check on Debugger counts first. One change per pass. GATE: no rubric fail; judgment rows scored (references/critique.md).

  10. Measure. Fixed worst fight at the target core count: stat unit, stat NiagaraOverview, Debug HUD, Insights with -statnamedevents (Niagara is invisible without it, Kiraly [00:10:52]); init_for_performance_baseline(); lever_check before each change; budget_oscillation when budgets are on. Destruction: frame series around the break, CVD, t.OverrideFPS 60 [verify]. GATE: niagara_overview_verdict, before_after, destruction_run_verdict within budget, visual parity.

  11. Deliver the budget sheet to scenario-unreal-performance.

Show full SKILL.md (656 more words)Show less

Numbers

ValueRelative toSource
NET_OneShot: 15 per system, about 30 per type, Spawn Only, Kill and Clear, instant cull 0.0fire-and-forget, not criticalKiraly [00:22:26]
NET_PickupPersistent: 5 (sight lines), Continuous, Asleep, cull delay 1.0 spersistent criticalKiraly [00:24:03]
Max Pool Size 32, Prime 0 (defaults); type cap = pool sizeper systemKiraly [00:32:18], [00:33:22]
Flipbook 8 x 8 on 1024 = 128 px tiles, end frame 63, bake at 30 fpsbakerFlipbook Baker doc
Thresholds 5000 / 500 / 50; strain 50000, radius 100, velocity 500quickstart wallChaos docs
Boxes below 0.3 relative size; 4,000 fragments in 4 levels, about 200 bodies hitleaf proxies; clusteringXiao Yue [00:25:51], [00:22:32]
Remove on sleep 3 s; removal 5 to 10 s, then a per-platform multiplierdebrisCaillaud [00:10:43], [00:11:24]

Quality gates

  • Measurable: audits (audit_niagara, audit_gc, audit_vfx_textures, caps_verdict, system_plan, gc_recipe_verdict); per-thread stats at the target core count, averages and spikes; break spike and recovery; capture rubric (footprint vs radius, value bands, blowout, saturation under values, 60 / 30 / 10 with the accent at the focal point, size classes held over time, head contrast, color-blind contrast, intensity curve, schedule, strobing); image_checks rejects blank frames.
  • Visual: grayscale read at gameplay distance; popcorning; story beats; crowd read; no pops across quality levels; the break reads as the material with thick interiors, no floating chunks, heavy debris, removal hidden by dust.

Common mistakes

MistakeWhat it looks likeFix
Hand-matched radiusring larger than the damage zoneUser.Radius from gameplay
White blowoutflat white blobcount duplicates, then an alpha-blended saturated layer behind the additive core
Round head at speedstrobing dotsstretch along velocity, motion blur in the texture
Build-up after the hit; smoke before the flashmuddy payoffspawn schedule: stop at the hit, causes first
Shrink-only fadepopcorning cardsopacity fade from mid-life, matched layer colors
Effect Type per emitterembers get the uncullable typeone type per system, Scalability Mode Self
Distance culling to cut RTRT unchangedlever_check: caps, CPU sims, stateless
Budget without decaycull, respawn, culldecay rate, non-critical types only
Fixed bounds smaller than the trailtrail vanishes on screenfixed_bounds_check
Destroying the projectile on impacttrail pops offdeactivate, let particles finish
Sleep to hold a wallwakes on a bumpanchor or kinematic bones
Default connection graphfloating chunks, corner hingesProximity or Bounds Overlap Filtered
MSC with a tuned threshold arraytuning does nothingtensile strength on the physical material
Field or strain falloff per bulletphysics spikestrain plus breaking velocity, no falloff
Debris profile on the whole GCplayer walks through the intact wallswitch broken bones on the break event
Sleeping debris that never wakessolver costdisable
gc.removal_duration = ...refused (read-only attribute)set_editor_property

Handoffs

  • Receives from scenario-unreal-materials: particle master material, instances, texture settings; from scenario-unreal-gameplay: numbers, cast animation timing, pooled spawns, NDC writes, strain calls; from scenario-unreal-world-building: destructible placements and counts.
  • Delivers to scenario-unreal-performance: a budget sheet (system, Effect Type, caps, pool, sim target, per-thread cost, core count, quality; GCs with pieces, peak active bodies, break spike, recovery) plus the repeatable scenario; to scenario-unreal-cinematics: Chaos caches, Cinematic scalability; to scenario-unreal-lighting-rendering: particle lights, Heterogeneous Volumes. Cloth belongs to scenario-unreal-animation.

UE 5.8 notes

  • Data Channels Production Ready since 5.5 (the GDC 2025 talk still says experimental); lightweight emitters Beta since 5.5, compile step dropped in 5.7; Niagara Fluids Beta; "Empty" template is "Minimal".
  • r.HeterogeneousVolumes.Allow (5.8); Niagara Editor Preview Actor (5.7).
  • Chaos: default Dataflow template at GC creation, runtime Dataflow evaluation (5.8); destruction throttles in Project Settings (5.6).
  • GC Python: root_proxy_data, size_specific_data, set_dataflow_asset; per-bone data (anchors, Remove on Break, one-way levels) is not on the class.

References

© 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 6 other files (scripts, references) in skills/game-engines/unreal/scenario-unreal-vfx of scenario-labs/skills.

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

Open the folder on GitHubat commit f6f8ab7

Compare with similar skills

Scenario Unreal Vfx 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 Vfx compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Scenario Unreal Vfx this skillscenario-labs/skills946—~5.1kAutomated safety check: PassMIT
Unreal BridgeTornLux/UnrealBridge306—~8.4kAutomated safety check: NotesMIT
Unreal Blueprint Authoringflopperam/unreal-engine-mcp1.1k—~1.6kAutomated safety check: PassNone
UMG Material MCPwinyunq/UnrealMotionGraphicsMCP210—~913Automated safety check: PassMIT
Unreal Animation Bone Editorkevinpbuckley/VibeUE730—~1.3kAutomated safety check: PassMIT
Unreal Engine MCPEpicGames/unreal-engine-skills-for-claude-code-plugin338—~1.8kAutomated 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 Blueprint Authoring

    flopperam/unreal-engine-mcp

    Walks an agent through creating and editing Unreal Engine Blueprints with the Flopperam MCP's bp_* tools, from inspection to commit and verification.

    1.1k GitHub stars~1.6k tokensUpdated 3 mo ago
    Game DevelopmentAuto-check passed
  • UMG Material MCP

    winyunq/UnrealMotionGraphicsMCP

    Creates, edits and compiles Unreal Engine 5.8 material assets as one HLSL Custom node through the UMG MCP bridge, instead of editing .uasset files directly.

    210 GitHub stars~913 tokensUpdated 2 mo ago
    Game DevelopmentAuto-check passed
  • 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 3 days ago
    Game DevelopmentAuto-check passed
  • Unreal Engine MCP

    EpicGames/unreal-engine-skills-for-claude-code-plugin

    Drives a live Unreal Editor through the unreal-mcp server: spawn actors, edit Blueprints, materials and sequences, change properties and trigger Live Coding.

    338 GitHub stars~1.8k tokensUpdated 24 days ago
    Game DevelopmentAuto-check passed
  • Unreal Scene Building

    flopperam/unreal-engine-mcp

    Guides scene and world building in Unreal Engine through the Flopperam MCP: placing actors, sculpting landscapes, scattering foliage, editing materials and verifying the level.

    1.1k GitHub stars~1.4k tokensUpdated 3 mo 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

Works with

Questions about Scenario Unreal Vfx

What does Scenario Unreal Vfx do?

A skill your agent uses when a UE5 task involves Niagara or Chaos destruction: a Niagara fireball, projectile trail, impact explosion, muzzle flash, spell, smoke, sparks, debris, Niagara fluids or…. Scenario Unreal Vfx is an agent skill from scenario-labs/skills.

When should I use Scenario Unreal Vfx?

Scenario Unreal Vfx fits situations like: A UE5 task involves Niagara; chaos destruction: a Niagara fireball; projectile trail; impact explosion.

How do I install Scenario Unreal Vfx in Claude Code?

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

How do I install Scenario Unreal Vfx in Codex?

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

Can I use Scenario Unreal Vfx 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-vfx -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-vfx, .gemini/skills/scenario-unreal-vfx, .github/skills/scenario-unreal-vfx and .opencode/skills/scenario-unreal-vfx in your project.

What does Scenario Unreal Vfx need to run?

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

Does Scenario Unreal Vfx 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 Vfx 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 Vfx use?

Scenario Unreal Vfx 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 Vfx use?

About 5.1k tokens (SKILL.md is roughly 21k 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 46k tokens, read only when the agent opens those files.

What are the alternatives to Scenario Unreal Vfx?

Skills that share tags, products or a category with Scenario Unreal Vfx: Unreal Bridge (TornLux/UnrealBridge, 306 stars), Unreal Blueprint Authoring (flopperam/unreal-engine-mcp, 1.1k stars), UMG Material MCP (winyunq/UnrealMotionGraphicsMCP, 210 stars) and Unreal Animation Bone Editor (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 Vfx?

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.