Skill This
AI Skill Report Card

Creating 3D Models and Animations

B68·Sep 28, 2026·Source: Extension-page
Quick Start12 / 15

For any 3D asset request, follow this pipeline order — do not skip steps:

  1. Concept & requirements: gather client/creative brief (style, scale, poly budget, platform target, deadline).
  2. Blockout: rough primitive shapes to validate proportions and composition.
  3. Model: high-detail sculpt or hard-surface model.
  4. Retopology & UV unwrap: clean topology for animation/game engines, non-overlapping UVs.
  5. Texture/Material: PBR textures (albedo, normal, roughness, metallic) or stylized shaders.
  6. Rig (if animated): skeleton, weight painting, controls.
  7. Animate: keyframes, storyboard-driven sequences, physics/secondary motion.
  8. Light & Render: set up lighting, camera, render passes.
  9. Review & Deliver: export in required format (FBX, OBJ, glTF, USD), check platform constraints.
Recommendation▾
Examples are still fairly abstract summaries of a process rather than concrete input/output pairs with specifics (e.g., actual texture map names, mesh stats, or file structure); add a truly concrete example showing actual deliverable output like a file tree or export settings.
Workflow14 / 15

Progress checklist for a typical asset:

- [ ] Clarify use case (film/game/architecture/product) and technical constraints (poly count, engine, file format)
- [ ] Collect references and concept sketches
- [ ] Blockout / gray-box the scene or object
- [ ] Get stakeholder sign-off on blockout before detailing
- [ ] Sculpt/model at final detail level
- [ ] Retopologize for intended use (real-time vs. render)
- [ ] UV unwrap and check for stretching/seams
- [ ] Texture with correct resolution/format for target pipeline
- [ ] Rig and weight-paint if the asset will animate
- [ ] Animate key sequences per storyboard
- [ ] Light, set camera, render test frames
- [ ] QA: check silhouette, scale, texel density, animation clipping
- [ ] Export and verify in destination engine/software
- [ ] Archive project files and reference images

Adjust depth per industry:

  • Gaming: strict poly/texture budgets, LODs, real-time engine compatibility (Unreal, Unity).
  • Film: higher fidelity, render-time budgets less strict, focus on shading and lighting realism.
  • Architecture: precision to scale/blueprint, material accuracy, walkthrough camera paths.
  • Product design: photorealistic materials, turntable renders, manufacturing-accurate dimensions.
Recommendation▾
This skill covers a domain (3D modeling/animation) that is largely performed in external software (ZBrush, Maya, UE5) rather than something Claude executes directly — clarify what Claude's actual role is (e.g., guiding a human, generating scripts/specs, writing pipeline code) since the skill doesn't address that gap.
Examples12 / 20

Example 1: Input: "Create a game-ready character model, max 15k triangles, for Unreal Engine 5." Output: Blockout → sculpt in ZBrush → retopo to ~14.5k tris in Maya → UV unwrap with 4 texture sets → bake normal/AO maps → PBR textures in Substance Painter → rig with Unreal Mannequin-compatible skeleton → export FBX with correct axis/scale settings for UE5 import.

Example 2: Input: "Design a storefront exterior for an architectural walkthrough." Output: Import CAD/blueprint reference → model to real-world scale in meters → apply accurate material libraries (glass, brick, metal) → set up daylight HDRI lighting → animate a walkthrough camera path → render at production resolution with AO and GI passes.

Example 3: Input: "Client wants a 15-second animated logo reveal." Output: Storyboard 3-4 key beats → block camera and object motion → model/extrude logo geometry → animate with easing curves and secondary motion (particles, light flares) → render with motion blur → deliver as ProRes/MP4 with alpha channel option.

Recommendation▾
Add edge cases specific to AI-assisted workflows, such as generating procedural assets via scripting (Python/MEL/Blender API), since without code or tool-specific guidance this reads as generic industry knowledge rather than an actionable Claude skill.
Best Practices
  • Always confirm technical specs (poly budget, texture resolution, target engine/format) before modeling — rework is expensive.
  • Blockout first; get approval before investing time in high-detail sculpting or texturing.
  • Match topology density to deformation needs — add edge loops only where the mesh bends (joints, facial areas).
  • Keep UV texel density consistent across an asset unless intentionally prioritizing focal areas.
  • Use non-destructive workflows (modifiers, layers, reference images) so revisions don't require starting over.
  • Maintain a reference/archive library of prior assets and client feedback for consistency across projects.
  • Test assets in the actual destination environment (game engine, render farm, AR viewer) before final delivery.
  • Communicate constraints and tradeoffs (realism vs. performance) clearly to clients/directors up front.
Common Pitfalls
  • Skipping the blockout stage and jumping straight to detailed sculpting — leads to costly proportion fixes later.
  • Ignoring topology flow, causing pinching or artifacts during rigging/animation.
  • Overlapping or poorly scaled UVs, resulting in blurry or inconsistent textures.
  • Exceeding poly/texture budgets for real-time targets, causing performance issues discovered too late.
  • Failing to confirm export/format requirements (units, axis orientation, embedded textures) before handoff.
  • Rendering final frames without doing low-res test passes first, wasting render time on lighting/composition mistakes.
  • Neglecting version control/archiving, making it hard to revert or reuse work.
0
Grade BAI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
12/15
Workflow
14/15
Examples
12/20
Completeness
15/20
Format
15/15
Conciseness
12/15
Save to My Skills