Agent skill

Scenario Maya Rigging

by scenario-labs in scenario-labs/skills

A skill your agent uses when rigging a character, creature or prop in Maya: "rig this character", placing or orienting joints, Orient Joint doing nothing, IK/FK switch and matching, pole vector…

MITAuto-check passedGame Development

Install Scenario Maya Rigging

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

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

GitHub CLI
$ gh skill install scenario-labs/skills scenario-maya-rigging --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-rigging .claude/skills/scenario-maya-rigging && 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-rigging
GitHub stars
946
Token cost
~5.2k tokens
SKILL.md length
2,069 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 rigging a character, creature or prop in Maya: "rig this character", placing or orienting joints, Orient Joint doing nothing, IK/FK switch and matching, pole vector…

  • Works in 10 steps: Gate the model.… → Place joints at pivots on edge loops:… → Build and orient. R.joint_chain(spec,… → …
  • Rigging a character
  • SKILL.md covers Stance (the expert delta), Establish first, Choose the path and Workflow, plus 6 more sections
  • Runs Python scripts from its folder; calls npx

What it does

Scenario Maya Rigging is an agent skill from scenario-labs/skills. Use when rigging a character, creature or prop in Maya: "rig this character", placing or orienting joints, Orient Joint doing nothing, IK/FK switch and matching, pole vector flips or elbow drift, space switching, foot roll, spline IK spine, offsetParentMatrix, blendMatrix or matrix rigging, controls and lockdown for animators, Quick Rig, HumanIK, AdvancedSkeleton or mGear, a game skeleton for Unreal or Unity, or a slow rig (parallel evaluation, profiling, GPU Override not kicking in).

Its SKILL.md is about 5.2k 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. 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

  • Rigging a character
  • Prop in Maya: rig this character
  • Orienting joints
  • Orient Joint doing nothing

Example prompts

  • “rig this character”
  • “/scenario-maya-rigging”

Requirements

  • Python 3
  • Node.js

Workflow steps

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

  1. Gate the model. mx_validate.validate(profile="model") clean; cm; height to spec (about 180); feet at y = 0; centered on X; frozen; eyes…
  2. Place joints at pivots on edge loops: spine joint under the rib cage (antCGi), wrist decoupled from the palm (Fragapane), elbows pre-bent…
  3. Build and orient. R.joint_chain(spec, parent, up="plane") for limbs, up=(0, 0, 1), up_axis="y" for spine and neck, world=[...] for root…
  4. Hand the bind skeleton to scenario-maya-deformation (it binds while you build controls): joints only, one hierarchy, labels, rig_check JSON.
  5. Control rig. R.ikfk_limb(bind[:3], name, rig_parent, ctrl_parent, own_solver=char + "_ikRPsolver"): handles of a type share one solver…
  6. Scale and stretch. Root scale only on groups that do not inherit it; stretch base lengths times root scaleY; IK spine joints under a…
  7. Lock down. R.lockdown; FK hinges keep their bend axis; limits; controller tags; selection sets. GATE: R.lockdown_audit and…
  8. Performance. Key first (R.rom_keys, two different values per used attribute): a keyless rig profiles fast and lies. R.eval_census(rig)…
  9. Review. R.rom_keys, then mx_review.playblast (GUI) or R.pose_review (headless); R.precision_test at shot distances…
  10. Deliver. New version, validate(profile="rig") clean, test JSON, playblast, what was not verified.

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

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

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

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,069 words, ~5,194 tokens.

Download SKILL.mdSave it as .claude/skills/scenario-maya-rigging/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
scenario-maya-rigging
description
Use when rigging a character, creature or prop in Maya: "rig this character", placing or orienting joints, Orient Joint doing nothing, IK/FK switch and matching, pole vector flips or elbow drift, space switching, foot roll, spline IK spine, offsetParentMatrix, blendMatrix or matrix rigging, controls and lockdown for animators, Quick Rig, HumanIK, AdvancedSkeleton or mGear, a game skeleton for Unreal or Unity, or a slow rig (parallel evaluation, profiling, GPU Override not kicking in).
license
MIT

Maya rigging

Expert rigging means every value is explained and every behavior measured: joints at real pivots with computed orientation, controls at zero with their placement in offsetParentMatrix, IK/FK and space switches that move nothing, and a rig that survives scale, distance, several characters per shot and an animator keying everything. The rig is the output of a build script and data. 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).

