scenario-zbrush-hard-surface
Use when modeling hard surface in ZBrush 2026 (sci-fi helmet, weapon, prop, armor plates, mechanical parts, kitbash, vents, panel lines, bolts, concept to game asset), when using ZModeler, Dynamic Subdivision and creasing, Live Boolean, Knife, Clip, Slice or Trim curves, IMM, ArrayMesh, NanoMesh orβ¦
Install / Use
npx skills add scenario-labs/skills --skill scenario-zbrush-hard-surfaceInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
OtherSupported Platforms
Tags
Our assessment of scenario-zbrush-hard-surface
scenario-zbrush-hard-surface scores 86/100 on our quality scale, 195th of 354 Other skills we index.
Its SKILL.md is 19 KB long, well organised into 11 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-zbrush-hard-surface 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-zbrush-hard-surface compared with similar skills
All 4 of these similar skills score higher than scenario-zbrush-hard-surface; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| scenario-zbrush-hard-surface (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-zbrush-hard-surface?
- Run
npx skills add scenario-labs/skills --skill scenario-zbrush-hard-surface. The install tabs above show the steps for each supported agent. - Which AI agents does scenario-zbrush-hard-surface 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-zbrush-hard-surface 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-zbrush-hard-surface still maintained?
- The repository was last updated 35 days ago, so scenario-zbrush-hard-surface is actively maintained.
Skill content
View source on GitHubname: scenario-zbrush-hard-surface description: "Use when modeling hard surface in ZBrush 2026 (sci-fi helmet, weapon, prop, armor plates, mechanical parts, kitbash, vents, panel lines, bolts, concept to game asset), when using ZModeler, Dynamic Subdivision and creasing, Live Boolean, Knife, Clip, Slice or Trim curves, IMM, ArrayMesh, NanoMesh or Panel Loops, or when edges look razor sharp, a Make Boolean Mesh fails or leaves holes, planes look wobbly, Mirror And Weld erased an edit, or ZRemesher ruins a hard-surface part." license: MIT
ZBrush hard surface
Hard surface is judged as a result: it reads as manufactured when every edge is clearly straight or
clearly curved, planes carry an even highlight, edges are wide enough to catch light and every part
could be built (Plouffe, Klimer). The agent builds that language from deterministic operations
(primitives, Live Boolean stacks, polygroups as the crease plan, Dynamic Subdivision numbers,
ArrayMesh, Panel Loops) and uses clicks and strokes only where nothing else exists. 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-zbrush-expert (bridge, stroke engine, review loop, 2026 traps).
Toolkit: scripts/zb_hardsurface.py
(import sys; sys.path.insert(0, "<this skill>/scripts"); import zb_hardsurface as hs, then
hs.hs_call("new_part", "cube")), built on the lead's zb_ops, zb_review, zb_audit and
zb_stroke. Nothing in it has run in ZBrush yet.
Stance (the expert delta)
- Polygroups are the crease plan. Groups By Normals at 45 degrees (33 catches softer planes, 60 misses edges), Mirror And Weld, UnCreaseAll, Crease PG (Pavlovich; Plouffe). Crease first, a loop only where the falloff must be local. Crease PG after later edits recreases borders you softened on purpose: regroup, or crease by angle.
- The gap SmoothSubdiv minus CreaseLvl sets the edge. 0 reads razor, "very CG"; the closer
CreaseLvl sits to SmoothSubdiv, the tighter the edge, so 4/3 is tighter than 4/2
(
hs.edge_width). Pavlovich works at 3/2 and bakes 4/2; Plouffe keeps CreaseLvl 3 over a razor 4 and calls 2 too soft. Deciding condition: render both under metal, keep the widest edge that still looks planned. - QGrid is for boxy blocks (it facets arcs). Curved spans take Smooth Subdiv plus Crease Tolerance, tuned per span: 22 held Pavlovich's arch; too low creases the arc's small angles.
- Booleans need clean inputs (Live Boolean doc; Pavlovich): watertight, no coplanar faces, similar density, low Dynamic levels, nothing partly hidden. DSDiv on, one Start group per separate part, then ZRemesher Detect Edges at Half. Creases, UVs, levels and layers die in the boolean; polygroups survive.
- Keep cuts and repeats live. ArrayMesh the cutter, not the result. Instanced fasteners (NanoMesh, ArrayMesh) make a late "flathead, not Phillips" one Edit Mesh swap; per-seat imports cost one call per seat.
- Straight or curved, never in between (Plouffe). Polish planes, then edges, then corner softness, sharp to smooth; never mix sharp and round edges close together; one cavity along a border sells a separate plate.
- Function and camera set the detail (Klimer): how it is made, where power flows, one fastener family, repeated angles identical. Validate twice in engine: the block (500 to 40k polys) with the rig, then a decimated high under 1M points. Unseen interiors and undersides stay filled or simple, sold by dark AO (Pavlovich).
- Micro detail waits for sign-off, on 3D layers (Klimer): a negative strength carves in, duplicating doubles, and a layer dies with any topology change, so layers come after the last boolean, remesh or Apply [added].
- Mirror And Weld always copies negative X onto positive X. Good half on +X: Deformation Mirror first (Pavlovich, Plouffe). Slice, Trim and BRadius ignore symmetry, so every one-sided edit ends here.
What the agent can and cannot do here
| Deterministic (script it) | Click or stroke [verify] | GUI only, or substitute |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Primitives, Unify, placement (new_part, place, import_part); Live Boolean roles (set_roles, roles_from_groups), DSDiv, Make Boolean Mesh, Show Coplanar and Show Issues | ZModeler: a saved brush or 2026 preset holding the action and crease option, one canvas_action at click_target (a drag the first time; a tap replays) | Clip, Trim, Slice, Knife (Ctrl+Shift drag; press_key is broken): boolean cutters, fitted_split_groups, DynaMesh Groups on a group outline, a ZScript IKeyPress wrapper (scenario-zbrush-automation) |
| Dynamic Subdiv, CreaseLvl, CTolerance, Crease PG, Crease Bevel, Apply | NanoMesh insert: one click on a face of the target group, or on a front-facing plane (the shipped macro's routine) | Gizmo deformers: Deformation sliders on an axis-aligned part |
| Groups By Normals, Mirror And Weld, Panel Loops, GroupsLoops, ArrayMesh, NanoMesh sliders, MeshFromBrush (fastener_from_brush), masks (mask_fillet), ZRemesher, DynaMesh, Decimation | IMM: a synthesized Dots stroke, or Curve Mode on script curves; imm_ready first | Retopo brush, Mask By Polypaint dialog, freehand masks, hPolish planing (weak strokes) |
Establish first
| Input | Changes | Default when silent |
| --------------- | ------------------------------------------------------------ | -------------------------------------------------------------------------------------------- |
| Destination | game (bake to a low), film, print collectible, concept read | game asset baked to one 2048 map (Pavlovich's pistol) |
| Camera | first person and ADS, third person, turntable, print framing | third person; detail sized to what reads there |
| Budget | low-poly triangles, map size, high-poly cap | report counts and ask; never invent a budget |
| Function sheet | how it opens, vents, power, how it is made, fastener family | write one before blocking (Klimer) |
| Scale | rigged: real scale in the block; concept: proportion | Unify (about 2 units), Z forward, perspective off (Chervenka); mm briefs via to_tool_units |
| Moving parts | a hinged visor stays a separate part and Start group | separate |
| Painter handoff | Substance Bridge, or OBJ plus an external bake | ask; both are below |
Workflow
- Setup. Proxy or concept as a SubTool; Unify, Z forward, X symmetry; versioned ZTL before every boolean, DynaMesh, ZRemesher and Apply (no undo from Python). GATE: longest bbox side about 2; ZTL on disk.
- Block.
new_partandplace, orimport_partfrom a DCC block; body first, cutters below. GATE: forms sheet (zb_review.review) against the concept; a rigged asset's block OBJ checked in engine with the rig before detailing. - Shell. Deformation sliders on primitives, subtractive boxes for openings, Make Boolean Mesh,
zremesh_recipe("after_boolean"). The sculpted route (DynaMesh 128 to 176, hPolish, TrimDynamic) is concept only. GATE:hygiene(obj)ok (it stands in for Check Mesh, which reports through a note); PolyFrame shows even quads. - Crease plan.
crease_by_groups(45),dynamic_subdiv(intent="working"); arcscrease_by_angle, tuned per span. Loops and insets made with ZModeler take their crease at creation (zmodeler_plan: Insert EdgeLoop "Crease"; Inset "Crease New Edges" crisp, "Crease Inner Poly" rounded; defaults are Do Not Crease). GATE:check_crease; metal sheet (review_sheets) shows soft, light-catching edges, no scalloping, symmetric polygroups. - Cuts and vents. Cutters
new_part(..., op="sub")through the surface, never flush; Smooth 3 / CreaseLvl 2 plus crease by angle;array_meshon the cutter. GATE before:stack_report()["problems"]empty,coplanar_reportclean, Show Coplanar snapshot has no red,array_planwalls ok. Thenmake_boolean_mesh(short timeout). GATE after: UMesh SubTools equal Start groups; Show Issues snapshot clean; recrease (Crease PG unless a border was softened on purpose);hygienebefore ZRemesher. Any one-sided edit:mirror_report,mirror_weld(keep=...), thenmirror_checkon exports before and after. - Panels and fitted parts. Plan panels as polygroups first. Real separations: Panel Loops with
Plouffe's recipe (
panel_loops). A visor or hatch that fits its opening: one cutter used twice (fitted_split_groups: Intersect in one Start group, Subtract in the other), or DynaMesh Groups on a group outline. Seams: a thin subtractive cutter fromborder_polylinespluscurve_mesh[verify]. Masks:mask_fillet(Klimer's blur, invert, repeated). GATE:split_copy("groups")counts panels; gaps constant on the sheet. - Hardware. One family. ArrayMesh rows; radial sets as ArrayMesh Rotate 360 then
array_commit("nano")with ZRVar variation (Chervenka); a part from an IMM without a drag:fastener_from_brush; no face where a bolt goes: a helper plane. A port across a seam:seam_port_groups(Pavlovich). Exact runs:spaced_points. GATE: count, orientation and the same fastener everywhere on the sheet. - High-poly commit.
bake_split(): Apply at 4/2 on a copy, Dynamic off on the original. Exact chamfer widths: Crease Bevel width or a boolean chamfer, since Polish only gives the minimum (Polycount). GATE: levels = 1 + Flat + Smooth;edge_languagehas no ambiguous lines;plane_flatnessno wobbly groups;pinch_reportflags nothing. - Micro detail (after sign-off). Layers per region (Tool:Layers:New; procedures P15). GATE:
layer_safe(recorded, zb_ops.stats())before and after each pass. - Low poly and handoff. Dynamic-off cage; ZR
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.
