scenario-maya-groom
Use when grooming hair or fur in Maya with XGen (Interactive Groom splines or legacy descriptions): scalp hair, eyebrows, eyelashes, fur, guides, clumps, noise, parting, density maps, a fill layer, aiStandardHair shading, noisy or flickering hair renders, hair that must move (Linear Wire, nHair, Ale…
Install / Use
npx skills add scenario-labs/skills --skill scenario-maya-groomInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Project & Program ManagementSupported Platforms
Tags
Our assessment of scenario-maya-groom
scenario-maya-groom scores 86/100 on our quality scale, 37th of 84 Project & Program Management skills we index (top 45%).
Its SKILL.md is 20 KB long, well organised into 10 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 1,048 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 35 days ago, so scenario-maya-groom is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.
Automated pattern scan on 2026-11-20. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
scenario-maya-groom compared with similar skills
All 4 of these similar skills score higher than scenario-maya-groom; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| scenario-maya-groom (this skill)by scenario-labs | 86 | 1.0k | 35d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 2mo ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 2mo ago | SKILL.md |
| prospectingby coreyhaines31 | 100 | 60.1k | 11d ago | SKILL.md |
| ad-creativeby coreyhaines31 | 100 | 60.1k | 11d ago | SKILL.md |
Frequently asked questions
- How do I install scenario-maya-groom?
- Run
npx skills add scenario-labs/skills --skill scenario-maya-groom. The install tabs above show the steps for each supported agent. - Which AI agents does scenario-maya-groom work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is scenario-maya-groom safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is scenario-maya-groom still maintained?
- The repository was last updated 35 days ago, so scenario-maya-groom is actively maintained.
Skill content
View source on GitHubname: scenario-maya-groom description: "Use when grooming hair or fur in Maya with XGen (Interactive Groom splines or legacy descriptions): scalp hair, eyebrows, eyelashes, fur, guides, clumps, noise, parting, density maps, a fill layer, aiStandardHair shading, noisy or flickering hair renders, hair that must move (Linear Wire, nHair, Alembic caches), or a groom for Unreal (groom Alembic, cards). Also when XGen hair looks CG, clumps look uniform, the scalp shows through, or an XGen script fails." license: MIT
Hair and fur grooming (XGen Interactive Groom, Maya 2027)
Expert grooming sets the flow on a few guides first, then a clump hierarchy with loose roots and
varied profiles, then breakup only where the reference shows it (tips, strays), judged in close,
side-lit renders with the real hair shader. Interactive Groom brushes have no stroke API, so the
agent grooms with data (guides from a flow sheet wired into the stack, masks written as images,
modifiers set by value) and judges with numbers from exported strands plus renders. Code:
scripts/mx_groom.py (import mx_groom as G). If a sibling skill named here
is missing from your available skills, load it with skill_get (Scenario MCP) or ask the user to
install it (https://github.com/scenario-labs/skills#install); unattended, proceed from tool schemas
and flag the gap.
REQUIRED BACKGROUND: scenario-maya-expert (execution channel, review loop, 2027 version traps).
Status (2026-09-24): every Maya call here is not yet run in Maya (2027 not installed). The
pure layer of mx_groom passes offline (tests/code/maya-groom/test_mx_groom_offline.py). Names
not quoted from the 2027 help resolve at run time from G.NAME_CANDIDATES.
Stance (the expert delta)
- Flow first, on the guides, copied from arrows drawn over the reference (Fernandez). Flow is pressure: neighbors share the compression curve, and opposing streams meet through a straighter band. Short fur turns sharply, long hair slowly. Decide whether the flow or a clump owns each big shape.
- Roots loose, every clump different, two levels (Fernandez). No attraction over about the first
14 % of the length, or the base pinches into bald lines. 3 to 5 small clumps per big one; a third
level only for long hair or manes. Vary size and profile (
G.CLUMP_PROFILES: spike, onion). - Mask and tightness are different knobs (Fernandez 05, 06). The mask decides triangle versus
square: square clumps are tight small clumps inside a looser big clump, both masks lowered.
Tightness (IG Clump strength [added]) 0 keeps the clump's shape without converging; mask 0 removes
it. Straight guides make them look alike, so test on noisy guides (
G.clump_follow). - The level that gets the noise decides what breaks (Fernandez 07). Clump-level noise (the secondary Clump's Noise, tip half) breaks the big clumps and keeps the small ones and the roots; a Noise modifier breaks the small clumps too, so it goes on few hairs (Giovannini: 0 on the body, 3 on a 5 % share). Vary the frequency; fray only on few hairs. Stray clumps come from holes in the primary's mask, not a new system.
- The hairline reads real through thinner edge strands plus transition and peach-fuzz descriptions, not density alone (Hadi Karimi). One density map is shared by every description; each hair type gets its own description.
- A short fill layer hides the scalp (Giovannini): body guides cut to 2/3, so long hair need not be "crazy dense".
- Motion drives a few wires, never the hair (Flood). Export the wires from the Linear Wire's inGuide. Update the Reference State at the rest pose on frame 1. Curve to Spline gets Align to Normals off.
- Standard Hair realism comes from melanin, roughness and IOR (Arnold hair doc). Keep diffuse 0, tints white and indirect scales at 1, and use ribbon mode (Min Pixel Width only works there). Blond hair gets Extra Depth. Cost has four knobs (MPW, transparency depth, specular samples, AA); opacity below 1 costs significantly.
Establish first
Write the answers to brief.json before any node.
| Input | Changes | Default when silent |
| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------- |
| Target | Arnold strands, Unreal strands, or cards (MtoA renders no XGen Card primitives) | Arnold strands |
| Hair types | one description each: body, fill, fringe, strays, brows, upper and lower lashes, transition, fuzz. Close-up face: rule peach fuzz in or out (Hadi) | body + brows |
| Style | realistic: random clump points, Randomness > 0, melanin. Stylized: clumps on the guides (FlippedNormals), flat Base Color with Melanin 0 [added]. Both: a point on the defined-to-soft range, same silhouette (Fernandez 07) | realistic |
| Motion, and who owns it | static follow; keyed or simulated wires; rig or CFX department (Flood) or the groom file (2027 help) | follows the scalp |
| Still or animated | still likeness: grow on the head (Hadi). Animated or real time: scalp cap with clean UVs | scalp cap |
| Camera distance | Scattering Mode: Accurate for close-ups (10 to 30 % slower), Adaptive for mixed shots | Adaptive |
| Budget | spline count and GPU memory (xgmSplineQuery), Unreal sim guides | state a number |
| Reference | flow arrows and clump counts come from it | ask; else write the assumed look down |
| New or inherited | Interactive Groom for new work; legacy XGen only for an inherited asset or non-spline primitives | Interactive Groom |
Workflow
Headless mayapy (mx_run --plugins mtoa,xgen,abc, in that order) covers guides, masks, Alembic,
Unreal tags, lint, analysis and Arnold reviews; the GUI bridge covers the menu queries and whatever
the probe shows does not evaluate headless (IG computes on the GPU).
references/procedures.md P16 is the whole job as one script with every
gate asserted (G.gate raises).
- Probe and recipes (once per install).
G.probe()headless and in the GUI. Menu actions with no documented command are read, not clicked: through the bridge,G.menu_recipe(name)queries the item's command string (cmds.menuItem(item, q=True, command=True)) and stores it; Attribute Editor buttons (Make Wires Dynamic, Reference State Update, Rebuild) go throughG.button_recipe(name, node). Export Cache opens a dialog: write its@path@template fromG.recipe_source. GATE: probe JSON saved;recipe_status()shows the recipes the plan needs as recorded. - Scalp.
G.scalp_check(scalp, for_unreal=...). GATE: noerror:line, border edges present (the hairline), UVs unique. - Flow sheet and counts. From the reference write the flow sheet (
base,whorl,part,direction, length regions) and count big clumps and small per big. GATE:G.check_flow_sheet(flow) == []. - Guides.
g = G.make_guides(scalp, flow, spacing=..., cvs=8, collide=head), few first (FlippedNormals);symmetric=Trueonly on symmetric topology (Hadi). GATE:G.gate(G.measure_curves(...)["verdict"]), penetration 0, discontinuities only at parts and whorls. - Descriptions and wiring.
G.create_description(scalp, "hair_body")per hair type (recipe, renamed).G.wire_guides(desc, g["curves"]): a Guide modifier low in the stack interpolates the guides, fed by a Curve to Spline on its inGuide; it holds the region maps parts need. A Curve to Spline on the description itself turns each curve into one hair and disables everything below it: only for exact strands or caches. GATE:G.wiring_verdict: flow-sheet error of the hair drops after wiring, and the InGuide_base cache holds every guide. - Stack, density and masks. Bottom to top: base (CV count per Numbers), Scale, Guide, primary
and secondary Clump (
G.build_clumps), strand Noise on a share, length breakup, Collision.G.write_hairline_maskfor the hairline (band=True: transition), one map shared across descriptions (G.connect_texture),G.patchesholes in the primary's mask for stray clumps. GATE:G.gate(G.lint()["lines"]); thecoveragepass (showthrough %) and spline count within budget. - Clumps and breakup, one layer at a time (Giovannini). Once per install, P5b's two tests
settle the Clump Scale convention, which knob acts as tightness and what each noise level breaks.
Export mid-stack caches, then
G.hierarchy_from_states(3 to 5),G.breakup_reportandG.measure_abc. Render Clump before and after Noise once each (2027 help). GATE:breakup_verdictandstrand_verdictclean; a side-lit close-up passesreferences/critique.md, triangles and squares in the reference's proportion. - Shader and render.
G.hair_shader(desc, preset=...)(replaces the defaulthairPhysicalShader),G.curve_render(desc, "ribbon", min_pixel_width=...),G.cost_sweepover the four knobs with flicker. Save before rendering XGen. GATE:G.review(...)sheet judged with the critique, no shaderwarn:. - Motion. Static follow, keyed wires (Flood) or dynamics (Linear Wire, Make Wires Dynamic). Caches are versioned. GATE: renders at the rest, mid and last frames with no penetration.
- Deliver (Handoffs).
Numbers
| Value | Relative to | Source | | ------------------------------------------------------------------------------------------- | ---------------------------------------- | -------------------------------------------------- | | no clump pull over the first ~14 % | strand length, clump profile | Fernandez 02 [00:17:56] | | spike: 0.01 at mid length; onion: mid bulge ~0.9 | legacy Clump Scale ramp (radius reading) | Fernandez 02 [00:05:38], frames 00:06:00, 00:10:51 | | 3 to 5 small clumps per big; 2 levels
Truncated for display — read the full file on GitHub.
Related Skills
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
prospecting
60.1kWhen the user wants to find and qualify prospects for outbound, or asks who to target first, which signal to prioritize, or where to spot buyers with the problem: buying signals, enrichment, verification, account research.
ad-creative
60.1kWhen the user wants to write or judge ad creative, or asks which ad, hook, or angle to run or kill: headlines, primary text, and variations for Google, Meta, LinkedIn, and TikTok, fresh angles when creative fatigues. Test hypotheses name the metric, comparison, and expected direction.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
