Blender

This skill lets a coding agent operate Blender on the desktop through Flue, a local shell-to-application bridge. Rather than running an MCP server, the agent pipes Python into `blender_bridge.py` and receives structured JSON back, driving Blender's own `bpy` runtime directly. Flue is described as a thinner, simpler shell contract than MCP, following the path: agent shell to blender_bridge.py to bpy to JSON result.

It is intended for situations where the human requests work performed inside Blender — inspecting the open scene, collections, objects, meshes, materials, or selection; making bounded edits; or running small `bpy` scripts. A CLI agent cannot act inside Blender without a bridge like Flue. To proceed, the agent should first read FLUE.md in the skill directory, which explains how Flue works, the bridge contract, a worked `bpy` example, and safety expectations. If Flue is installed, the agent should also read the Flue SKILL.md and the Blender adapter's APP.md for the operational contract before working. If Flue is not installed, the agent should tell the human; the install command is `pip install flue && flue setup`, and installation must not happen without explicit approval in the current session.

The same stdin/stdout contract supports many other professional desktop applications, including Photoshop, Illustrator, Premiere, After Effects, InDesign, Audition, Houdini, 3ds Max, Unity, and Microsoft Office — a single install covers all adapters. Because Flue acts inside professional desktop software, safety guidance emphasizes treating the human as the driver, preferring small inspectable steps, and avoiding destructive actions unless explicitly requested. Flue is MIT-licensed and reviewable on GitHub and PyPI before use.