Update to ImagineArt

{
  "name": "blender",
  "description": "Build or edit Blender scenes using ImagineArt reference images and textures — objects, materials, lighting, cameras, keyframes and verified renders. Use for editable .blend projects, product turntables, 3D scenes and material work. Requires Blender app access, a supported integration, or a local Blender executable.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 526
    },
    {
      "relative_path": "assets/ATTRIBUTION.md",
      "size_in_bytes": 150
    },
    {
      "relative_path": "assets/icon.svg",
      "size_in_bytes": 283
    },
    {
      "relative_path": "references/blender-workflow.md",
      "size_in_bytes": 4076
    },
    {
      "relative_path": "references/qa.md",
      "size_in_bytes": 1443
    }
  ],
  "skill_md_contents": "---\nname: blender\ndescription: Build or edit Blender scenes using ImagineArt reference images and textures — objects, materials, lighting, cameras, keyframes and verified renders. Use for editable .blend projects, product turntables, 3D scenes and material work. Requires Blender app access, a supported integration, or a local Blender executable.\n---\n\n# Blender Studio\n\nDeliver an editable `.blend` project and the requested render or export. ImagineArt can\nsupply reference images, texture artwork and backgrounds; build geometry and animation\nin Blender. An image or video that looks three-dimensional is not an editable 3D asset.\n\nRead `references/blender-workflow.md` before operating Blender, and\n`references/qa.md` before delivery.\n\n## Tokens\n\n`/blender` `/blend` `/turntable` `/material` `/3d-scene`\n\nUse this skill when the user wants to work in Blender or receive an editable 3D scene.\nFor only a generated product image, use Product Studio; for a rendered logo video without\nan editable scene, Brand Studio already covers the task.\n\n## Check access and inspect the project\n\n1. Inspect available integrations for actual Blender operations. Do not assume a Blender\n   MCP server, extension, or add-on is installed because this skill is present.\n2. Otherwise use an available local Blender executable with Python scripting, or desktop\n   controls. Follow the host's access and execution permissions. Check the installed version.\n3. Inspect the existing file, active scene, object names, collections, materials, cameras,\n   render engine, frame range, frame rate and output dimensions before editing.\n4. If Blender access is unavailable, state that limitation. Offer a scene-building script\n   or asset handoff, clearly marked unexecuted. Do not claim a `.blend` exists or spend\n   generation credits on an alternative deliverable without the user's agreement.\n\n## Establish the deliverable\n\nUse the user's existing scene and settings for edits. For a new scene, establish subject,\nscale, still versus animation, output dimensions and duration. Choose reasonable defaults\nfor unspecified visual details and state them. Ask about real-world dimensions when they\naffect the task; do not infer accurate product geometry from a single photo.\n\nSeparate the editable project from any interchange export. If GLB, FBX or another format\nis requested, inspect the installed exporter's support and verify that output separately;\nmodifiers, procedural materials and rigs may need format-specific preparation.\n\n## Generate only missing assets\n\n- Use existing user assets first. A change to camera, material color, text or keyframe\n  timing normally needs no new ImagineArt call.\n- Use `generate_image` for reference boards, background plates or texture artwork.\n  Consult the current tool schema for valid model, resolution and aspect-ratio values.\n- Use `request_image_upload` when ImagineArt needs a user-supplied image and the host\n  requires its upload widget. Local Blender-only edits do not require uploading the scene.\n- Resolve the ImagineArt organization as directed by the tool; use returned IDs rather\n  than inventing them. For pending generations, follow the widget's polling flow or the\n  current `fetch_status` tool contract on a host without widgets.\n- Download completed outputs through available authorized file tools to stable project\n  paths before using them in Blender. Never treat a remote URL as an imported local image.\n- Request flat, evenly lit texture artwork where appropriate. Check tiling seams; a prompt\n  asking for seamless output is not proof that it tiles. Do not represent an ordinary RGB\n  image as a calibrated normal, roughness, displacement map, or HDR lighting environment.\n\n## Build or edit\n\n1. Save a working copy when modifying an existing project. Keep the source recoverable.\n2. Build named objects in a task collection; retain editable text, modifiers and material\n   nodes unless the requested output requires conversion. Never clear the whole scene as\n   a routine setup step in an existing project.\n3. Assign materials and image textures deliberately. Check UV placement, texture scale,\n   image color-space role and missing-file indicators.\n4. Place a camera, set its framing and focus, and light the subject. Use real lights or an\n   appropriate environment for illumination; a generated background plate need not light\n   the scene accurately.\n5. For animation, keyframe only the requested objects or camera. Preserve existing actions.\n   For a turntable, keep lighting stable unless the brief calls for moving lights, and\n   check the loop boundary for a duplicate hold frame or a jump.\n6. Render a small preview and inspect it before committing to the full render. Check\n   framing, clipping, materials, readable text, shadows and animation at representative frames.\n7. Save the `.blend`, bundle required resources, render/export, and reopen the saved project\n   to verify the requested result. A successful script exit or a queued render is insufficient.\n\n## Follow-up edits\n\nLocate the existing object, material or action by name. Change only the requested property.\nFor \"make the bottle blue,\" edit that material; preserve geometry, camera, lighting,\nanimation and other materials. Check whether the material is shared before altering it.\nDo not rebuild the scene to make a local edit.\n\n## Failure handling\n\nDistinguish unsupported capabilities, missing files, render failures and ImagineArt refusals.\nStop on safety/content refusals; never switch models to bypass them. If the reason is\nunclear, stop and clarify. Disclose model or output-setting changes used for a confirmed\ncapability limitation. Retry technical failures at most twice; do not duplicate pending\ngeneration jobs or restart a full animation render blindly.\n\n## Delivery\n\nProvide paths to the `.blend`, bundled resources and final outputs. State what was actually\nreopened, rendered and inspected, plus any missing dependencies or unverified outputs.\nNever describe a script, viewport screenshot or reference image as a completed 3D project.\n"
}