跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
搜索与研究

3d-asset-production

Use this skill to turn generated, captured, scanned, or modeled 3D output into production-ready standalone assets for DCC, real-time engine, web, or interchange delivery. It covers requirements, topology repair, scale and axes, UVs, PBR baking, LODs, static and skeletal readiness, rig handoff, optimization, glTF/USD/FBX delivery, validation, QA, and rights/provenance. Do not use it for provider-specific generation prompts, full scene/world building, mocap operation, or exact CAD/manufacturing work.

calesthio · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add calesthio/generative-media-skills --skill 3d-asset-production

技能说明


name: 3d-asset-production description: Use this skill to turn generated, captured, scanned, or modeled 3D output into production-ready standalone assets for DCC, real-time engine, web, or interchange delivery. It covers requirements, topology repair, scale and axes, UVs, PBR baking, LODs, static and skeletal readiness, rig handoff, optimization, glTF/USD/FBX delivery, validation, QA, and rights/provenance. Do not use it for provider-specific generation prompts, full scene/world building, mocap operation, or exact CAD/manufacturing work.

3D Asset Production

This skill is for finishing an asset so another artist, engine, viewer, marketplace, configurator, game, AR app, or renderer can actually use it. The input may be generated mesh output, photogrammetry, NeRF/GSplat-derived mesh, scan cleanup, sculpt, CAD-derived polygon export, hand-modeled geometry, or a kitbashed draft. The output is a documented, validated asset package with predictable geometry, scale, materials, texture maps, LODs when needed, and provenance.

Use it when the user asks for asset prep, retopology, cleanup, optimization, baking, UVs, PBR textures, LODs, rig handoff, static mesh delivery, skeletal mesh readiness, game-ready assets, web-ready assets, GLB/glTF/USD/FBX export, DCC-to-engine delivery, or QA of a 3D model.

Do not use it for:

  • Choosing or prompting a specific 3D generation provider.
  • Building a whole environment, shot, level, or composed scene.
  • Running motion-capture sessions or solving mocap performances.
  • Exact CAD, toleranced manufacturing, BIM compliance, or simulation-grade engineering geometry.
  • Character performance direction, although this skill can prepare a mesh for rigging or animation handoff.

Start With The Delivery Contract

Before touching topology, define the asset's consumer. A beautiful mesh is still a failed delivery if the receiving engine cannot load its textures, its unit scale is wrong, or the rigging team cannot bind it.

Ask for or infer these requirements:

  • Asset role: hero prop, background prop, avatar body, modular garment, weapon, vehicle, scan archive, AR product, web configurator item, cinematic asset, marketplace asset, mobile asset.
  • Target consumers: Blender, Maya, Houdini, Unreal, Unity, WebGL/three.js/Babylon, USD pipeline, DCC handoff, custom runtime, marketplace.
  • Format set: source DCC file, .glb/.gltf, .usd/.usda/.usdc/.usdz, .fbx, texture archive, preview renders, validation report.
  • Runtime budget: triangle count, vertex count, material count, draw-call/submesh target, texture resolution, compressed texture formats, LOD count, memory/download size, supported extensions.
  • Spatial contract: real-world dimensions, unit system, axis/up convention, pivot, origin, bounds, snap points, socket points.
  • Material contract: PBR workflow, color space, texture channel packing, transparency mode, normal tangent basis, renderer-specific shader expectations.
  • Animation contract: static mesh, skeletal mesh, blend shapes/morph targets, cloth/hair handoff, deformation range, max bone influences, root bone, naming convention.
  • Rights contract: input source, user rights, third-party references, scan consent, generated-output terms, trademarks/logos, attribution, license, distribution region.

Treat unknown target requirements as a risk, not as permission to guess. If the user cannot specify budgets, create a defensible baseline and label it as a proposed budget.

Evidence Classes

This skill uses three kinds of claims:

  • Documented facts are statements from official specifications, vendor manuals, standards, or project documentation. They are cited in the source notes.
  • Empirical observations are repeatable production findings that should be verified on the user's actual asset and target runtime.
  • Production heuristics are practical defaults. They are not universal rules; change them when the delivery contract says otherwise.

Documented Facts To Anchor Decisions

  • glTF 2.0 is an API-neutral runtime asset delivery format, not an authoring format. It represents scene descriptions with JSON plus binary buffers and image resources, or as GLB for a single binary container. Source: Khronos glTF 2.0 specification, verified 2026-07-11, https://registry.khronos.org/glTF/specs/2.0/glTF-2.0.html.
  • glTF uses a right-handed coordinate system with +Y up, +Z forward, -X right, and meters for linear distances. Source: Khronos glTF 2.0 specification, verified 2026-07-11.
  • glTF material core is metallic-roughness PBR. Base color textures are sRGB; metallic-roughness texture data is linear, with roughness in green and metalness in blue. Normal textures are tangent-space and linear. Source: Khronos glTF 2.0 specification, verified 2026-07-11.
  • glTF skinning uses linear blend skinning with JOINTS_n and WEIGHTS_n attributes; one joint/weight set gives up to four influences per vertex, and JOINTS_n and WEIGHTS_n sets must match. Source: Khronos glTF 2.0 specification, verified 2026-07-11.
  • glTF node transforms can use either a matrix or TRS. Animated nodes must not use matrix; animations target translation, rotation, scale, or morph target weights. Source: Khronos glTF 2.0 specification, verified 2026-07-11.
  • glTF Validator validates JSON/GLB correctness, internal references, binary buffers, forbidden accessor values such as NaN, accessor bounds, sparse accessors, animation data, images, and several extensions. Source: KhronosGroup/glTF-Validator README, verified 2026-07-11, https://github.com/KhronosGroup/glTF-Validator.
  • USD is designed for scalable interchange, composition, layering, overriding, and organization of 3D scene description across DCC pipelines. USD can represent models, geometry, shading, animation, primvars, payloads, references, variants, and asset metadata. It is not itself a high-performance rigging system. Source: OpenUSD Introduction, verified 2026-07-11, https://openusd.org/release/intro.html.
  • Unreal Engine's FB
阅读完整来源 ↗