Module scripts/mx_rig.py (sys.path.insert(0, "<skills>/scenario-maya-rigging/scripts"); import mx_rig as R): not yet run in Maya; its pure math passed offline (test_rig_offline.py). With Maya installed, run tests/code/maya-rigging/run_all.sh and fix what test_rig_probe contradicts.

Stance (the expert delta)

  • Clean values, one place for each. Rotations zero at rest, orientation in jointOrient (or nowhere: Fragapane), control placement in offsetParentMatrix (antCGi; Maya Learning Channel). OPM composes, world = local * OPM * dagParentWorld (2027 transform node): feed .matrix for a relative drive, or multiply a worldMatrix by the DAG parent's worldInverseMatrix, then zero translate, rotate and jointOrient or they apply twice (Maya Learning Channel; antCGi's leg rotating backwards).
  • Compute, never eyeball. -orientJoint silently skips joints with rotations or no child (2027 cmds.joint); a secondary world axis along the bone is ill-defined (antCGi's toes). R.joint_chain computes jointOrient from positions; a pole on the chain plane adds zero drift (R.pole_vector_position) [added].
  • The animator defines done. Zero pop switching IK/FK at neutral, only the active mode visible, everything else locked because animators "select hierarchy and key all", limits at breaking points, behavior mirroring on limbs, same orientation on eyes and face (antCGi).
  • Matrices before constraint stacks, and know the blend. OPM, blendMatrix and pickMatrix keep channels free (Maya Learning Channel cut 20 joints from one hand). blendMatrix is an ordered stack, each target overriding the ones before (equal thirds: 1, 1/2, 1/3); parentMatrix (2025) normalizes and stores per-target offsets (2027 Help). Spaces blend offset targets, never the space itself, or the IK flips (antCGi).
  • The built rig is disposable. Guides, build script, serialized weights and settings; fixes go back into the data (Miquel Campos, mGear: "we serialize everything and we build clean every single time"; Bungie). Metadata and joint labels, not names, identify chains (Bungie). A skinCluster reads only influence world matrices and bindPreMatrix: reset the bind pose, never rebuild joints for it (Fragapane).
  • Structure decides speed. The Evaluation Graph leaves static curves out and rebuilds at the first differing key; without curves a rig "is going to be paralyzed terribly" (Fragapane; Using Parallel Maya 2027). Split components so cheap global work finishes early, even by duplicating cheap math (Fragapane); no Python nodes, scene-querying expressions or driven frozen; hosts out of the limbs (Miquel Campos); DG, Serial and Parallel agree before optimizing.
  • Test at the extremes. Scale 1.24 and 1.6 (antCGi), a million units away and upside down (Fragapane), three referenced characters, a quick bind while building (antCGi).
  • Deformation skeleton apart from the control rig. Engines see joints, skin and blendshapes only: one root at the origin, engine names, a joint budget (antCGi, Unreal and Unity docs, Bungie).

Establish first

InputChangesDefault when silent ([added] unless attributed)
Targetfilm keyframe rig vs engine skeleton (names, axes, influences, one root)feature keyframe rig, custom
Camera distance, styleauto-rigger or custom; twist and corrective joints; stylized: crude proportion rig and art-direction paintovers first, final-aim notes from day one (Miquel Campos)hero: custom; crowd: Quick Rig
Skeleton conventionreusing engine animation needs its names and hierarchyX down the bone, bend on local Z, positive Z flexes
Animator conventionsIK/FK default, spaces, colors, pickersarms FK, legs IK; spaces world, cog, chest, head; ask
Shot loadcharacters per shot, dense meshesthree referenced characters
Face, mocap, budgetface to scenario-maya-deformation; HumanIK; joint and influence countsjaw, eyes, aim control; ask the lead (antCGi: "it pays to be frugal")

Choose the path

Quick Rig + HumanIKAdvancedSkeletonmGear ShifterCustom (mx_rig)
biped facing +Z; game or background character "not looked at closely" (Maya Learning Channel); HumanIK when animation is retargeted (2027 Help); 15 nodes, strict T-stancebody plus face from a fit skeleton, rebuilt by toggling fit; engine export via Convert to BlendShapes Onlymany characters, a team, Unreal exporter; confirm a 2027 build for the OS first [verify]hero rig, strict engine skeleton, rigs the agent must rebuild and verify: this workflow

Workflow

  1. Gate the model. mx_validate.validate(profile="model") clean; cm; height to spec (about 180); feet at y = 0; centered on X; frozen; eyes dead ahead; loops at knuckles, elbows, knees; mouth bag for a face (antCGi). Send problems back as a list; never edit a client model unasked. GATE: no fail; wire sheet looked at.
  2. Place joints at pivots on edge loops: spine joint under the rib cage (antCGi), wrist decoupled from the palm (Fragapane), elbows pre-bent back, knees forward; the first upper-arm and thigh twist joint stays at the top with the shoulder or hip, mid twist joints are placed by position so they keep the parent's orientation (antCGi). GATE: R.chain_plane does not raise on any limb; joints over wireframe looked at.
  3. Build and orient. R.joint_chain(spec, parent, up="plane") for limbs, up=(0, 0, 1), up_axis="y" for spine and neck, world=[...] for root, cog, head, eyes and feet (antCGi: animators, engine foot placement), end_aim= for clavicles; existing skeletons: R.orient_with_cmds ('zup' for legs and spine). R.mirror_chain: behavior for limbs, orientation for eyes and face; rotate orders on controls (R.rotate_order(twist, main); Fragapane); R.set_preferred_angles(root). GATE: R.rig_check(joints=bind) clean; mirror within 1e-3 cm; all digits curl on one axis and sign, thumb fixed, so one attribute makes a fist (antCGi).
  4. Hand the bind skeleton to scenario-maya-deformation (it binds while you build controls): joints only, one hierarchy, labels, rig_check JSON.
  5. Control rig. R.ikfk_limb(bind[:3], name, rig_parent, ctrl_parent, own_solver=char + "_ikRPsolver"): handles of a type share one solver node, so several characters in a scene conflict (Fragapane: "can make a mess"; 2027 Help). Legs: extra=[ball, toe], orient_end=False, then R.reverse_foot with R.foot_pivots_from_mesh; spine P9; R.space_switch(ctrl, [None, cog, chest], names=[...]); R.ikfk_match(meta, to="fk"|"ik", key=True) uses stored offsets (antCGi instead adds a pole locator under the FK elbow and an ankle locator oriented like the IK foot). GATE: R.neutral_switch_test and pole drift below 1e-3; R.space_test as expected; FK and IK posed apart, R.blend_sweep_test finds no flip; roll sweep plants heel, ball, toe in turn; no shared-solver error; controls at zero.
  6. Scale and stretch. Root scale only on groups that do not inherit it; stretch base lengths times root scaleY; IK spine joints under a world-pivot scale group, as segmentScaleCompensate blocks scale (antCGi). GATE: R.scale_test at 1.24 and 1.6, neutral and stretched, below 1e-3 cm.
  7. Lock down. R.lockdown; FK hinges keep their bend axis; limits; controller tags; selection sets. GATE: R.lockdown_audit and R.opm_audit(rig) empty; the rig still works.
  8. Performance. Key first (R.rom_keys, two different values per used attribute): a keyless rig profiles fast and lies. R.eval_census(rig), R.eval_ab(bind, meshes, frames); R.prepare_eval_graph(root=rig) tags every control (with the animator's Preferences > Settings > Animation > Include controllers in evaluation graph, first keys stop rebuilding the graph) and turns on the curve manager for the session. R.gpu_override_census(meshes), then the GUI Evaluation HUD must show a non-zero k count, else deformerEvaluator -meshes says why. Profile DG, Serial, Parallel and GPU Override with 1 and 3 referenced characters; keep dated profiles (Miquel Campos). GATE: no census error; modes agree within 1e-5; each dense mesh on the GPU or its reason written.
  9. Review. R.rom_keys, then mx_review.playblast (GUI) or R.pose_review (headless); R.precision_test at shot distances; references/critique.md. GATE: frames looked at; elbows, knees, shoulders, wrists, feet read right.
  10. Deliver. New version, validate(profile="rig") clean, test JSON, playblast, what was not verified.
Show full SKILL.md (787 more words)Show less

Numbers

ValueRelative toSource
Twist joints: upper arm 2 (top, mid), lower arm 1, thigh 2, calf 1, plus wrist and footboneantCGi
Pole locator 30 units out by hand; computed pole distance = longer segmentelbowantCGi; [added]
Switch, drift, scale error below 1e-3 cm; mid-blend path within max(1 deg, 5%) of the direct anglebind joints[added] gates
Foot break 25 deg: ball = roll to 25, then 50 - roll; toe = roll - 25; limits footRoll -40..80, footBank -60..60footRollantCGi
Mid spine twist falloff 1, 0.5, 0.25ribbon jointsantCGi
Precision: problems at 1e5 units, flicker at 1e6rig top nodeFragapane
Hosts out of limbs: 20 to 17 ms per frameone characterMiquel Campos
GPU Override: over 2000 vertices (NVIDIA), 500 (AMD); MAYA_OPENCL_DEFORMER_MIN_VERTS, 0 sends allper meshUsing Parallel Maya 2027
blendMatrix equal shares: 1, 1/2, 1/3 ...; counting the inputMatrix: 1/2, 1/3 ...ordered stack2027 Help; [added]
HumanIK 15 nodes; Unity 4 influences; Unreal FBX 2020.2engine contractdocs

Quality gates

Code (mx_rig): rig_check (rest rotations, orientation, controls, poles, shared solvers, OPM doubling, evaluation census, lockdown), neutral_switch_test, blend_sweep_test, space_test, scale_test, precision_test, eval_ab, gpu_override_census, game_skeleton_check; scenario-maya-expert's validate(profile="rig").

Visual: placement over wireframe front and side; ROM playblast of every control axis, front, side and three-quarter; foot roll scrubbed; scaled rig in an extreme pose. Look for knee pop, elbow flips, candy-wrapper wrists, collapsing shoulders, sliding feet.

Common mistakes

MistakeWhat it looks likeFix
Orient Joint on a joint with rotationsnothing changes, no errorfreeze rotations first, or R.joint_chain
Secondary world axis along the bone ('yup' on a leg, world Z on forward toes)thigh and calf axes disagreean axis across the bone; R.orient_with_cmds refuses it
Straight elbow or kneeIK bends the wrong way or backwardspre-bend, rebuild, set preferred angle
Pole off the chain plane; pole too closeelbow drifts when constrained; arm flips as the hand movesR.pole_vector_position; move it farther behind
worldMatrix into OPM under a moving parent, or values left under an OPM drivedouble transform, reversed rotationparent's worldInverseMatrix or .matrix; R.bake_to_opm; R.opm_audit
Equal blendMatrix weights for an averagethe last target wins1, 1/2, 1/3, or a parentMatrix node
Blending to a space's own matrixcontrol snaps onto the target, IK flipsoffset targets (R.space_switch)
Handles on the scene's shared solverreferenced characters conflict; one edit changes every rigown_solver per character
Settings host inside the limbslow playback (node-level cycle)host on the limb's parent space
Flip mid IK/FK blendtoes or wrist spin halfwayconstraint blend: interpType Shortest (antCGi); matrix blend: measure with R.blend_sweep_test
Profiling a keyless rignumbers collapse once animated; stutter on first keyskeys first; controller tags plus prepopulation
GPU Override HUD "Enabled (0 k)"nothing deforms on the GPUR.gpu_override_census, deformerEvaluator -meshes
Scale wired twice, or stretch not normalizeddouble scaling; limbs stretch when the rig scalesscale non-inheriting groups only; base length times root scaleY
Groups, handles, locators unlocked"key all" breaks the rigR.lockdown
Spline curve under its start joint; helpers under bind jointsdependency cycle; engine export errorskeep both outside the bind skeleton

Handoffs

  • Receives from scenario-maya-modeling or scenario-maya-retopology-uv: a mesh passing validate(profile="model"), cm, Y-up, facing +Z, feet at y = 0, centered, frozen, symmetric, pre-bent limbs, eyes forward.
  • Delivers to scenario-maya-deformation: the bind skeleton (joints only, one root, oriented, rotations zero, labels), rig_check JSON, and whether bind joints blend by constraint or through OPM (its pose readers depend on it); receives weights as data and correctives to reconnect.
  • Delivers to scenario-maya-animation: the rig to reference, controls at zero and tagged, validate(profile="rig") clean, switch list, ROM playblast, known limits.
  • Game rigs to scenario-maya-pipeline-scripting: game_skeleton_check clean, bind blends by constraint unless an OPM export was proven; they export the FBX.

Maya 2027 notes

  • 2026 renames: addDL, multiplyDL, pointMatrixMultDL; plain math names create unitless nodes; condition, multiplyDivide, reverse, blendMatrix unchanged.
  • parentMatrix (2025) has Snap and Initialize Target Offset; axisFromMatrix replaces the per-axis nodes.
  • Orient Joint: negative primary axes fixed in 2027.1; Auto orient secondary axis since 2025.
  • ikHandle lists only RP, SC and spline; load spring and 2-bone solvers first. FBIK forces Serial: use HumanIK.
  • GPU Override: 2027.2 known issue, a crash when scrubbing with it on (disable it or the invisibility evaluator); the paper covers OpenCL on AMD and NVIDIA only, so read the HUD on Apple GPUs [verify]. Evaluator settings are per session, not saved in the scene.
  • Skin Tools layers block classic weight tools until deleted (scenario-maya-deformation). PySide6 only; PyMEL is not bundled.

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/dcc/maya/scenario-maya-rigging 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_rig.py

Open the folder on GitHubat commit f6f8ab7

Compare with similar skills

Scenario Maya Rigging 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 Rigging compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Scenario Maya Rigging this skillscenario-labs/skills946—~5.2kAutomated safety check: PassMIT
Godot Gdscript Patterns925236118/AlphaAgent10310 repos~5kAutomated safety check: PassMIT
Sprite Genaldegad/sprite-gen2.7k—~4.9kAutomated safety check: PassApache-2.0
2D Map and Scene Generator0x0funky/agent-sprite-forge4.4k—~2.9kAutomated safety check: PassMIT
Fantasy Framework Development Guideqq362946/Fantasy1.4k—~5.8kAutomated safety check: PassCustom licence
Dev StoryDonchitos/Claude-Code-Game-Studios26k—~2.4kAutomated safety check: NotesMIT

Similar skills

  • Godot Gdscript Patterns

    925236118/AlphaAgent

    Master Godot 4 GDScript patterns including signals, scenes, state machines, and optimization.

    103 GitHub starsUsed in 10 repos~5k tokens
    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
  • 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
  • Development and review guide for the Fantasy C# distributed game server framework: ECS, FTask, routing, service discovery, config and databases.

    1.4k GitHub stars~5.8k tokensUpdated yesterday
    Game DevelopmentAuto-check passed
  • Dev Story

    Donchitos/Claude-Code-Game-Studios

    Implement a story: ADR guidelines, right programmer agent, code plus test.

    26k GitHub stars~2.4k tokensUpdated 2 days ago
    Game DevelopmentAuto-check: notes
  • Plays an authorized Game Boy or Game Boy Color ROM in one persistent headless Coffee GB session, inspecting frames and keeping an action trace for replay or tests.

    1.2k GitHub stars~1.3k tokensUpdated 9 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 today
    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 today
    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 today
    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 today
    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 today
    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 today
    Auto-check passed

Questions about Scenario Maya Rigging

What does Scenario Maya Rigging do?

A skill your agent uses when rigging a character, creature or prop in Maya: "rig this character", placing or orienting joints, Orient Joint doing nothing, IK/FK switch and matching, pole vector…. Scenario Maya Rigging is an agent skill from scenario-labs/skills. Use when rigging a character, creature or prop in Maya: "rig this character", placing or orienting joints, Orient Joint doing nothing, IK/FK switch and matching, pole vector flips or elbow drift, space switching, foot roll, spline IK spine, offsetParentMatrix, blendMatrix or matrix rigging, controls and lockdown for animators, Quick Rig, HumanIK, AdvancedSkeleton or mGear, a game skeleton for Unreal or Unity, or a slow rig (parallel evaluation, profiling, GPU Override not kicking in).

When should I use Scenario Maya Rigging?

Scenario Maya Rigging fits situations like: rigging a character; prop in Maya: rig this character; orienting joints; orient Joint doing nothing.

How do I install Scenario Maya Rigging in Claude Code?

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

How do I install Scenario Maya Rigging in Codex?

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

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

What does Scenario Maya Rigging need to run?

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

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

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

What are the alternatives to Scenario Maya Rigging?

Skills that share tags, products or a category with Scenario Maya Rigging: Godot Gdscript Patterns (925236118/AlphaAgent, 103 stars), Sprite Gen (aldegad/sprite-gen, 2.7k stars), 2D Map and Scene Generator (0x0funky/agent-sprite-forge, 4.4k stars) and Fantasy Framework Development Guide (qq362946/Fantasy, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Scenario Maya Rigging?

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.