Agent skill

Scenario Maya Fx

by scenario-labs in scenario-labs/skills

A skill your agent uses when a Maya task involves simulation or procedural effects: nCloth or Nucleus (a cape, skirt, flag or garment on an animated character, cloth through the body, jittery or…

MITAuto-check passedGame Development

Install Scenario Maya Fx

skills CLI
$ npx skills add scenario-labs/skills --skill scenario-maya-fx -a claude-code

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

GitHub CLI
$ gh skill install scenario-labs/skills scenario-maya-fx --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/dcc/maya/scenario-maya-fx .claude/skills/scenario-maya-fx && 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-maya-fx
GitHub stars
946
Token cost
~5.3k tokens
SKILL.md length
2,057 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 Maya task involves simulation or procedural effects: nCloth or Nucleus (a cape, skirt, flag or garment on an animated character, cloth through the body, jittery or…

  • Works in 8 steps: Scale and inputs.… → Pick the system (options keyed to the… → Prepare cloth inputs. Topology gate… → …
  • A Maya task involves simulation
  • 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 Maya Fx is an agent skill from scenario-labs/skills. Use when a Maya task involves simulation or procedural effects: nCloth or Nucleus (a cape, skirt, flag or garment on an animated character, cloth through the body, jittery or stretchy cloth), nParticles, Bifrost graphs (Aero smoke, dust puff, mist, fire, liquids, MPM cloth, snow, sand, "Bifrost smoke"), MASH scattering or motion graphics, sim caches (nCache, Alembic, OpenVDB, filecache, USD) or FX delivered to lighting or a game engine (flipbook sprites).

Its SKILL.md is about 5.3k 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, Database migrations and Motion graphics. 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 Maya task involves simulation
  • Procedural effects: nCloth
  • Nucleus (a cape
  • Garment on an animated character

Example prompts

  • “Bifrost smoke”
  • “/scenario-maya-fx”

Requirements

  • Python 3
  • Node.js

Workflow steps

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

  1. Scale and inputs. mx_fx.scale_report(meshes, expected_size_m=...); if the model is not real size, fix the asset (Julan [00:02:02]). Record…
  2. Pick the system (options keyed to the brief)
  3. Prepare cloth inputs. Topology gate mx_fx.cloth_topology_verdict(mx_audit.audit(garment), expected_border_loops=1): evenly spaced quads…
  4. Build.
  5. First pass cheap, then cache. Low resolution (Aero detail 0.1, cloth first pass), frames evaluated in order from the start frame…
  6. Measure and look. rep = mx_fx.sim_report(cloth_out, body_SIM, start, end, action_start=..., thickness=...), rep["convergence"] =…
  7. Triage in this order (never stiffen first): scale; start state (pre-roll, Push Out, Crossover Push with Trapped Check); substeps with…
  8. Final cache and deliver. Final pass settings, nCache from the nucleus start (ncache_verdict: mcc stops at 2 GB, use mcx; positions only…

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 Maya Fx loads about 5.3k tokens when it runs, and up to ~34k if it reads all its reference files. Until then it costs about 119 tokens; SKILL.md has 2,057 words of instructions outside code blocks.

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

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,057 words, ~5,273 tokens.

Download SKILL.mdSave it as .claude/skills/scenario-maya-fx/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
scenario-maya-fx
description
Use when a Maya task involves simulation or procedural effects: nCloth or Nucleus (a cape, skirt, flag or garment on an animated character, cloth through the body, jittery or stretchy cloth), nParticles, Bifrost graphs (Aero smoke, dust puff, mist, fire, liquids, MPM cloth, snow, sand, "Bifrost smoke"), MASH scattering or motion graphics, sim caches (nCache, Alembic, OpenVDB, file_cache, USD) or FX delivered to lighting or a game engine (flipbook sprites).
license
MIT

Maya FX (Nucleus, Bifrost, MASH, caches)

An expert FX TD fixes scale and inputs before touching a knob, changes few settings one at a time, never judges a live solve, and proves the result on the cache in numbers (penetration, stretch, pops, convergence) and in renders from the shot camera. 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-maya-expert (execution channel, review loop, 2027 version traps).

Status (2026-09-24): Maya 2027 is not installed. The pure-Python layer of scripts/mx_fx.py passed offline (tests/code/maya-fx/test_fx_offline.py); every Maya call is not yet run in Maya; names marked [verify] are answered by job_00_fx_probe.py (python3 tests/code/maya-fx/run_all.py).

Stance (the expert delta)

  • Scale before anything. Nucleus and Bifrost compute in meters whatever Maya's unit: Space Scale and scene_units_in_meters 0.01 in a cm scene, or a 182 cm character is 182 m to the solver (2027 Help; SARKAMARI [00:29:22]; Stamatelos [00:30:21]). MPM detail_size is in meters, so a unit change silently changes resolution (Gast [00:07:29]).
  • Never simulate the production mesh. Duplicate the skinned body and garment, drive the duplicates with a blend shape at weight 1, hide the originals (SARKAMARI [00:10:04]).
  • Give the solver a clean start. Hold 25 frames, blend 25 frames into the first pose, action at 0, Nucleus start -50 (SARKAMARI [00:05:26]); Julan: A-pose at 0, walk by 24.
  • Substeps before stiffness. Collision iterations below the substep count do nothing; high stretch resistance at low substeps cannot converge (2027 Help, Tips). SARKAMARI's remaining penetration vanished at 30 substeps and 35 iterations, with Space Scale moved to 0.25 in the same pass [00:29:22] [00:29:57].
  • Cache, judge the cache, render the cache. nCache before every playblast; the render scene holds Alembics only (SARKAMARI [00:19:32], [00:40:07]).
  • Bifrost fails silently. Unpulled outputs are never computed, empty arrays are valid data, mismatched arrays truncate (Jason E3aOt5wuvoo [00:22:49]; Nordenstam [00:38:11]; graph doc). A sim solves only forward from its own start frame: default 1, and it must exist in the timeline (sim guide; Nordenstam [00:56:23]).
  • Do not simulate what you do not need. Start a snowball at the collider with its impact velocity (Gast [00:55:18]); layer garments through Alembic colliders (SARKAMARI [00:32:06]); coarse background sources (Stamatelos [00:21:25]).
  • One change per run, logged (Jason cd3HgvM8sXg [00:21:43]); mx_fx.set_attrs returns the log.

Establish first

InputWhy it changes the planDefault when silent
Shot range, fps, action startpre-roll, cache range, handles24 fps, pre-roll 50 frames before the action
Character deliverysim duplicates need a skinned or cached bodyreferenced rig or Alembic from scenario-maya-animation
Linear unit and real sizesolver scalecm, real size checked with mx_fx.scale_report
Destinationfilm (Arnold, VDB, Alembic) vs game (sprites, baked meshes, USD)Arnold film
Camera and motion blurwhat penetration is acceptableshot camera, blur on
Fabric or materialpreset, stiffnesscape: heavy denim values [added pick]; dust: Aero smooth
Budgetsubsteps, resolution, sim time per framefirst pass 10/12, detail 0.1; final 30/35

Workflow

  1. Scale and inputs. mx_fx.scale_report(meshes, expected_size_m=...); if the model is not real size, fix the asset (Julan [00:02:02]). Record any deliberate non-physical scale (SARKAMARI's 0.25 on a 182 cm character) with art_choice=True. GATE: no error line.

  2. Pick the system (options keyed to the brief):

    EffectDefaultAlternative and when
    Cape, garment on a characternClothBifrost MPM cloth when it must tear, live in a Bifrost graph, or go to a game via USD (Jason hmuWr2nWSms, yo6y7cANfX0)
    Dust puff, smoke, mistBifrost Aeroadd MPM sand or snow for dirt clumps; nParticles for grit (doc-level only)
    Snow, sand, mud impactMPM granularnone in the sources
    Scatter, crowds of copies, motion graphicsMASH (Repro)Instancer for speed; Bifrost scatter_points for USD point instancers
    Liquidsbasic_liquid_graphlegacy Bifrost Fluids is gone
  3. Prepare cloth inputs. Topology gate mx_fx.cloth_topology_verdict(mx_audit.audit(garment), expected_border_loops=1): evenly spaced quads (cross links need quads), manifold, single-sided, holes sealed (SARKAMARI [00:03:05]). Pre-roll mx_fx.add_preroll(ctrls, action_start, rest=bind_pose); duplicates at the bind frame with mx_fx.sim_duplicate. GATE: verdict clean, the duplicate follows the original within 0.01 cm.

  4. Build.

    • nCloth: mx_fx.build_cloth_rig(garment_SIM, body_SIM, action_start, preset=...): one nucleus, Space Scale for the unit, start at the pre-roll, first pass substeps 10 / iterations 12, preset values, thin cloth and collider. Pin a cape collar with an input-attract lock map (value 1 plus Input Attract Method "Lock values of 1.0 or greater", Collide Last Threshold 1.0, [added] recipe from the doc) or Point to Surface with Exclude Collisions (SARKAMARI [00:23:40]), members on the input mesh (output-mesh members risk a DG loop, doc; point_to_surface(..., cloth=) rewrites them). GATE: rig["verdict"] has no error.
    • Bifrost: start from basic_*_graph and Explode (Stamatelos [00:39:07]); script it with mx_fx.BifrostGraph (logs every VNN call) or reuse a GUI Echo All Commands log. Hide what you bring in (Jason). Open or flat emitters (ring, ground patch) need Shell, closed ones Solid (Stamatelos [00:10:40]). Set the sim's start frame. GATE: aero_source_verdict(...) on emitter_facts(mesh) and sim_range_verdict(...) clean; every output pulled; point or voxel count above 0 on every frame.
    • MASH: mx_fx.mash_network(sources, geometry="Repro") [verify MASH.api]; unit-size sources (Waters). GATE: mx_fx.mash_cache_reasons(mx_fx.mash_inventory(waiter)) read.
  5. First pass cheap, then cache. Low resolution (Aero detail 0.1, cloth first pass), frames evaluated in order from the start frame (mx_fx.run_sim, step_frames), every frame played in the GUI. After a geo_detail_size or time_step_size change, or a compound created or exploded, re-run from the start (sim guide). GATE: nothing non-finite, no empty frame.

  6. Measure and look. rep = mx_fx.sim_report(cloth_out, body_SIM, start, end, action_start=..., thickness=...), rep["convergence"] = mx_fx.convergence_test(...), mx_fx.sim_verdict(rep, budget_spf=...) (adds the doc's Timing Output gate: solve seconds per frame against the brief). Then look: headless mx_review.review([cloth_out, body_SIM], out, views=("side","back","threequarter"), modes=("clay",), focus=fixed) at the action start, the peak and the last frame; GUI mx_review.playblast from the shot camera; volumes with mx_fx.volume_review (Arnold, tricubic). Judge with references/critique.md.

  7. Triage in this order (never stiffen first): scale; start state (pre-roll, Push Out, Crossover Push with Trapped Check); substeps with iterations above; thickness down, Self Collide Width Scale up; stretch and compression together (SARKAMARI [00:24:50]); Bend Solver High Quality for flips; Collide Last Threshold 1.0 when attract or rigidity drags cloth through; lower Strength on popping constraints; "frame change too large" means play from the start or cache (2027 Help). Leftover pokes: a sculpted corrective on the cached mesh, or accepted under blur (SARKAMARI [00:37:12]). Aero detail: 2027 sharpening (aero_refinement_settings, low amount), adaptivity bounds, or post_refine_aero on the cache (frames in order, original sources and colliders) before lowering detail size everywhere (sim guide).

  8. Final cache and deliver. Final pass settings, nCache from the nucleus start (ncache_verdict: mcc stops at 2 GB, use mcx; positions only, so the cloth transform must stay still), disable the nucleus, Alembic of cloth and body over the shot range with UVs and color sets (mx_fx.alembic_export); Bifrost file_cache with only the properties the renderer needs; a cache-only render scene. GATE: mx_fx.alembic_check and file_sequence_report clean, a look at the cache.

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

Numbers

ValueRelative toSource
Space Scale, scene_units_in_meters 0.01cm scene2027 Help; Stamatelos
Nucleus 3 / 4 (presets), 10 / 12 first pass, 30 / 35 finalsubsteps / max collision iterationsdoc; SARKAMARI
Pre-roll hold 25 + blend 25, start -50action at 0SARKAMARI
Trousers friction 0.1, stretch 80, compression 20, damp 0.4 then 0.2, mass 0.8T-shirt preset 0.3 / 35 / 10 / 0.8 / 0.6SARKAMARI; doc
Loose shirt stretch 40, compression 15, mass 0.2, damp 0.3sameSARKAMARI
Rest length 0.9 tight, 0.5 bunching; attract 0.7 [?] collarpainted regionsSARKAMARI
Collide Last Threshold 1.0 (default 0.2)attract or rigidity in usedoc
Aero ambient 20, source 580, buoyancy -9.81rise comes from the differenceStamatelos
Aero detail 0.1 preview, 0.05 default, 0.025 fineAbsolute mode (world units); Relative keeps the voxel count constantJason; Stamatelos
MPM initial_firmness about v squared (10 m/s: 100)impact speedGast
MPM cloth area preservation 0.1 (0 = stiffest), vibration speed +10 steps, collision max speed about halfclothJason
Sprites 64 frames x 512 px, 8 x 8 on 4096; density 0.005 for the SDFflipbookJason

Quality gates

  • In code: cloth_topology_verdict, scale_report, nucleus_verdict (iterations above substeps, scale, pre-roll), sim_verdict (zero penetrating vertices after the action, stretch under 1.10 x rest [added], pops, settle, standoff, convergence, solve time), alembic_check (range, one mesh, vertex count), file_sequence_report (every frame, no runaway growth), sim_range_verdict (cache and review reach the shot end), ncache_verdict, mash_cache_reasons, overlaps (instances), sprite_framing, usd_check_unreal.
  • Visual: cloth weight and swing against reference at the character's speed, folds, armpit and back view with smooth preview, collar stiffness, garment stays on the shoulders, penetration visible in the shot camera or hidden by blur (SARKAMARI [00:36:39], [00:37:46]); smoke rises, breaks up, dissipates, no disappearing voxels, stepped trails or collider gap, judged in the render (Stamatelos; sim guide); MPM crack pattern, piece size, debris; MASH jitter while scrubbing a deforming mesh (Waters [00:03:53]).

Common mistakes

MistakeLooks likeFix
Space Scale 1 in a cm sceneslow, floaty giant cloth0.01, or record an art choice
Iterations at or below substepsextra steps change nothingiterations above substeps
No pre-roll, sim starts on the actionexplosion or intersection at frame 1hold plus blend, start -50
Alembic range starts after the nucleus startsolver jumps, cloth pops or freezes [added, verify]cache first, or export from the start frame
Thick cloth for self collisionsbloated cloth standing off the bodythin cloth, Self Collide Width Scale
Bifrost output not pulledobject vanishes, no errorroute feedback and debug nodes to the output
Stepping from after the sim's start frame, or a start frame outside the timelinefirst frames do not solve, or nothing happensstep from the start frame (sim_range_verdict)
Absolute resolution with a small detail sizevoxel count explodes, Maya hangsRelative, or an aero_source_verdict estimate under budget (Stamatelos [00:12:48])
Dust sourced hotrises as a plume instead of spreadingtemperature at ambient 20, initial speed and inherit velocity [added from Stamatelos' knobs]
Uniform smoke sourcelumpy mushroom cloudvary_source_property, noise-deformed emitter, turbulence, dissipation (Jason)
Relative collider detail on a big groundgap under smoke or snowsmaller collider detail, link_collider_detail (MPM)
MPM pin plus direct make-to-simulate linkcloth simulated twiceremove the direct link
Face-area MASH scatter on a skinned meshpoints jitterMesh from Points, skin, copy weights, Vertex + Flood
Animated Time Scale without Simulated Timecatch-up burstSimulated Time, then bake

Handoffs

  • Receives from scenario-maya-animation: a referenced rig or an Alembic of the character, the approved shot range and fps, bind pose available (for the pre-roll), validate(profile="shot") clean. Asks for pre-roll room before the action if the timeline starts on it.
  • Delivers to scenario-maya-lighting-rendering: a new scene version <shot>_fx_render_v###.ma holding only caches; Alembics <asset>_<fx>_v###.abc (UVs, color sets, shot range plus handles) and the body they collided with (SARKAMARI [00:39:34]); VDB sequences with only density and velocity (plus temperature for fire); Bifrost caches .bob for resumable work; sim_report.json, the review sheet or playblast looked at, and what was not verified. Units cm, Y-up; frame range stated.
  • Delivers to scenario-maya-pipeline-scripting (games): flipbook passes (emission, volume_direct, tangent-space normals) with sprite_framing clean, baked Alembic or USD meshes checked by usd_check_unreal, low resolution for engines (Jason yo6y7cANfX0 [00:05:09]).
  • Asks scenario-maya-rigging for a closed, simplified collider proxy when the render body is open or heavy.

Maya 2027 notes

  • Bifrost 3.0 (3.1.0.8 in 2027.1) is always installed; async evaluation; Batch Execute and Write State; node search. Legacy Bifrost Fluids is gone: basic_liquid_graph.
  • MPM 2027: link_collider_detail, max_voxel_movement retries, lag_colliders, initial_firmness.
  • Bifrost doc names disagree (simulate_liquid(s), liquid_solver_settings vs _properties, geo_volume_mode given to both Solid/Shell and Absolute/Relative): read ports with BifrostGraph.find_port.
  • nCloth Bend Solver default is High Quality. Cached Playback can cache dynamics in memory; files on disk remain the handoff.
  • MASH: Signal replaced Noise and Trig, Strength replaced Mute, nodes act on TRS, Repro is the default, Delay offsets transform animation.
  • Alembic is Ogawa only. AbcExport's -j string splits on spaces [added, verify]: alembic_export writes to a space-free temp path first.

References

  • references/procedures.md: full code for every stage (cloth, Bifrost, MPM, caches, VDB review, sprites, USD, MASH). Load before scripting.
  • references/expert-notes.md: principles by expert with timestamps, and the choices where experts disagree. Load when a setting needs a reason.
  • references/critique.md: the rubric to judge a sim, cache or scatter. Load before calling an effect done.
  • references/gui-paths.md: menus and hotkeys for a computer-use agent, plus the Echo All Commands discovery path.
  • references/sources.md: every source, credential, URL and best timestamps.
  • scripts/mx_fx.py: the toolkit (docstring lists every function). Tests: tests/code/maya-fx/.

© 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/dcc/maya/scenario-maya-fx of scenario-labs/skills.

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

Open the folder on GitHubat commit f6f8ab7

Compare with similar skills

Scenario Maya Fx 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 Maya Fx compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Scenario Maya Fx this skillscenario-labs/skills946—~5.3kAutomated safety check: PassMIT
Export Pipelinearjun988/blender-skills283—~1kAutomated safety check: PassMIT
Sprite Genaldegad/sprite-gen2.7k—~4.9kAutomated safety check: PassApache-2.0
3D Image Rendererhassancs91/claude-image-generation102—~1.4kAutomated safety check: PassMIT
Motion DesignWrongStack/WrongStack371—~852Automated safety check: PassMIT
Threejs World Generationcalesthio/OpenMontage66k—~2kAutomated safety check: PassAGPL-3.0

Similar skills

  • Export Pipeline

    arjun988/blender-skills

    Production export from Blender to FBX, GLTF, OBJ, USD, and Alembic with scale, pivot, rotation, normals, materials, animation, and collision verification via MCP.

    283 GitHub stars~1k tokensUpdated 3 mo ago
    Game DevelopmentAuto-check passed
  • Sprite Gen

    aldegad/sprite-gen

    Generates images and game sprites through GPT or Grok with guided provider choices, separate saved defaults, automatic cleanup and optional curation.

    2.7k GitHub stars~4.9k tokensUpdated yesterday
    Game DevelopmentAuto-check passed
  • 3D Image Renderer

    hassancs91/claude-image-generation

    Generate PNG images by building a real Three.js 3D scene and capturing one frame headlessly — no image model involved.

    102 GitHub stars~1.4k tokensUpdated 1 mo ago
    Game DevelopmentAuto-check passed
  • Motion Design

    WrongStack/WrongStack

    Implement web and React animation, gesture feedback, layout transitions and scroll sequences.

    371 GitHub stars~852 tokensUpdated yesterday
    Game DevelopmentAuto-check passed
  • Threejs World Generation

    calesthio/OpenMontage

    Build deterministic, editable, free-viewpoint Three.js worlds from text or structured briefs.

    66k GitHub stars~2k tokensUpdated 7 days ago
    Game DevelopmentAuto-check passed
  • 2D Map and Scene Generator

    0x0funky/agent-sprite-forge

    Plans and builds 2D game maps and scenes, from tilemaps and parallax backgrounds to HD-2D plates, with collision checks, a playable HTML preview and Tiled, Godot or LDtk export.

    4.4k GitHub stars~2.9k 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 Maya Fx

What does Scenario Maya Fx do?

A skill your agent uses when a Maya task involves simulation or procedural effects: nCloth or Nucleus (a cape, skirt, flag or garment on an animated character, cloth through the body, jittery or…. Scenario Maya Fx is an agent skill from scenario-labs/skills. Use when a Maya task involves simulation or procedural effects: nCloth or Nucleus (a cape, skirt, flag or garment on an animated character, cloth through the body, jittery or stretchy cloth), nParticles, Bifrost graphs (Aero smoke, dust puff, mist, fire, liquids, MPM cloth, snow, sand, "Bifrost smoke"), MASH scattering or motion graphics, sim caches (nCache, Alembic, OpenVDB, filecache, USD) or FX delivered to lighting or a game engine (flipbook sprites).

When should I use Scenario Maya Fx?

Scenario Maya Fx fits situations like: A Maya task involves simulation; procedural effects: nCloth; nucleus (a cape; garment on an animated character.

How do I install Scenario Maya Fx in Claude Code?

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

How do I install Scenario Maya Fx in Codex?

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

Can I use Scenario Maya Fx 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-maya-fx -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-maya-fx, .gemini/skills/scenario-maya-fx, .github/skills/scenario-maya-fx and .opencode/skills/scenario-maya-fx in your project.

What does Scenario Maya Fx need to run?

Going by SKILL.md and its folder, Scenario Maya Fx 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 Maya Fx 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 Maya Fx 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 Maya Fx use?

Scenario Maya Fx 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 Maya Fx use?

About 5.3k 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 28k tokens, read only when the agent opens those files.

What are the alternatives to Scenario Maya Fx?

Skills that share tags, products or a category with Scenario Maya Fx: Export Pipeline (arjun988/blender-skills, 283 stars), Sprite Gen (aldegad/sprite-gen, 2.7k stars), 3D Image Renderer (hassancs91/claude-image-generation, 102 stars) and Motion Design (WrongStack/WrongStack, 371 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Scenario Maya Fx?

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.