Blender Bpy
PassAudited by ClawScan on May 1, 2026.
Overview
This looks like a straightforward Blender automation reference, but it intentionally runs local Blender Python scripts and may use scheduled jobs for long renders.
Before installing, confirm you have Blender available and only run Blender Python scripts you trust or have reviewed. If you use cron or any REST/interactive setup for long-running work, keep it local and user-controlled, and stop scheduled jobs when finished.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A script can modify Blender scenes, write render outputs, consume CPU/GPU resources, and potentially use Python capabilities available to Blender.
The core workflow executes Python through Blender. This is central to the skill's purpose, but users should recognize that Blender Python scripts can perform local actions within the Blender/Python environment.
Scripts run via: `blender --background --python <script.py>`
Run only scripts you intend to use, review generated or downloaded scripts before execution, and keep work in project-specific directories.
Scheduled render jobs may keep running, use compute resources, or produce files after the immediate chat task ends.
The artifact suggests optional scheduled/background execution for long render jobs. This is disclosed and coherent for rendering, but persistence should remain user-controlled.
For long renders, consider Cron jobs in OpenClaw so main chat isn't blocked.
Use scheduled jobs only when desired, set clear stop conditions or limits, and remove cron jobs when rendering is complete.