Blender Render
PassAudited by ClawScan on May 11, 2026.
Overview
This skill coherently renders user-selected local 3D files with Blender; the main caveats are that it runs local Python/Blender commands and has manual dependencies not fully declared in metadata.
This appears safe for local Blender preview rendering. Before using it, make sure Blender and any optional Python packages come from trusted sources, provide only the local model paths you intend to render, and choose output paths carefully because the scripts will create or overwrite render image files there.
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.
The skill can run Blender headlessly and read/render the local model paths the user provides, then write PNG files to the chosen output location.
The workflow executes bundled Python scripts through Blender on user-supplied local paths. This is central to the stated rendering purpose and is not hidden, but it is still local code execution and file read/write activity.
"$BLENDER_BIN" --background \ --python scripts/render_stl_set_preview.py -- \ --input /path/to/final_parts_dir \ --output-dir /path/to/preview
Use explicit trusted input and output paths, review where files will be written, and run Blender from a trusted installation.
If Pillow is missing, the user may need to install a Python package manually, and the exact installed version may vary.
The skill documents an optional unpinned package installation step, while the registry metadata declares no required binaries or install spec. This is purpose-aligned and user-directed, but dependency provenance is less explicit.
Contact sheets require Pillow (`python3 -m pip install pillow`) if it is not already available.
Install dependencies from trusted package sources, preferably in a controlled Python environment; maintainers should declare Blender and optional Pillow requirements in metadata.